"Logon failure: unknown user name or bad password"

First, I checked all the obvious problems. The password is right and the login works perfectly.
Here is the output from Developer Studio when trying to deploy/process a cube:

Performing an incremental deployment of the 'MaxMinManufacturingDM' database to the 'localhost' server.
Generating deployment script...
Process Database MaxMinManufacturingDM
Done
Sending deployment script to the server...
Error -1056899072 : The following system error occurred: Logon failure: unknown user name or bad password. .
Error -1055784860 : Errors in the high-level relational engine. A connection could not be made to the data source with the DataSourceID of 'Max Min Manufacturing DM', Name of 'Max Min Manufacturing DM'.
Error -1054932980 : Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of 'Manufacturing Fact', Name of 'Dim Time' was being processed.
Error -1054932979 : Errors in the OLAP storage engine: An error occurred while the 'Year Of Manufacture' attribute of the 'Dim Time' dimension from the 'MaxMinManufacturingDM' database was being processed.

My Analysis Services project (or Business Intelligence project) has only one Data Source, "Max Min Manufacturing DM.ds". I'm using a SQL Server login with a saved password.

I double click the data source to get to the "Data Source Designer" dialog and see the following connection string:

Provider=SQLNCLI.1;Data Source=localhost;Persist Security Info=True;Password=**********;User ID=MaxMinUser;Initial Catalog=MaxMinManufacturingDM

I click "Edit" and "Test Connection" and get "Test connection succeeded". The "Save my password" option is checked. The password is fine and the login should works perfectly. Developer Studio can obviously connect to the database since I've done all the design through it. I can't imagine why I'm getting this error.

I'm using:

Windows XP (dev machine)
Relational Data Mart is using SQL Server 2000 SP4 (I can't upgrade to SQL Server 2005 for business reasons beyond my control)
Visual Studio Studio 2005
SQL Server Analysis Services 2005 (I believe I put SP1 on this).

Any idea?

Hello. Are you running the SQL Server services and the SSAS2005 services with the same or different accounts?

When you process a cube the SSAS2005 must have permissions to read data from the source database. If you run SSAS2005 on a separate machine than the sourec database and the SSAS2005 service account is running as "local system" this server have no permissions on other servers/machines.

You can check this is the SQL Server Configuration manager(for SSAS2005).

Also, try the default impersonation mode for the data source connection.

HTH

Thomas Ivarsson

|||Great!!! Setting the "impersonation mode" to default worked. I guess I should read up on that so I understand what the difference between the impersonation mode and the database login is.

Yes, everything is running on the same server (it's a development box): SSAS2005, MSSQL2000, and Visual Studio.

"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.

"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)

"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.

"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.

"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