Instance Uniunstall problem with "Uninst.isu" file

I am attempting to uninstall an instance of SQL Server 2000. When I run the SS2000 "change/uninstall" process in "Add/Remove Programs" (Control Panel), I get an error message stating that ...

"Unable to locate the installation log file 'C:\Program Files\Microsoft SQL Server\....\Uninst.isu Uninstallation will not continue."

I have looked in the directory and the file is not there.How do I uninstall SS2000?

Hi,

I am facing the same problem in fact I have manually removed all traces of sql server 2000 in program files. It is still exisiting in add/remove programs. How to remove it from there.

Thanks,

Bharath

|||

Even I am facing the same problem.

Can anyone help us., Please...

sql

Instance Uniunstall problem with "Uninst.isu" file

I am attempting to uninstall an instance of SQL Server 2000. When I run the SS2000 "change/uninstall" process in "Add/Remove Programs" (Control Panel), I get an error message stating that ...

"Unable to locate the installation log file 'C:\Program Files\Microsoft SQL Server\....\Uninst.isu Uninstallation will not continue."

I have looked in the directory and the file is not there.How do I uninstall SS2000?

Hi,

I am facing the same problem in fact I have manually removed all traces of sql server 2000 in program files. It is still exisiting in add/remove programs. How to remove it from there.

Thanks,

Bharath

Instance Uniunstall problem with "Uninst.isu" file

I am attempting to uninstall an instance of SQL Server 2000. When I run the SS2000 "change/uninstall" process in "Add/Remove Programs" (Control Panel), I get an error message stating that ...

"Unable to locate the installation log file 'C:\Program Files\Microsoft SQL Server\....\Uninst.isu Uninstallation will not continue."

I have looked in the directory and the file is not there.How do I uninstall SS2000?

Hi,

I am facing the same problem in fact I have manually removed all traces of sql server 2000 in program files. It is still exisiting in add/remove programs. How to remove it from there.

Thanks,

Bharath

|||

Even I am facing the same problem.

Can anyone help us., Please...

Instance name contains a dash

Hello

We are in the process of upgrading our SQL 2K server to a cluster environment. Currently the server is setup as a default instance running on a single box with log shipping as a warm backup

It is required to create an instance name for the new cluster to work. My question is

1) Has anybody tried to have an instance name that dash (-) in it.

Example: \\SERVERNAME\xxx-xx-xxx

I am told that it is not possible to have a server instance named this way. Would like to know if this naming convention is possible under SQL2K If not what is the suggested workaround

This will save a lot of time in application modifications

Thanks in advance

Gabe J

Don't do it, invest the work now and you will have a much more relaxing future. If it takes much time to modify your application to work with another instance name you probably have a design issue in your application.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

|||

Thanks for the advice.

SQL 2000 books online does not specifically mention that dash (-) cannot be used in an instance name ( you can even create tables and other objects in a database that contains a dash in them why not instance name?). Could you please be a little more specific as what exactly the issues would be if the instance name contained dashes.

I have to justify the requirement to make program changes, for that I need to understand what the issues are going to be.

Appreciate your help

Gabe J

|||

I don′t have any specific issue in mind that I can tell of if you use special characters in instance names. Sure you can have special characters in Tables and other objects, but "What you can do" is often the opposite "What is prefered to do". As from my experience I wouldn′t bet on that horse and take the risk of naming the object or even the instance with special characters, although I can. Thats just my two cents, perhaps someone has another opinion about that, but unless you have a hand on your code and have the opportunity to correct that thing (as of my opinion) I would that effort in it.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

|||

In general I agree with what Jens has to say. As far as I know, putting a dash in the instance name is supported. I remember back in the 7.0 days testers went to a lot of trouble to make sure that dashes worked fine in the server name. I don't remember finding any issues there (but it was a long time ago). I do seem to remember that our automation at the time needed multiple changes to run on those servers. :(

The effort was worth it for Microsoft but might not be for your arbitrary application.

|||

One of the suggestions made to get around with this issue is to place a registry hack by adding a key called "Connectto" in the following node

HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\MSSQLServer\Client\

And specify the value as the OLD server name = "XXX-XX-XXX"

and data = DBNMPNTW,\\<New Server name>\pipe\MSSQL$<Instance name>\sql\query

When applications connect irrespective of the connection string, this registry value connects to the SQL server instance.

Seems to work . Agree this is just a workaround instead of solving the real issue of making application modifications.

Has anyone tried this ?

Thanks for you suggestions

|||

Not sure where you heard about this registry hack, but I would not recommend using it unless it was mentioned in a specific Microsoft article...This ***hack*** may not work after a future release. Looks like this workaround maybe setting up a alias for the server. If this is the case, you should use SQL Server Configuration Manager instead.

As others have said, I am not really sure if dashes are supported, but I would not use...SQL Server maybe able to handle it fine, but some other external component may not.

Thanks,

Peter Saddow

|||

Agree that this is a **hack**. The SQL Server is a 2K version not 2005. How do I use the configuration manager to set up and alias name for the instance at the server level?

Thanks

|||

For SQL Server 2000, use SQL Server Client Network Utility. Select the "Alias" tab and enter the required information.

Hope this helps,

Peter Saddow

Instance means...

In oracle The simplest description of instance : combination of memory and process architecture

I sql server, what is the Instance.? it is combination of memory and process architecture if yes then pls give name those processes ?

A combination of menory and process architecture evidenced by a completely unique 'instance' of SQL Server. A computer can contain multiple SQL Server Instances, each with its own databases, security, users.|||

you can install sql server services more than one occurence (instance) in a same physical machine. If you install many sql server services on a single machine, you said to have many instance of sql server. One instance can be Default instance(which will have physical machine name as instance name) and all other instance can be called as Named Instances. Each instance run in different process and memory are and listen to different port. There are sql server serices which is instance instance aware and instance unaware.

eg. Database engine service is INstance aware where as SSIS is not (SSIS is common service for all instances)

Madhu

Installing SQL Server Reporting Services on SBS 2003 Premium for Dynamics CRM 3.0

We are currently in the process of performing a trial installation of Microsoft Dynamics CRM for a client. In amongst their existing IT infrastructure they have:
SBS 2003 SP1 PremiumServer 2003 StandardWhilst an organisation of their size would usually choose to deploy MS CRM Small Business, they've decided they don't want to install SBS on the same system as their SBS box and instead place it on their server 2003 and therefore we're attempting to install CRM Premium.

One of the requirements of Dynamics CRM 3.0 is SQL Server Reporting services (SRS).

SRS will not install on their server 2003 box, as unbeknownst to us initially, besides running Blackberry server, the machine also appears to be running a full blown instance of Terminal Services which SRS refuses to install alongside.. I even tried change user /install ... change user /execute and this failed.

Then I resolved instead to run SRS on the same machine as their SQLServer - the SBS box.

It didn't find visual studio - fair enough.. We don't want to customise any forms just yet.

It then complained about not being able to find ASP.net 1.1 and that sharepoint services were installed.. I read the notes on sharepoint/SRS co-installs and was satisfied there I knew what needed to be done..

I then attempted to install .net framework 1.1, but was advised it was already present. I then checked IIS manager and indeed ASP.net 1.1 was registered and enabled, whilst 2.0 ASP.net was also installed, but prohibited.

I reran the SRS install - and it still couldn't find ASP.net 1.1 and therefore has not installed the web components that MS Dynamics CRM 3.0 requires..

Could someone at least give me a pointer in the right direction here to getting it (SRS) installed happily?

AnthonyI may have found your answer. I believe it's here: http://icu-mscrm.blogspot.com/2007/08/fix-for-weird-error-when-installing-sql.html

Installing SQL Server 2000

When installing sql server, do you need to install a separate license or is
it a part of the installation process of sql server enterprise edition 2000?
Thank you.
New SQL Server DBA
The licence is "virtual", you need it but you don=B4t have to provide
it. You just have t specify how you want to licence the server
processor / CALs.
HTH, Jens Suessmeyer.

Installing SQL Server 2000

When installing sql server, do you need to install a separate license or is
it a part of the installation process of sql server enterprise edition 2000?
Thank you.
--
New SQL Server DBAThe licence is "virtual", you need it but you don=B4t have to provide
it. You just have t specify how you want to licence the server
processor / CALs.
HTH, Jens Suessmeyer.

Installing SQL Server 2000

When installing sql server, do you need to install a separate license or is
it a part of the installation process of sql server enterprise edition 2000?
Thank you.
--
New SQL Server DBAThe licence is "virtual", you need it but you don=B4t have to provide
it. You just have t specify how you want to licence the server
processor / CALs.
HTH, Jens Suessmeyer.

Installing SQL Express 2005 - [Microsoft][SQL Native Client]Shared Memory Provider: No process i

Hi Everyone,

I'm really in a desperate situation. I've tried installing Visual Web Developer including SQL Express 2005. I kept getting the error:

[Microsoft][SQL Native Client]Shared Memory Provider: No process is on the other end of the pipe.

I tried tinkering with the registry and that made things worse.

I even re-installed Windows! I completely nuked my hard disk, formatting it totally. After re-installing Win XP Pro and the rest of my applications, I tried again. I got the SAME ERROR as before:

[Microsoft][SQL Native Client]Shared Memory Provider: No process is on the other end of the pipe.

Am I the only person who's getting this error when installing SQL Express 2005?

I really need to use this software. I have projects to write and it's getting desperate. Is there someone out there who can give me a solution to this? All the Microsoft info on this error relates to connecting to an existing instance, not installing a new one.

I already have SQL 2000 installed. (MSDE + Evaluation version of SQL 2000) Could that be causing the problem? I really don't know what to do.

Ken, Please confirm that the SQL Server service is running. There are a few ways to determine this:

1) Open Task Manager, go to the Processes tab, click on Image Name to sort by name. If SQL Server is running you'll see an entery called sqlservr.exe.

2) Launch the Services manager from Control Panel -> Administrative Tools -> Services. Scroll down to find "SQL Server (<INSTANCE_NAME>)" Where <INSTANCE_NAME> will be displayed as the name of the instance you installed. If you didn't specify an instance name it will show as MSSQLSERVER or SQLEXPRESS, if you installed the Express edition.

3) From the Command Prompt type "Net Start" - this will list the currently running services. Look for "SQL Server (<INSTANCE_NAME>)"

Dan

|||Hi Dan,

Thanks for replying to my message!

Here's what I got:

1) In Task Manager I found sqlservr.exe and sqlmangr.exe.
2) In Services, I don't have anything starting with "SQL Server..." but I do have MSSQLSERVER. The only thing starting with SQL is SQLSERVERAGENT which is not running.
3) Running "net start" shows the same as option 2 - I have MSSQLSERVER running.

I don't have SQL Express running just now. I know that much. Whenever I try to install, I get the error and it rolls back, deleting the files.

What I do have is MSDE and an evaluation version of SQL 2000. They are working fine. I'm using them for my existing SQL stuff just now.

It's almost as if the SQL Expressinstaller expects something to be there that isn't. It tries to use a named pipe to connect to an instance that isn't there.|||

Ken,

Take a look at the file %Program Files%\Microsoft SQL Server\90\Setup Bootstrap\log\SQLSetup*_*_SQL.log for the failed installation - you can open this up in notepad. Search for "Value 3" (this is the generic error code for Windows Installer). Surrounding this should be all of the error text for the problem. Copy and paste that into a reply. My initial guess is that the server isn't starting up - you can also look in the event log for failures associated with SQL Server. I believe the MSSQLSERVER services you see are for your SQL 2K instances and not SQL2K5 so this tells me the SQL2K5 engine is failing to start.

Dan

|||Hi Dan,

I was pretty sure there wasn't an instance of SQL 2005 running. Whenever I tried to install it I got an error message saying it failed. Then I looked through the logs and found the error messages about named pipes.

Since I had deleted the logs, I decided to be brave and try installing it again, so I could see the log files and give you the "value 3" information you asked for.

I was surprised to find that this time it installed perfectly! It asked me to reboot which I did and all seems to be well.

I've had a few teething problems with my database in VWD and DotNetNuke, though. It seemed when I added a database file in VWD, the program couldn't connect to it. I got the following error:

An attempt to attach an auto-named database for file C:\inetpub\wwwroot\DotNetNuke\App_Data\database.mdf failed. A database with the same name exists, or specified file cannot be opened, or it is located on UNC share.

I deleted the database and tried again, stopping and starting the service since there was an error deleting the file. (or creating the new one, I forget which)

Anyway, I've only got one hurdle now - I need to give the ASPNET account permission on the database in question and I don't know how to do it. I've seen a sqlcmd.exe command that I could maybe use from the command line.

I wondered about downloadingMicrosoft SQL Server Management Studio Express but I was hesitant because it had the dubous words "Community Technology Preview" at the end which sounds a bit like b-e-t-a to me. I just had to re-install windows because of a beta (Visual Studio 2005 Beta 2) so I don't relish the prospect of something similar again.

Is SSMSE CTP safe to use? Is that what I should use to give permission to the ASPNET account?

Thanks for the help, by the way. It's really great when someone takes the time to respond!|||I can answer a couple of my own questions here...

The two errors I had seemed to be due to the fact that I had a connection active to the database through Visual Web Developer while I was running the web application that was attempting to connect. When I chose "Detach Database" in VWD, I was able to refresh the browser and everything was rosy.

I'm still curious about SSMSE CTP and whether it's worth a shot or not, though!|||

Ken, I'm glad to hear that you're up and running! As for SSMS-EE it is a CTP which means it's pre-release software. If you read through the General Tools forum (http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=84&SiteID=1) you'll see that some folks have experienced a few issues with it. I'll say this: SSMS-EE is largely based on the same code base as SSMS so it's pretty solid. However, there were a few modifications made which may have destabilized it in certain areas. We're fixing bugs but I don't know when the next update will come out. So I suggest you read through the forum and ask other people who've installed it what they think - that will be the best way to make an informed decision.

Don't take my hesitation as a lack of confidence in the product. I haven't installed SSMS-EE so I can't speak first hand about it and I don't want to steer you wrong.

Your three other options are: 1) use the command line tool (sqlcmd.exe) or 2) buy developer for $50 (http://www.microsoft.com/sql/howtobuy/default.mspx) or 3) Download the evaluation edition and use it for 180-days until SSMS-EE releases (http://www.microsoft.com/sql/downloads/trial-software.mspx). While I can't say for sure, I expect SSMS-EE to release some time in the next 180-days.

Cheers,
Dan

|||Ok, good stuff. I appreciate your unbiased view of the product. That's sound advice.

I think that I'll stick with sqlcmd.exe for now since I don't plan on using SQL 2005 for much yet. Once SSMS-EE releases I'll get it, though.

I would just request one final clarification, if you don't mind. What would you say is the difference between "community technology preview" and beta? I should say that I don't want a huge answer but I'm wondering if they're synonymous or if CTP is one iteration on from beta. Does it go alpha -> beta -> ctp -> release? I just want to be able to have a realistic expectation of the reliability of things I'm going to install in the future based on the suffix :) Just a rough idea would be great.

Have a relaxing Christmas and happy New Year, by the way!