"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

"Invalid authorization specification"

I use SQL Server 2005 Analysis Services Deployment Wizard to generate an xmla deployment script. I get the following error when I try to run it:

<Exception xmlns="urn:schemas-microsoft-com:xml-analysis:exception" />
<Messages xmlns="urn:schemas-microsoft-com:xml-analysis:exception">
<Error ErrorCode="3238395904" Description="OLE DB error: OLE DB or ODBC error: Invalid authorization specification; 28000." Source="Microsoft SQL Server 2005 Analysis Services" HelpFile="" />
<Error ErrorCode="3239182436" Description="Errors in the high-level relational engine. A connection could not be made to the data source with the DataSourceID of 'Max Min Sales DM 1', Name of 'Max Min Sales DM 1'." Source="Microsoft SQL Server 2005 Analysis Services" HelpFile="" />
<Error ErrorCode="3240034316" Description="Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of 'Product', Name of 'Product' was being processed." Source="Microsoft SQL Server 2005 Analysis Services" HelpFile="" />
<Error ErrorCode="3240034317" Description="Errors in the OLAP storage engine: An error occurred while the 'Brand Name' attribute of the 'Product' dimension from the 'MaxMinSalesDM' database was being processed." Source="Microsoft SQL Server 2005 Analysis Services" HelpFile="" />
</Messages>

In the script, I see the following data sources:

<DataSources>
<DataSource xsi:type="RelationalDataSource">
<ID>Max Min Sales DM</ID>
<Name>Max Min Sales DM</Name>
<ConnectionString>Provider=SQLNCLI.1;Data Source=localhost;Persist Security Info=True;Password=;User ID=;Initial Catalog=MaxMinSalesDM;DataTypeCompatibility=80</ConnectionString>
<ImpersonationInfo>
<ImpersonationMode>Default</ImpersonationMode>
</ImpersonationInfo>
<Timeout>PT0S</Timeout>
</DataSource>
<DataSource xsi:type="RelationalDataSource">
<ID>Max Min Sales DM 1</ID>
<Name>Max Min Sales DM 1</Name>
<ConnectionString>Provider=SQLNCLI.1;Data Source=localhost;Persist Security Info=True;Password=;User ID=;Initial Catalog=MaxMinSalesDM;DataTypeCompatibility=80</ConnectionString>
<ImpersonationInfo>
<ImpersonationMode>Default</ImpersonationMode>
</ImpersonationInfo>
<Timeout>PT0S</Timeout>
</DataSource>
</DataSources>

I am surprised the connection strings don't contain any username/password info since the data source objects have user/password info saved with them when I access the project through Visual Studio. I try manually adding in User ID and Password, rerun, and get a different error:

<root xmlns="urn:schemas-microsoft-com:xml-analysis:empty">
<Exception xmlns="urn:schemas-microsoft-com:xml-analysis:exception" />
<Messages xmlns="urn:schemas-microsoft-com:xml-analysis:exception">
<Error ErrorCode="3238395904" Description="OLE DB error: OLE DB or ODBC error: Communication link failure; 08S01; Shared Memory Provider: I/O Error detected in read/write operation [4]. ; 08S01; Login failed for user 'MinMaxUser'.; 28000." Source="Microsoft SQL Server 2005 Analysis Services" HelpFile="" />
<Error ErrorCode="3239182436" Description="Errors in the high-level relational engine. A connection could not be made to the data source with the DataSourceID of 'Max Min Sales DM 1', Name of 'Max Min Sales DM 1'." Source="Microsoft SQL Server 2005 Analysis Services" HelpFile="" />
<Error ErrorCode="3240034316" Description="Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of 'Product', Name of 'Product' was being processed." Source="Microsoft SQL Server 2005 Analysis Services" HelpFile="" />
<Error ErrorCode="3240034317" Description="Errors in the OLAP storage engine: An error occurred while the 'Brand Name' attribute of the 'Product' dimension from the 'MaxMinSalesDM' database was being processed." Source="Microsoft SQL Server 2005 Analysis Services" HelpFile="" />
</Messages>
</root>

Any ideas? Thanks in advance!

This is quite common situation you are having: Analysis Server doesnt have permission to access SQL Server relational database.
It takes little while to troubleshoot connectivity problems. You need to make sure you set correctly security credentials required for Anlaysis Server to access relational database.

For one, try and make sure the account Analysis Server runs under can access SQL Server using windows authentication.

There is quite a bit information out there on how to setup connectivity and connection security.

HTH.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

"Hang" when deploying SSAS solution?

I've noticed that BI Studio seems to 'hang' when I do a Build -> Deploy Solution. The output window will just say "Sending deployment script to the server" and the Deployment Progress window will just churn, with no commands listed. It's been running for nearly ~ 1 hr without feedback - how can I tell if AS is working or not? CPU on the AS instance is idle.

The one workaround I've noticed is to open the database directly in BI Studio, and make the changes there, but this is obviously less than ideal for multiple reasons.

hello,

i'd suggest to check what's the deployment server specified in your project and whether it's as expected. right click on the project node in solution explorer, and go to Properties->Deployment, Target->Server.

also, it should be possible to use SQL Server Profiler to start a trace for the specific AS server, and see what happens on the server when you do a Build->Deploy Solution...

hope this helps,

|||The target server is just "localhost" (which is correct). When I put profiler on it, I can see the large XMLA deployment script, but it doesn't reveal anything about the current status..|||Ok. I created a fresh, new, import from 9.0 project, and made my changes there. Now when I tried to deploy it actually looks like it's doing something (i.e. there's activity in profiler, and the deployment progress tab actually shows what dimensions/measure groups are being processed..)

Very weird.|||Restart the Analysis Services Service on the target deployment server (if possible) before you try to deploy the roject again and see what happens. Seems like something may be hanging up the service when this happens.