Showing posts with label previous. Show all posts
Showing posts with label previous. Show all posts

Wednesday, March 28, 2012

Installtion

I was trying to install SQLSERVER 2000 on WINOWS 2000 Advanced server,i am
getting an error "A previous program installation created pending file
operations on the installation machine.you must restart the computer before
running setup".I did restart the computer again i am getting same error.
I am wondering how to resolve this issue.Pls help me ..
Advance Thanks,
Sriram.
See if this helps:
http://support.microsoft.com/default...95&Product=sql
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
"Ram" <Ram@.discussions.microsoft.com> wrote in message
news:3DF5F779-AAB6-484B-9F22-AA44CBD23F70@.microsoft.com...
> I was trying to install SQLSERVER 2000 on WINOWS 2000 Advanced server,i am
> getting an error "A previous program installation created pending file
> operations on the installation machine.you must restart the computer
before
> running setup".I did restart the computer again i am getting same error.
> I am wondering how to resolve this issue.Pls help me ..
> Advance Thanks,
> Sriram.

Installing Visual Web Dev. 2005 Express: Must uninstall ANY previous versions of SQL Server

Hello,
According to http://msdn.microsoft.com/vstudio/express/vwd/download/, I have to uninstall any and all versions of SQL before I attempt to install the VWD 2005 express edition. is there a work around this? I currently have SQL 2000 installed for my work; a must have for me, I can't just uninstall it.
(yes I left a similar question in the Visual forums, but haven't received any replies as of yet..just fishing for an answer here)
thanks so much, looking forward to giving VWD a test drive.
Ron Malizia
rmalizia@.co.grays-harbor.wa.us

That warning was intended to have users remove any and all previous Betas of SQL Server 2005 prior to installing VWD Express.

It's okay to have MSDE or SQL 2000 on your box, or even to have SQL Server 2005 on your box. But if you have any of the SQL Server 2005 Betas or CTP installs, please remove them first.

-Jeffrey

Monday, March 26, 2012

Installing SSL on SQL Server 2000

previous Message:
Hello Kevin,
I've have installed an Enterprise Root CA on the domain, and I went through
the web form to request and install a new certificate. I installed both an
Administrator certificate and a Web Server certificate, but when I choose
to Force Encryption from the Server Network Utility, I get an error message
when I try restarting SQL Server.
The message says something to the effect that encryption is being
requested, but a valid certificate does not exist. I can see the
certificate in the Personal folder, so I'm not sure why I'm getting the
error message.
Can you help?
Thanks,
Jason
--
We use exactly the same certificate that IIS would use to setup a SSL
session. The new error message above indicates that the SQL Server service
account is not finding the certificate. So, look at the account that is
starting the MSSQLServer service. If the service is started using a domain
user account, and the certificate was requested by a local admin, then the
service will not be able to find the certificate.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.Kevin,
The MSSQLServer service is running under a domain user
account. The account that I used to request the
certificate was a domain admin account. Do I need to
therefore request another certificate while I'm logged in
as the user running the MSSQLServer service? Also, which
template should I use when requesting the certificate,
Administrator or Web Server?
Thanks,
Jason
quote:

>--Original Message--
>previous Message:
>Hello Kevin,
>I've have installed an Enterprise Root CA on the domain,

and I went through
quote:

>the web form to request and install a new certificate. I

installed both an
quote:

>Administrator certificate and a Web Server certificate,

but when I choose
quote:

>to Force Encryption from the Server Network Utility, I

get an error message
quote:

>when I try restarting SQL Server.
>The message says something to the effect that encryption

is being
quote:

>requested, but a valid certificate does not exist. I can

see the
quote:

>certificate in the Personal folder, so I'm not sure why

I'm getting the
quote:

>error message.
>Can you help?
>Thanks,
>Jason
>--
>We use exactly the same certificate that IIS would use

to setup a SSL
quote:

>session. The new error message above indicates that the

SQL Server service
quote:

>account is not finding the certificate. So, look at the

account that is
quote:

>starting the MSSQLServer service. If the service is

started using a domain
quote:

>user account, and the certificate was requested by a

local admin, then the
quote:

>service will not be able to find the certificate.
>
>Thanks,
>Kevin McDonnell
>Microsoft Corporation
>This posting is provided AS IS with no warranties, and

confers no rights.
quote:

>
>.
>
|||Kevin,
I removed the original certificates that I created as the
domain admin account, and went back and logged in as the
account that's running SQL Server. I then requested a new
Web Server certificate, installed it, and selected the
option to Force Protocol Encryption. When I stopped and
restarted SQL Server, everything appears to be running
smoothly.
Thanks for your help in getting me going in the right
direction!
Jason
quote:

>--Original Message--
>Kevin,
>The MSSQLServer service is running under a domain user
>account. The account that I used to request the
>certificate was a domain admin account. Do I need to
>therefore request another certificate while I'm logged

in
quote:

>as the user running the MSSQLServer service? Also, which
>template should I use when requesting the certificate,
>Administrator or Web Server?
>Thanks,
>Jason
>
domain,[QUOTE]
>and I went through
I[QUOTE]
>installed both an
>but when I choose
>get an error message
encryption[QUOTE]
>is being
can[QUOTE]
>see the
>I'm getting the
>to setup a SSL
the[QUOTE]
>SQL Server service
the[QUOTE]
>account that is
>started using a domain
>local admin, then the
>confers no rights.
>.
>
|||You're welcome!
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Hi Kevin,
I have the same problem with Jason, but I have
follow through all the steps and is my SQL server is still
not able to start up after I force protocol encryption.
Have read and follow through this article but still it
couldn't be start.
http://support.microsoft.com/default.aspx?scid=kb;en-
us;318605
Event log under system log shows this error when I try to
start the service.
A fatal error occurred when attempting to access the SSL
server credential private key. The error code returned
from the cryptographic module is 0x80090016.
The CA is a stand alone PC that is not in any domain. My
SQL server is also another standalone PC not in any domain.
Regards,
Chan
quote:

>--Original Message--
>You're welcome!
>Thanks,
>Kevin McDonnell
>Microsoft Corporation
>This posting is provided AS IS with no warranties, and

confers no rights.
quote:

>
>.
>
|||Hi Chan,
This error indicates the following.
- NTE_BAD_KEYSET (0x80090016)
- Key container does not exist.
- You do not have access to the key container.
- The Protected Storage Service is not running.
Since you're attempting to set this up in a workgroup, you'll need to have
http access to a Standalone CA.
You'll need to follow the steps in this kb article:
276553 HOW TO: Enable SSL Encryption for SQL Server 2000 with Certificate
Server
http://support.microsoft.com/?id=276553
After installing the certificate on the server you should be able to view
the certificate by using MMC snapin for certificates or by looking at the
properties of IE, under Content, Certificates. From here, you should be
able to verify that your certificate is valid.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.

Friday, March 23, 2012

Installing SQL Server Express 2005

I'm not able to remove previous version of SQL Server Express 2005 (CTP). It is listed under "Add or Remove Programs", but without REMOVE button. I tried to remove it before, but unsucessfully.

As result, I can't install release version that comes with the Visual Studio 2005 Pro.

Here is the last *_Core.log from C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files:

Microsoft SQL Server 2005 Setup beginning at Fri Nov 18 21:29:08 2005
Process ID : 500
c:\7d4db81c6810fe28cd3f7014507d\setup.exe Version: 2005.90.1399.0
Running: LoadResourcesAction at: 2005/10/18 21:29:8
Complete: LoadResourcesAction at: 2005/10/18 21:29:8, returned true
Running: ParseBootstrapOptionsAction at: 2005/10/18 21:29:8
Loaded DLL:c:\7d4db81c6810fe28cd3f7014507d\xmlrw.dll Version:2.0.3604.0
Complete: ParseBootstrapOptionsAction at: 2005/10/18 21:29:8, returned true
Running: ValidateWinNTAction at: 2005/10/18 21:29:8
Complete: ValidateWinNTAction at: 2005/10/18 21:29:8, returned true
Running: ValidateMinOSAction at: 2005/10/18 21:29:8
Complete: ValidateMinOSAction at: 2005/10/18 21:29:8, returned true
Running: PerformSCCAction at: 2005/10/18 21:29:8
Complete: PerformSCCAction at: 2005/10/18 21:29:8, returned true
Running: ActivateLoggingAction at: 2005/10/18 21:29:8
Complete: ActivateLoggingAction at: 2005/10/18 21:29:8, returned true
Delay load of action "DetectPatchedBootstrapAction" returned nothing. No action will occur as a result.
Action "LaunchPatchedBootstrapAction" will be skipped due to the following restrictions:
Condition "EventCondition: __STP_LaunchPatchedBootstrap__500" returned false.
Running: PerformSCCAction2 at: 2005/10/18 21:29:8
Loaded DLL:C:\WINDOWS\system32\msi.dll Version:3.1.4000.2435
Product "{2AFFFDD7-ED85-4A90-8C52-5DA9EBDC9B8F}" versioned 9.00.1116 is not compatible with current builds of SQL Server.Expected at least version: 9.00.1399.06
The Product Name is "Microsoft SQL Server 2005 Express Edition CTP"
Loaded DLL:C:\WINDOWS\system32\msi.dll Version:3.1.4000.2435
Error: Action "PerformSCCAction2" threw an exception during execution.
Return Code: 70032
Message displayed to user
SQL Server 2005 Setup has detected incompatible components from beta versions of Visual Studio, .NET Framework, or SQL Server 2005. Use Add or Remove Programs to remove these components, and then run SQL Server 2005 Setup again. For detailed instructions on uninstalling SQL Server 2005, see the SQL Server 2005 Readme.

Delay load of action "UploadDrWatsonLogAction" returned nothing. No action will occur as a result.
Message pump returning: 70032

Any advice, please?

This is very strange. I've never heard of the "Remove" button disappearing. If you have the original installation media you can run the following:

setup.exe /qb REMOVE=ALL INSTANCENAME=<your instance name>

If you did the default installation for Express the instanace name will be SQLEXPRESS. If you installed as the default instance it'll be MSSQLSERVER.

Dan

|||The only reason I'm aware of that you would see that behaviour is when you look at add/remove under a non-admin account, although in some applications you only get a Change button, which gives you the option to remove or modify the components.|||

Installing SQL Server express

I had the same problem. (The problem is with sql server 9)My solution is a collection of many ideas. Credit to all.
0. I used the recommended uninstaller (vs_uninst_betas.exe) - it did not work
1. Delete the menu entries
2. Delete the files in %programfiles%\Microsoft SQL Server
3. Delete the files in %programfiles%\Microsoft Visual Studio 8
4. Go to %windir%\microsoft.net\framwork and delete all those old v2.0.* directories
5. Get a registry cleaner and clean the bulk of the orphan entries
6. Run the vs uninstaller (vs_uninst.exe) - by the way it does not like it if you have internet explorer open at the same time
7. Get a cup of tea - run the regedit.exe program. Search in HKEY_LOCAL_MACHINE for "9.00." and delete all the sql server 9 related entries. (Ensure that you do not delete entries used by other programs - check the DisplayName value first)

8. If you belong to a domain ensure that your privileges can be verified -if not then login as the local administrator before installing

Great product, a pity about the lose ends.

This toke me about 16 hours to solve. See http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=119089&SiteID=1

sql

Installing SQL Server Express 2005

I'm not able to remove previous version of SQL Server Express 2005 (CTP). It is listed under "Add or Remove Programs", but without REMOVE button. I tried to remove it before, but unsucessfully.

As result, I can't install release version that comes with the Visual Studio 2005 Pro.

Here is the last *_Core.log from C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files:

Microsoft SQL Server 2005 Setup beginning at Fri Nov 18 21:29:08 2005
Process ID : 500
c:\7d4db81c6810fe28cd3f7014507d\setup.exe Version: 2005.90.1399.0
Running: LoadResourcesAction at: 2005/10/18 21:29:8
Complete: LoadResourcesAction at: 2005/10/18 21:29:8, returned true
Running: ParseBootstrapOptionsAction at: 2005/10/18 21:29:8
Loaded DLL:c:\7d4db81c6810fe28cd3f7014507d\xmlrw.dll Version:2.0.3604.0
Complete: ParseBootstrapOptionsAction at: 2005/10/18 21:29:8, returned true
Running: ValidateWinNTAction at: 2005/10/18 21:29:8
Complete: ValidateWinNTAction at: 2005/10/18 21:29:8, returned true
Running: ValidateMinOSAction at: 2005/10/18 21:29:8
Complete: ValidateMinOSAction at: 2005/10/18 21:29:8, returned true
Running: PerformSCCAction at: 2005/10/18 21:29:8
Complete: PerformSCCAction at: 2005/10/18 21:29:8, returned true
Running: ActivateLoggingAction at: 2005/10/18 21:29:8
Complete: ActivateLoggingAction at: 2005/10/18 21:29:8, returned true
Delay load of action "DetectPatchedBootstrapAction" returned nothing. No action will occur as a result.
Action "LaunchPatchedBootstrapAction" will be skipped due to the following restrictions:
Condition "EventCondition: __STP_LaunchPatchedBootstrap__500" returned false.
Running: PerformSCCAction2 at: 2005/10/18 21:29:8
Loaded DLL:C:\WINDOWS\system32\msi.dll Version:3.1.4000.2435
Product "{2AFFFDD7-ED85-4A90-8C52-5DA9EBDC9B8F}" versioned 9.00.1116 is not compatible with current builds of SQL Server.Expected at least version: 9.00.1399.06
The Product Name is "Microsoft SQL Server 2005 Express Edition CTP"
Loaded DLL:C:\WINDOWS\system32\msi.dll Version:3.1.4000.2435
Error: Action "PerformSCCAction2" threw an exception during execution.
Return Code: 70032
Message displayed to user
SQL Server 2005 Setup has detected incompatible components from beta versions of Visual Studio, .NET Framework, or SQL Server 2005. Use Add or Remove Programs to remove these components, and then run SQL Server 2005 Setup again. For detailed instructions on uninstalling SQL Server 2005, see the SQL Server 2005 Readme.

Delay load of action "UploadDrWatsonLogAction" returned nothing. No action will occur as a result.
Message pump returning: 70032

Any advice, please?

This is very strange. I've never heard of the "Remove" button disappearing. If you have the original installation media you can run the following:

setup.exe /qb REMOVE=ALL INSTANCENAME=<your instance name>

If you did the default installation for Express the instanace name will be SQLEXPRESS. If you installed as the default instance it'll be MSSQLSERVER.

Dan

|||The only reason I'm aware of that you would see that behaviour is when you look at add/remove under a non-admin account, although in some applications you only get a Change button, which gives you the option to remove or modify the components.

|||

Installing SQL Server express

I had the same problem. (The problem is with sql server 9)My solution is a collection of many ideas. Credit to all.
0. I used the recommended uninstaller (vs_uninst_betas.exe) - it did not work
1. Delete the menu entries
2. Delete the files in %programfiles%\Microsoft SQL Server
3. Delete the files in %programfiles%\Microsoft Visual Studio 8
4. Go to %windir%\microsoft.net\framwork and delete all those old v2.0.* directories
5. Get a registry cleaner and clean the bulk of the orphan entries
6. Run the vs uninstaller (vs_uninst.exe) - by the way it does not like it if you have internet explorer open at the same time
7. Get a cup of tea - run the regedit.exe program. Search in HKEY_LOCAL_MACHINE for "9.00." and delete all the sql server 9 related entries. (Ensure that you do not delete entries used by other programs - check the DisplayName value first)

8. If you belong to a domain ensure that your privileges can be verified - if not then login as the local administrator before installing

Great product, a pity about the lose ends.

This toke me about 16 hours to solve. See http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=119089&SiteID=1

Wednesday, March 21, 2012

Installing SQL Server 2005, Detecting Installed IIS

When trying to install SQL 2005, the installation halts at "Detecting Installed IIS". From a previous forum discussion I tried disabling Norton Anti-Virus and Firewall, but the install still does not get past this point.

Please help.

have you checked the sql intall log?|||No, what should I be looking for?|||

%ProgramFiles%\Microsoft SQL Server\90\Setup Bootstrap\Log\Summary.txt

for more information, BOL 2005 (on a machine that you have it installed on succesfully :) ) "Setup [SQL Server], logs"

Derek

|||

Tom, if you can search the suggested logs for the text string "return value 3" and post the +/- 10 lines on each side, we may be able to debug.

Thanks,
Samuel Lester (MSFT)

|||

I cannot find the text string "return value 3"?

Would you be opposed to me emailing the log files to you?

You can email me at sql2005_help@.yahoo.com.

Thanks for any help you can give me.

|||

Since the install seems to be hanging, the logs probably won't be of much use. Go ahead and send me the zipped up log files to samles@.microsoft.com. I can take a look, but my guess is that you may need to toggle something in your anti-virus/firewall/DNS settings. This issue has appeared a few times and the solutions have been in these areas. Sorry about not having a more direct answer.

Thanks,
Samuel Lester (MSFT)

|||I did get SQL 2005 installed! After Sam looked at the log files and could not find anything out of the norm, I made sure my machine met the requirements. With that I reinstalled .Net 2.0 and removed .Net 1.1 from my machine. Whether it was the reinstall of 2.0 or the removal of .Net 1.1; the install went without a hitch. I also did disable my firewall and anti-virus for the install.sql