asked on PowerShell Script 'Hangs' in 3.0
The attached script worked fine in 2.0, however the progress bar did not display. The server was running 2.0 and I upgraded to 3.0. At that point in time, the script no longer runs. It starts out, displays the progress bar, with 0% complete, and then hangs.
If I check task manager, I can see DTExec.exe running, and the data all gets imported, but the script shows no progress. I have to finally kill it with a Ctrl-Break.
Also the script works fine on another server running 3.0.
The script is relatively generic, but via the parms file, it executes DTExec.exe (32-bit) with parameters to execute an SSIS package. There were no problems until I upgraded the other server with PS 3.0. On both servers the version is 3.0, Build = -1, Revision = -1.
I've included the log file from a good run.
0002.ImportData.txt
0002.ImportData-20131212-111527.log
If I check task manager, I can see DTExec.exe running, and the data all gets imported, but the script shows no progress. I have to finally kill it with a Ctrl-Break.
Also the script works fine on another server running 3.0.
The script is relatively generic, but via the parms file, it executes DTExec.exe (32-bit) with parameters to execute an SSIS package. There were no problems until I upgraded the other server with PS 3.0. On both servers the version is 3.0, Build = -1, Revision = -1.
I've included the log file from a good run.
0002.ImportData.txt
0002.ImportData-20131212-111527.log
PowershellMicrosoft SQL Server 2008SSIS
Last Comment
D B
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
For some reason localhost did not work. I needed to use the server name. The server name is one of the values read from the parms.csv file.
You should definitely look at that. Does it work if you use the "." for the server, or "(local)"? Maybe shared memory or Named Pipe is excempt, and you need to use TCP/IP for MSSQL.
ASKER
It was no problem. Made to be portable so server name is in a parameter file. 'localhost' worked on the other servers I ran the code against.