Jump to content

This is a ready-only archive of the InstallSite Forum. You cannot post any new content here. / Dies ist ein Archiv des InstallSite Forums. Hier können keine neuen Beiträge veröffentlicht werden.

SQLDMO issues with SQL and Windows 2008R2...

2 replies to this topic


  • Full Members
  • 3 posts

Posted 07 May 2011 - 00:50

For years we have been using SQLDMO to install/upgrade a database. We started on SQL 2000 and now are moving to 2008 R2. The problem is that Microsoft no longer installs SQLDMO with 2008R2. I also need to install on Windows Server 2008 R2 64 & 32 bit.


I've searched and found a "SQLDMO Merge Module" from www.installsite.org, (SQL 7 and 2000), but it just doesn't seem to want to work/install. I get the the errors trying to use SQLDMO in my vbscript and I look and it wasn't installed. The directories also didn't seem to be created. I also tried just including the two needed files (SQLDMO.dll and .rll) and that works in that it lays down the two files and on the SECOND run of the installer, the .rll file is there and the .dll will register and the installer succeeds.

On the 32 bit machine I can manually register the dll with regsvr32 but not on the 64 bit machine (even with
"cd \windows\syswow64
regsvr32 c:\filename.dll")

Does anybody have an answer/suggestion? How would I debug exactly what Installshield is doing during the install? Can I require that the .rll is laid down first before the .dll file attempts to register?

Any thoughts?


  • Full Members
  • 3 posts

Posted 12 July 2011 - 22:51


Any takers?


  • Moderators
  • 1,447 posts

Posted 13 July 2011 - 01:18

All experience indicates that trying to continue to use Microsoft products beyond their deprecation period is an uphill battle. I really wouldn't try this at all. I don't know what is the case here, but I would assume Microsoft has replaced the underlying API on the server side and probably includes the older APIs in a short transition period in order to migrate their own tools to the new API. Once they are done migrating, so are you - at least according to Microsoft.

For this particular problem I think you need to ask developers and not deployment specialists. Accordingly I want to recommend that you check your options at stackoverflow.com. It is a programming QA site, and you might get more feedback there. Do remember to come back here for deployment questions ;-).
-Stein Åsmul