October 14, 2008 at 5:02 am
Hi, I'm wondering whether anyone can help me with an annoying problem.
I have a production server which won't seem to execute SSIS packages from a command line prompt using dtexec. I have several packages built and working on my test server which have the encrypt sensitive as password option specified, which I then put in the command line.
None of the packages will work after changing their connection strings to the production server, but the message I'm getting is as below:
C:\Documents and Settings\Administrator.UKWACALOR>dtexec /f "d:\SSIS\SRUpdate.dtsx" /De password
Microsoft (R) SQL Server Execute Package Utility
Version 9.00.3042.00 for 32-bit
Copyright (C) Microsoft Corp 1984-2005. All rights reserved.
Started: 11:48:32
Progress: 2008-10-14 11:49:48.65
Source: Data Flow Task
Validating: 0% complete
End Progress
What I've noticed is I can change the excel connection manager to an incorrect path which doesn't exist and the message above is returned, no messages about the Excel connection manager being wrong. I can change the username and passwords of the OLEDB connection to something which doesn't exist and it doesn't complain about them being wrong, just gives the message above.
I've created a new basic package which loads the data from a spreadsheet into a table in the database, and again all it does is give the message above. No error messages, nothing helpful, just Validating then End progress. All the packages will execute ok in the Business Intelligence Development Studio and load the correct data and then execute the relevant stored procedures not a problem when run there.
I've checked the setups of our test server where this will work and our production server where it doesn't, and everything seems to be setup the same.
Does anyone have any ideas about what could be causing packages to not even start executing and then just drop out like the example above??
Thanks
Brad
October 14, 2008 at 5:37 am
Try running it through the package execution GUI.
SSIS does not really return error messages. You simply have to turn on logging in the package. Right-Click in the control flow and choose Logging and log errors to a file. If you have a connection failure during package validation, the package immediately stops. Turning on logging will help give you the detail you need to find the error.
October 14, 2008 at 10:24 am
Hi, thanks for that.
When trying to connect to integration services on my production server I get the following message:
Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)
Library not registered. (Exception from HRESULT: 0x8002801D (TYPE_E_LIBNOTREGISTERED)) (Microsoft.SqlServer.DTSRuntimeWrap)
Library not registered. (Exception from HRESULT: 0x8002801D (TYPE_E_LIBNOTREGISTERED)) (Microsoft.SqlServer.DTSRuntimeWrap)
So I went to check this out on my test server and I can connect ok. I checked to see if Integration services are running which they were, and it was using the same account as on my test server. We had installed the service pack on our production machine but not our test box just yet as people are still using it.
After a search around I found people had overcome this by using the following command:
regsvr32 "C:\Program Files\Microsoft SQL Server\90\DTS\Binn\DTS.dll"
However the problem still persists after doing this. Will the server need to be restarted after reregistering this as I haven't been in a position to do that just yet.
Failing that, does anybody else have any ideas??
Thanks
October 14, 2008 at 10:35 am
Which service pack?
If I remember correctly, if you create a package on a machine with sp2, it will not work on a machine without the service pack. There were some major SSIS changes.
October 14, 2008 at 10:48 am
Sorry, it was Service Pack 2.
One of jobs was run before the service pack was installed about a month ago, and in the job history it has succeded next to it. Plus I'm also not able to run the small SSIS package I created on our production server, which has never touched our test server, and it has the same problem as the other packages with starting and then just ditching out.
The differences introduced in SP2 sounds interesting though, are you able to point me in the direction of any information on it??
Thanks
October 14, 2008 at 10:51 am
If you look up sp2 on the MSDN website, you will find the release notes.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply