"Login timeout expired" prevents package deployment

I'm trying to deploy an SSIS package to a server ("SQL Server" deployment). The package does have an encrypted password, which has both worked nicely and not in the past. It's entirely possible that our other "DBA" has busted something on the server, thus preventing my access to it, but I'm curious if anyone has any experience w/ error code 0x80004005 (Login timeout expired) in the SaveToSqlServer method.

Is that just the generic you-can't-log-in message, or is it really trying to imply that the SQL Server is not responding to login attempts?

Thanks for any help,

Ben

===================================

Could not save the package "C:\Documents and Settings\foo\bar\bin\Deployment\foo.dtsx" to SQL Server "BAR". (Package Installation Wizard)

===================================

The SaveToSQLServer method has encountered OLE DB error code 0x80004005 (Login timeout expired). The SQL statement that was issued has failed.

Program Location:

at Microsoft.SqlServer.Dts.Runtime.Application.SaveToSqlServer(Package package, IDTSEvents events, String serverName, String serverUserName, String serverPassword)

at Microsoft.SqlServer.Dts.Deployment.DtsInstaller.SavePackageToSqlServer(WizardInputs wizardInputs, String packagePassword, Boolean bUseSeverEncryption, String serverName, String userName, String password, String packageFilePath, List`1 configFileNames)

at Microsoft.SqlServer.Dts.Deployment.DtsInstaller.InstallPackagesToSqlServer(WizardInputs wizardInputs)

===================================

The SaveToSQLServer method has encountered OLE DB error code 0x80004005 (Login timeout expired). The SQL statement that was issued has failed.

Program Location:

at Microsoft.SqlServer.Dts.Runtime.Wrapper.ApplicationClass.SaveToSQLServer(IDTSPackage90 Package, IDTSEvents90 pEvents, String ServerName, String ServerUserName, String ServerPassword)

at Microsoft.SqlServer.Dts.Runtime.Application.SaveToSqlServer(Package package, IDTSEvents events, String serverName, String serverUserName, String serverPassword)

Hi Ben,

Did you ever receive a response to this issue? We're experiencing the exact same error.

Thanks!

Kim -

|||I just wonder if there is a firewall in place blocking RPC or something.|||

Hi - Did anyone ever receive a response to this thread? I am having the exact same problem.

Thanks!!

Tyra

|||

All of the sudden I am getting this also. No password on packages. Config files used. Was able to install to SSIS server before, the same package. This was to update a package. I can still import from SSIS manager. I tried both integrated auth and SQL auth with no success. Careful, after it throws up gthe error on screen, the process looks like it could finish successfully, and tells you it does. Your old script is left though.

SSIS is running on the same server as I run the package manifest from. Tried killing SQL server agaent so no packages would run while installing, no luck.

The SaveToSQLServer method has encountered OLE DB error code 0x80004005 (Login timeout expired)

===================================

Could not save the package "C:\DtsDeploy\UpdateDevAdpDms\Load_SoHeaderDim.dtsx" to SQL Server "(local)". (Package Installation Wizard)

===================================

The SaveToSQLServer method has encountered OLE DB error code 0x80004005 (Login timeout expired). The SQL statement that was issued has failed.

Program Location:

at Microsoft.SqlServer.Dts.Runtime.Application.SaveToSqlServer(Package package, IDTSEvents events, String serverName, String serverUserName, String serverPassword)
at Microsoft.SqlServer.Dts.Deployment.DtsInstaller.SavePackageToSqlServer(WizardInputs wizardInputs, String packagePassword, Boolean bUseSeverEncryption, String serverName, String userName, String password, String packageFilePath, List`1 configFileNames)
at Microsoft.SqlServer.Dts.Deployment.DtsInstaller.InstallPackagesToSqlServer(WizardInputs wizardInputs)

===================================

The SaveToSQLServer method has encountered OLE DB error code 0x80004005 (Login timeout expired). The SQL statement that was issued has failed.

Program Location:

at Microsoft.SqlServer.Dts.Runtime.Wrapper.ApplicationClass.SaveToSQLServer(IDTSPackage90 Package, IDTSEvents90 pEvents, String ServerName, String ServerUserName, String ServerPassword)
at Microsoft.SqlServer.Dts.Runtime.Application.SaveToSqlServer(Package package, IDTSEvents events, String serverName, String serverUserName, String serverPassword)

|||

It had been 3 whole days since I last deployed a package, so I guess I forgot how.

I think my problem was using the deployment package. I figured since it was the SSIS deployment utility, it was installing to the SSIS (Integration Servcies) which does not have a named instance. All of my Database engines are named (SQLSERVER/myInstance).

When you use the SSIS deployment utility, you are installing the packages to the Database engine, not the Integration Services....so you have to specify which instance to install the package to. If I am wrong, then there is something wrong with my SQL install.

SO in short, make sure you are using the right server name and instance when deploying packages.