This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Database Import Connection Failure -- Please help.
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Nov 05, 2007
11:02 AM
Database Import Connection Failure -- Please help.
When I use IS2008's Database Import Wizard to connect to a SQL Server 2005 database on our network, I get the following error...
I can connect to the same database using SQL Server Management without any problems. 😞
What could I be doing wrong?
Please advise.
Thanks,
HL
[Microsoft][ODBC SQL Server Driver][SQL Server]To connect to this server you must use SQL Server Management Studio or SQL Management Objects (SMO). (55555)
I can connect to the same database using SQL Server Management without any problems. 😞
What could I be doing wrong?
Please advise.
Thanks,
HL
(21) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Nov 27, 2007
01:15 PM
I installed Microsoft SQL Server 2005 Developer Edition on my clean Windows Server 2003 box, and I verified the SQL-DMO worked okay against a Microsoft SQL Server 2005. I ran your sample VBScript using SQL-DMO and I was able to see all of database names available on the server. I installed the Microsoft SQL Server 2005 RTM and applied the SP2 to set up the machine. Is that how you install your Microsoft SQL Server?
Also, I found a thread in Microsoft Community forum discussing about the "To connect to this server you must use SQL Server Management Studio or SQL Management Objects (SMO)." error. They seem to have solved the error by applying the Microsoft SQL Server 2005 Backward Compatibility Component. See http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=389607&SiteID=1 for more information.
It looks like that I need you to do more tests in order to narrow down your issue. Could you run the following tests and let me know the results?
Scenario 1:[LIST=a]
Install Microsoft SQL Server 2005 Developer Edition RTM with the Database Services and Client Components on a clean machine.
Check to see if the SQL-DMO is working.
Apply Microsoft SQL Server 2005 SP2.
Check to see if the SQL-DMO is working.
Install the InstallShield IDE.
Check to see if the SQL-DMO is working.
Scenario 2:[LIST=a]
Install Microsoft SQL Server 2005 Developer Edition RTM with only the Database Services on a clean machine.
Install Microsoft SQL Server 2005 Backward Compatibility Component available as a feature pack at Microsoft.com.
Check to see if the SQL-DMO is working.
Apply Microsoft SQL Server 2005 SP2.
Check to see if the SQL-DMO is working.
Install the InstallShield IDE.
Check to see if the SQL-DMO is working.
Scenario 3:[LIST=a]
Install Microsoft SQL Server 2005 Express Edition SP2 on a clean machine.
Install Microsoft SQL Server 2005 Backward Compatibility Component available as a feature pack at Microsoft.com.
Check to see if the SQL-DMO is working.
Install the InstallShield IDE.
Check to see if the SQL-DMO is working.
Regards.
Also, I found a thread in Microsoft Community forum discussing about the "To connect to this server you must use SQL Server Management Studio or SQL Management Objects (SMO)." error. They seem to have solved the error by applying the Microsoft SQL Server 2005 Backward Compatibility Component. See http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=389607&SiteID=1 for more information.
It looks like that I need you to do more tests in order to narrow down your issue. Could you run the following tests and let me know the results?
Scenario 1:[LIST=a]
Scenario 2:[LIST=a]
Scenario 3:[LIST=a]
Regards.
![](/skins/images/8C9D13A71C7F7695F3262372C0172D68/responsive_peak/images/icon_anonymous_message.png)