"SQL Server Mobile encountered problems when opening the database."

Hi,

I am writing an application for a device (HP IPAQ 6828) having Windows Mobile 5.0 using

-MS .NET Compact Framework 2.0 SP-1
-SQL Mobile 2005.
-VS 2005 .NET

The application uses Merge Replication. The error occurs in the Synchronise() Method of the SqlCeReplication object.

"SQL Server Mobile encountered problems when opening the database."

repl.AddSubscription(AddOption.ExistingDatabase)
repl.Synchronize()

I also checked the the connection string and it seems to be fine. Both my device and server can ping each other. Moreever I can also access the Web syncronization folder(on server) from the device.

Is anyone having a resolution for this?

This problem may be caused by many reasons.

The most common is not disposing the replication object or other data related objects. Make sure there isn't any other arround.
Sql Mobile 2005 allows multiple connections except while syncronizing.

Another known cause is a bad path on the connection string.

Other forum entries referring this problem:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=334604&SiteID=1

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=478902&SiteID=1

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=961633&SiteID=1|||

Hi,

I finally found the solution to this...

repl.AddSubscription(AddOption.ExistingDatabase)
repl.Synchronize()

(Note: I am trying to synchronize on an exisiting database)

The problem was since my database is already in use by my application and I am trying to sync the same DB. Synchronization cannot occur if the connection is already open by the application. Sql Mobile 2005 allows multiple connections except while synchronizing.

Therefore we need to close and dispose the open connection used by the application as under before attempting to synchonize.

(Below is the sample code)

private sub SampleSync()

sharedCon.close
sharedCon.dispose

try

' TO DO: Set replication object properties here

repl.AddSubscription(AddOption.ExistingDatabase)
repl.Synchronize()

finally
repl.dispose
end try

' TO DO: Open your shared connection here if required.

End sub

Note: Most of the times the connection string also causes a problem. A sample connection string would look like this...

repl.SubscriberConnectionString ="\Program Files\YourAppName\YourDb.sdf;Password =<...>"

"SQL Server Management Studio Express" install location

I just installed the "SQL Server Management Studio Express" but it didn't tell me where it was installed. How do I get the application started ?A short-cut should have been add to ALL Programs | Microsoft SQL Server 2005 | SQL Server Management Studio Express CTP.

Peter|||found it here

"C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\ssmsee.exe"

"SQL Everywhere" is a Sybase trademark

It's all well and good that Microsoft has finally entered the well-established mobile database market (the market that iAnywhere Solution's SQL Anywhere product current *owns* by a wide margin). However, it should be noted that "SQL Everywhere" is a Sybase trademark. For confirmation of this fact, see http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.help.mro12.6.mro126ig/html/mro126ig/legal.htm

For confirmation of the fact that SQL Anywhere owns the mobile database market, note that it is the database of choice for the 500,000 mobile devices that will be used in the 2010 US Census; see http://www.internetadsales.com/modules/news/article.php?storyid=7347

Breck

The full name of the new mobile db is SQL Server Everywhere Edition, and I don't see that in the list you're linking.

Plus, wouldn't you think that a company like Microsoft has done some research before they decide on their product names?

|||

"Plus, wouldn't you think that a company like Microsoft has done some research before they decide on their product names?"

http://seattletimes.nwsource.com/html/businesstechnology/2002397450_microvista23.html

By naming the next version of Windows "Vista," Microsoft may have stepped on the toes of another software company just down the road in Redmond.

So, no, or: When an 800-lb gorilla has got to go, he doesn't ask where's the restroom, he just goes!

Whois vista.com?

Registrant:
CommunityIQ
11241 Willows Road
Redmond, WA 98052
US
Registrar: DOMAINBANK
Domain Name: VISTA.COM
Created on: 02-NOV-94
Expires on: 01-NOV-14
Last Updated on: 27-OCT-05
Administrative, Technical Contact:
Admin, Domain ***@.VISTA.COM
vista.com
11241 Willows Road
Redmond, WA 98052
US
3609208478

'She said the company filed for trademark protection of the words "Windows" and "Vista" used together. ..."The name Vista is commonly used by a variety of companies in a variety of industries," she said. "We are only using the word Vista paired with our trademark Windows so the two together - 'Windows Vista' - ...

If that's MS's stance, then it should have no problem with "Linux Windows". After all,
Windows is used by a variety of ... (yada-yada-yada).

"Sql Broswer" vs. "Hide Sql Instance"

I was never clear what the sql 2005 Browser service is about. But now that I've found the "Hide Instance" property of a server (SQL Server Configuration manager, select Protocols for MSSQLSERVER, right-click, go to Properties) I'm more confused than ever. What is the difference between these two items?

TIA,

Barkingdog

Hiding instance will prevent the broadcast request for instance to list that server instance. YOu will have to directly and explicitly connect to it (and therefore know the name).

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

|||

That makes sense but if I stop the Sql Browser won't that have the same impact?

TIA,

Barkingdog

|||Yes, shutting down your computer will also hide the instance in some way :-)

SQL Browser is not only for enumeration of instances, it will redirect requests to SQL Server instances, although the user did not specify the port to connect to, e.g. Connecting to instance SomeServer\SomeInstance on port 1677 (random port chosen by me) needs to be written in the connection string like this (without SQL Server Browser) SomeServer\SomeInstance,1677. SQL Server browser activated will also redirect the request for SomeServer\SomeInstance to the specific port without naming the port epplicitly.

So, hiding the SQL Server instance means something different. It won′t answer broadcasting request for instance names and only react on connection requests.

HTH, Jens Suessmeyer:

http://www.sqlserver2005.de

"Sql Broswer" vs. "Hide Sql Instance"

I was never clear what the sql 2005 Browser service is about. But now that I've found the "Hide Instance" property of a server (SQL Server Configuration manager, select Protocols for MSSQLSERVER, right-click, go to Properties) I'm more confused than ever. What is the difference between these two items?

TIA,

Barkingdog

Hiding instance will prevent the broadcast request for instance to list that server instance. YOu will have to directly and explicitly connect to it (and therefore know the name).

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

|||

That makes sense but if I stop the Sql Browser won't that have the same impact?

TIA,

Barkingdog

|||Yes, shutting down your computer will also hide the instance in some way :-)

SQL Browser is not only for enumeration of instances, it will redirect requests to SQL Server instances, although the user did not specify the port to connect to, e.g. Connecting to instance SomeServer\SomeInstance on port 1677 (random port chosen by me) needs to be written in the connection string like this (without SQL Server Browser) SomeServer\SomeInstance,1677. SQL Server browser activated will also redirect the request for SomeServer\SomeInstance to the specific port without naming the port epplicitly.

So, hiding the SQL Server instance means something different. It won′t answer broadcasting request for instance names and only react on connection requests.

HTH, Jens Suessmeyer:

http://www.sqlserver2005.de

"Open Table" NOT WORKING. Can someone HELP!

In my instance of "sql server 2005" I right click on a table and select "Open Table" then I get the error message "Object reference not set to..." Then has been happening since I installed I have tryed searching groups and posting to get a solution. I have load the adventure works data base and get the same error when performing "open table". Can someone from MS please respond. Also if Open Table works can you edit the data directly in the results pane?

I had very similar problem. The problem was gone after I installed SP2.|||

Have you tried to attempt from another client's machine against this server?

Also test and try using SP2 on SQL 2005, if it is not a SQL 2005 instance then make sure to have latest service pack on SQL 2000 too.

|||

I am sorry but I should have been more specific about what happened in my case. Here is the story:

The instance of SQL 2005 is on machine A and I had no problem in accessing the tables from machine A. The problem was with machine B on which I was running Management Studio to access the SQL server on machine A. I could connect, open the database, display columns of the tables, but whenever I tried to open a table to browse data or modify the table, I got the error. I installed SQL 2005 SP2 on machine B and the problem was gone. Apparently something was wrong with the instance of Management Studio on machine B. It worked fine flawlessly for a very long time. I have no clue what caused the problem for SSMS.

"Open Table" NOT WORKING. Can someone HELP!

In my instance of "sql server 2005" I right click on a table and select "Open Table" then I get the error message "Object reference not set to..." Then has been happening since I installed I have tryed searching groups and posting to get a solution. I have load the adventure works data base and get the same error when performing "open table". Can someone from MS please respond. Also if Open Table works can you edit the data directly in the results pane?

I had very similar problem. The problem was gone after I installed SP2.|||

Have you tried to attempt from another client's machine against this server?

Also test and try using SP2 on SQL 2005, if it is not a SQL 2005 instance then make sure to have latest service pack on SQL 2000 too.

|||

I am sorry but I should have been more specific about what happened in my case. Here is the story:

The instance of SQL 2005 is on machine A and I had no problem in accessing the tables from machine A. The problem was with machine B on which I was running Management Studio to access the SQL server on machine A. I could connect, open the database, display columns of the tables, but whenever I tried to open a table to browse data or modify the table, I got the error. I installed SQL 2005 SP2 on machine B and the problem was gone. Apparently something was wrong with the instance of Management Studio on machine B. It worked fine flawlessly for a very long time. I have no clue what caused the problem for SSMS.

"Open Table" NOT WORKING. Can someone HELP!

In my instance of "sql server 2005" I right click on a table and select "Open Table" then I get the error message "Object reference not set to..." Then has been happening since I installed I have tryed searching groups and posting to get a solution. I have load the adventure works data base and get the same error when performing "open table". Can someone from MS please respond. Also if Open Table works can you edit the data directly in the results pane?

I had very similar problem. The problem was gone after I installed SP2.|||

Have you tried to attempt from another client's machine against this server?

Also test and try using SP2 on SQL 2005, if it is not a SQL 2005 instance then make sure to have latest service pack on SQL 2000 too.

|||

I am sorry but I should have been more specific about what happened in my case. Here is the story:

The instance of SQL 2005 is on machine A and I had no problem in accessing the tables from machine A. The problem was with machine B on which I was running Management Studio to access the SQL server on machine A. I could connect, open the database, display columns of the tables, but whenever I tried to open a table to browse data or modify the table, I got the error. I installed SQL 2005 SP2 on machine B and the problem was gone. Apparently something was wrong with the instance of Management Studio on machine B. It worked fine flawlessly for a very long time. I have no clue what caused the problem for SSMS.

"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