Post reply

"invalid class string error" when building diagrams

  • May 15, 2006 at 9:12 am

    #91280

    we have sql server 2000 running on windows 2003 server. We have installed sp4 after which I started to receive the following error when creating new diagram "invalid class string error". I'm connected to the server and have EM open, but when I try to add a table to the diagram an error occurs. We upgraded two servers with sp4 and the same problem is happening on both. When I connect from another sql box where sp4 has not yet been installed I am able to create a diagram, which I can then open from the server with sp4.

    I've looked for this error on Google, but was unable to find anything that would point me to the solution. any help would be great!!!!

    Thanks

     

     

  • May 15, 2006 at 1:20 pm

    #637983

    Are you local client tools also patched to sp4?

  • May 15, 2006 at 2:45 pm

    #638009

    I thought that database client tools were a part of Database Components sp4, so I assume that by local you mean another computer(client) and not an actual server. Then the answer is no client was not patched to sp4 - this is the only way I am able to build diagrams.

    thx

  • May 16, 2006 at 8:12 am

    #638158

    I'm pretty sure I remember reading that client tools (EM and QA) must be reinstalled on all clients for SP4.  I don't remember the issues, but this might be one of them.

    You could test this by opening Enterprise Manager on a SP4 server, and see if you can work with diagrams there.

  • May 16, 2006 at 8:15 am

    #638162

    From what I am able to ascertain, an object that is used to create the diagrams is not registered with Windows (e.g. a COM class ID (CLSID) or a ProgID).  That is, the registry entry is missing.   Did you have an problems or encounter any errors during the upgrade?

     

  • May 16, 2006 at 8:20 am

    #638167

    No there were no problems or errors during the upgrade. Do you think reinstalling clinet tools would be an ultimate solution, or do you know of a registry entry that I may want to check?

  • May 16, 2006 at 8:42 am

    #638175

    I can't think of a good reason why you wouldn't upgrade the client tools, since you already upgraded the servers.  I don't think a registry hack will solve the problem.

  • May 16, 2006 at 8:47 am

    #638178

    what do you mean upgrade them? didn't you say they need to be reinstalled? I can reinstall from an original installation CD. is this what you mean or is there an option in sp4 to only upgrade client tools. I didn't think there was, so I'm confused here.

    thank you for your help!!!

  • May 16, 2006 at 8:48 am

    #638179

    Scott is correct, it is always a good idea to upgrade the client tools with the same service pack as the server. Not doing so can cause problems, particularly if something like the MDAC version changes. For example, this has caused problems in the past whereby stored procedure could no longer be debugged in QA because the client tools weren't upgraded.

    Just run the service pack on your workstation. It will only upgrade the items that are installed.

     

  • May 16, 2006 at 10:13 am

    #638200

    let me make things clear. I have client tools such as (QA & EM) installed on a database server which was patched up with sp4. I connect to the server and open EM go to a database and try to create a diagram, here is where I get an error. I also have xp workstation (sql server client tools are installed), but not patched with sp4 - when I connect to the server from workstation I am able to create a diagram. You are suggesting to upgrade a workstation but the problem I have is using client tolls installed on the server and not on workstations.

     

    thank you for you help!!!

  • June 14, 2006 at 2:08 am

    #643563

    Hi

    I experienced the same problem. I was able to solve it by reregistering mdt2dd.dll and msdt70.dll. To do this open a command prompt and type the following:

    Unregistering

    regsvr32.exe /u "Crogram Files\Common Files\Microsoft Shared\MSDesigners98\mdt2dd.dll"

    regsvr32.exe /u "Crogram Files\Common Files\Microsoft Shared\MSDesigners98\msdt70.dll"

    Reregistering

    regsvr32.exe "Crogram Files\Common Files\Microsoft Shared\MSDesigners98\mdt2dd.dll"

    regsvr32.exe "Crogram Files\Common Files\Microsoft Shared\MSDesigners98\msdt70.dll"

     

    Hope this is as helpfull to you as it was to me

    Greetz

  • July 15, 2006 at 1:33 am

    #649397

    I had the same problem, tried the solution you gave and it worked beautifully.

    Thanks a lot

  • September 7, 2007 at 11:51 am

    #732240

    Worked great for me too.  Thanks for such a helpful post

  • February 21, 2008 at 9:06 am

    #780709

    I also encountered this error (after un-installing SQL Server 2005 Express) when trying to add any table to a new diagram, and your solution worked like a charm! Thanks! 😀

Viewing 14 posts - 1 through 14 (of 14 total)

You must be logged in to reply to this topic. Login to reply