May 15, 2009 at 3:35 am
Hi all, please can someone offer me some giudance.
I have a SQL 2005 installed on a Vista Ultimate box, with a second named instance. The installation was from an old DVD with no services packs, I do have a disk with SP1 on it. So after installing the default instance and a named instance, I ran the SP1 update and then collected the remaining updates from the Windows update service. Everything is fine no prblems.
However I now need to remove the second named instance, because it is the back end of an application that is failing to connect to the database, primarily because it is designed to connect to a MSDE instance (I was trying to be clever and get it to connect to a 2005 instance!) Unfortunately the software vender isn't being too helpful as they only support the product when connected to MSDE. I don't want to install the MSDE instance because it will have the same name as the second instance and I fear that it could cause problems, especially if I upgrade to Express and then 2005.
So I went to Add/Remove programs selected the SQL 2005 uninstall and followed the instructions, selecting only the named instance that I needed to remove. Everything seems to go well until I tried to connect to the default instance then everything went pear shaped on me. Nothing could connect to the default instance, the error message was long and unfortunately I didn't make a note of it, but the jist of it was that the server name wasn't recognised, or there was a problem with the connection. I even uninstalled the whole shooting match and tried to re-install just the default instance but that failed with the same error message.
Fortunately I had a disk image so I have restored the box to the state prior to uninstalling the instance, and am now looking for some options. I either need to remove the second named instance or get the software to connect to the 2005 db. I have tried everything that I can think of, down both lines, there are no connection strings as it's all in the software. The instance cannot be removed via Add/Remove as this renders the default instance in operable. Any help would be much appreciated.
Chris
ps when I installed the second instance it stipulated to connect via the windows 'local system' and not the 'Network Service' could this make a difference in the way that the software connects to the database, if so how do I change the instance to connect with the 'Network Service' as opposed to the 'Local System'?
Thanks in advance
May 16, 2009 at 2:51 am
Ok I done some rooting around and lots of thinking, can someone tell me if I am on the right tracks here.
When I installed the updates for SQL 2005 via the Windows update service, the update makes changes to both the system files and the application files, correct?
When I uninstalled the second instance the uninstall was performed by the 'Microsoft Server Setup Support Files', correct?
Now from what I have read these files seem to very import in the uninstall process, so could it be that these files are only complatible with the original installation (with no service packs added) and that during the uninstall of the second instance they over wrote some of the Service Pack files, which could, or did make it impossible to connect to the server, after uninstalling the second instance.
If this is indeed the case can these files be Removed safely with the Windows 'Add/Remove' function and where can I download new ones that will work with SP3?
May 19, 2009 at 3:41 am
The application that I want to connect to the second named instance has the MSDE connection string hard coded into it, so now I have to look at uninstalling the second named instance - can anyone please help?
May 22, 2009 at 6:08 am
Sorted now - had to reregister dmo after uninstalling instance.
Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply