DTS_E_PRODUCTLEVELTOLOW
Feb 24, 2008
I just upgraded my development machine from SQL Server 2005 Express edition to Standard edition. I can still execute my packages in Business Intelligence Development Studio, and when I use SQL Server Management Studio to connect to SSIS on our server I can import them into the database and run them (I understand the package is actually running locally, using SSIS on my desktop).
But when I RDP to the server, bring up SSMS, and try to run the package from the MSDB folder, I now get:
SSIS Error Code: DTS_E_PRODUCTLEVELTOLOW. The product level is insufficient for component "Task 1"
Before the upgrade, that worked fine.
So which product level is too low? I upgraded SQL Server on my desktop, so SSIS, SSMS, and BIDS there cannot be any lower than they were before. That seems to leave SQL Server and/or SSIS on the server, but that doesn't make any sense at all.
All BIDS is doing is generating XML (the .dtsx file) that represents the SSIS package, and as far as I know SSIS as a language is the same everywhere so how can there be run-time discrepancies between the development host and the deployment host?
View 4 Replies
Mar 20, 2008
hy all
I have a simple SSIS packae dataflow importing data from FileSource to SQL2005 table.
From my local machine it works fine but after deployment to MSDB db on the target server i got the error above.
The FileSource is located in a remotlly FileServer
my Server data:
Microsoft SQL Server Enterprise Edition (64-bit)
Microsoft Windows NT 5.2 (3790)
version: 9.00.3042.00
my workstation data:
Microsoft SQL Server Management Studio 9.00.3042.00
Microsoft Analysis Services Client Tools 2005.090.3042.00
Microsoft Data Access Components (MDAC) 2000.085.1117.00 (xpsp_sp2_rtm.040803-2158)
Microsoft MSXML 2.6 3.0 4.0 5.0 6.0
Microsoft Internet Explorer 7.0.5730.11
Microsoft .NET Framework 2.0.50727.42
Operating System 5.1.2600
View 8 Replies
View Related
Mar 23, 2008
hy all
this is my second post on this issue, and I'm hoping to solve it now.
I got this error msg: DTS_E_PRODUCTLEVELTOLOW
when tring to run SSIs package with load data from File source (simple one) to DB on SQL2005 and the package is stored and exec on the SSIS server.
We installed the SSIS server with the Database engine on the same machine.
when running from my workstation it work fine, but when the package was uploaded to the MSDB and executed from there - it failed.
help, anyone.
Oh, by the way - microsoft issues on that problems didnt helpd - i got the enteprise edition installed and there is a match between the versions of all the components: BIDS, Server SSIS and SQL2005
udi
View 1 Replies
View Related
May 25, 2007
I have created SSIS packages to move data utilizing OLE-DB with an iSeries box.
The packages runs fine in the Integration Services Project but when I import the packages to the server it fails with:
Error: SSIS Error Code DTS_E_PRODUCTLEVELTOLOW. The product level is insufficient for component.
Any help would be appreciated.
We are running SQL Server 2005 Enterprise Edition with SP 2A.
View 25 Replies
View Related
Dec 27, 2007
I am having the following problems and scenarios.
I am moving all of our SSIS packages from a stand alone server to a clustered environment. The old server ran Enterprise Edition, the new server runs Enterprise Edition 64 bit.
One package on the new server is giving me the error messaage DTS_PRODUCTLEVELTOLOW when run from a job. The package is stored in MSDB
I went back to the server and ran the following with the following results.
- Connected to SSIS from Management Studio on my desktop and ran the package and got the same error message.
- Did the same as above but was connected to the server through Remote Desktop and it ran fine
- Ran the job, which just runs the package and it ran fine
On the new server it won't run in any scenario.
Any ideas on what to do?
Thanks
View 8 Replies
View Related
