![]() | |
![]() |
| | Thread Tools | Display Modes |
#11
| |||
| |||
|
|
JohnH (JohnH (AT) discussions (DOT) microsoft.com) writes: I did contact Pinnacle and they seemed unable to help. I spent ages with their helpdesk for Studio 11 but they seemed unable (or perhaps unprepared) to deal with the problem. I'm beginning to think that the only solution will be a clean install of XP (and all other software). I guess it's overdue as its been a couple of years since I last did it. Who wants reinstall a machine? I hate it everytime I have to do it - be that because of a hardware problem, or because I get new box or OS. It takes ages to get everything in place. I did look under the Start menu in All Programs and could find not reference to SQL Server Configuration Manager or the SQL Server Program group. In Program Files there are two references. The first is Microsoft SQL Server (containing 3 folders labelled 80, 90 and MSSQL.1. All 3 folders contain additional folders and/or files) and the second is Microsoft SQL Server Compact Edition (containing a single folder v3.1) It is the folder with MSSQL.1 that holds the remnants of the missing instance. Not you will have much use for that piece of information. One more option is to open a support case with Microsoft. But they are likely to charge you an arm and a leg. Or did you say that a Microsoft person helped you to uninstall Microsoft Accounting? After all, it seems to be a bug in that uninstall that caused the problem. So from that point of view, they should refund you. But I would not take that for granted. -- Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se Links for SQL Server Books Online: SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx SQL 2000: http://www.microsoft.com/sql/prodinf...ons/books.mspx |
#12
| |||
| |||
|
|
Hello Erland - Thanks for the reply. I've decided to have one more go at uninstalling the whole SQL installation, using a program called Revo Uninstaller. I've used it before and it can be configured to remove all traces of a software package. I now have six instances of SQL software showing up when I scan with Revo Uninstaller. These are: Hotfix 2050 for SQL Server 2000 ENU (KB948110) - Cannot ID a location Microsoft SQL Server Compact Edition (ENU) - In C:\Progarm Files\MS SQL Server Microsoft SQL Server Desktop Engine (PINNACLESYS) - Cannot ID a location Microsoft SQL Server Native Client - In C:\Prgram Files\MS SQL Server Microsoft SQL Server Setup Support Files (English) - In C:\Program Files\MS SQL Server\90\Setup Bootstrap Microsoft SQL Server VSS Writer - In C:\Program Files\MS SQL Server (with subfolders: 80, 90, MSSQL.1) My thinking is to remove all traces of SQL, including PINNACLESYS and then to reinstall SQL and if necessary, reinstall Pinnacle's Studio package. Just one last question for you - Can I remove all the above instances without causing terminal problems with my machine? Very many thanks for all your help and support - all much appreciated. |
#13
| |||
| |||
|
|
JohnH (JohnH (AT) discussions (DOT) microsoft.com) writes: Hello Erland - Thanks for the reply. I've decided to have one more go at uninstalling the whole SQL installation, using a program called Revo Uninstaller. I've used it before and it can be configured to remove all traces of a software package. I now have six instances of SQL software showing up when I scan with Revo Uninstaller. These are: Hotfix 2050 for SQL Server 2000 ENU (KB948110) - Cannot ID a location Microsoft SQL Server Compact Edition (ENU) - In C:\Progarm Files\MS SQL Server Microsoft SQL Server Desktop Engine (PINNACLESYS) - Cannot ID a location Microsoft SQL Server Native Client - In C:\Prgram Files\MS SQL Server Microsoft SQL Server Setup Support Files (English) - In C:\Program Files\MS SQL Server\90\Setup Bootstrap Microsoft SQL Server VSS Writer - In C:\Program Files\MS SQL Server (with subfolders: 80, 90, MSSQL.1) My thinking is to remove all traces of SQL, including PINNACLESYS and then to reinstall SQL and if necessary, reinstall Pinnacle's Studio package. Just one last question for you - Can I remove all the above instances without causing terminal problems with my machine? Very many thanks for all your help and support - all much appreciated. Ah, this is enlightening. It seems that the PINNACLESYS instance is not meant to be SQL 2005, but SQL 2000. Else it would not say Desktop Engine. But some of the other files are definitely from SQL 2005. Note that these are not server instances, but they are just SQL Server related install items. Yes, I think that you could just as well try to nuke them. But if you have a machine to spare, I would first try to make an install of Pinnacle to see if that works out, and if you get an instance of SQL 2000 MSDE. Else it's probably not worth the effort. -- Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se Links for SQL Server Books Online: SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx SQL 2000: http://www.microsoft.com/sql/prodinf...ons/books.mspx |
#14
| |||
| |||
|
|
JohnH (JohnH (AT) discussions (DOT) microsoft.com) writes: Hello Erland - Thanks for the reply. I've decided to have one more go at uninstalling the whole SQL installation, using a program called Revo Uninstaller. I've used it before and it can be configured to remove all traces of a software package. I now have six instances of SQL software showing up when I scan with Revo Uninstaller. These are: Hotfix 2050 for SQL Server 2000 ENU (KB948110) - Cannot ID a location Microsoft SQL Server Compact Edition (ENU) - In C:\Progarm Files\MS SQL Server Microsoft SQL Server Desktop Engine (PINNACLESYS) - Cannot ID a location Microsoft SQL Server Native Client - In C:\Prgram Files\MS SQL Server Microsoft SQL Server Setup Support Files (English) - In C:\Program Files\MS SQL Server\90\Setup Bootstrap Microsoft SQL Server VSS Writer - In C:\Program Files\MS SQL Server (with subfolders: 80, 90, MSSQL.1) My thinking is to remove all traces of SQL, including PINNACLESYS and then to reinstall SQL and if necessary, reinstall Pinnacle's Studio package. Just one last question for you - Can I remove all the above instances without causing terminal problems with my machine? Very many thanks for all your help and support - all much appreciated. Ah, this is enlightening. It seems that the PINNACLESYS instance is not meant to be SQL 2005, but SQL 2000. Else it would not say Desktop Engine. But some of the other files are definitely from SQL 2005. Note that these are not server instances, but they are just SQL Server related install items. Yes, I think that you could just as well try to nuke them. But if you have a machine to spare, I would first try to make an install of Pinnacle to see if that works out, and if you get an instance of SQL 2000 MSDE. Else it's probably not worth the effort. -- Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se Links for SQL Server Books Online: SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx SQL 2000: http://www.microsoft.com/sql/prodinf...ons/books.mspx |
![]() |
| Thread Tools | |
| Display Modes | |
| |