Hi Joe,
The little server icon is called Service Manager and it does not list the
named instances.
To check the status of the named instance that you have installed, you can
type the server name in the Severbox. It is a dropdown cum text box. So you
will be able to type the SQL Server Name.
For a named instance, the SQL Server name would be
<computername>\<Instancename>.
In your case it would be <computername>\JoesDB01.
After typing the server name, click on Refresh Services button and it
should show you the state of the different services, like the SQL Server,
SQL Server Agent, Distributed Transaction Coordinator.
You can control the state of each Service,
1. Start - Click on this to start/Continue the service, if it is Stopped or
Paused
2. Stop - Click on this to stop the Service.
3. Pause - Click on this to pause the service. Pausing, will allow the
current users to work and will not allow new users to connect to the SQL
Server.
You can also installed the SQL Web Data Administrator, to create and manage
Database from
http://www.microsoft.com/downloads/d...798-C57A-419E-
ACBC-2A332CB7F959&displaylang=en
HTH
Ashish
This posting is provided "AS IS" with no warranties, and confers no rights.
Great! This helped a lot. Things seem to be working fine now
Thanks Ashish!
-- Joe
sql
Showing posts with label service. Show all posts
Showing posts with label service. Show all posts
Friday, March 30, 2012
Monday, March 26, 2012
Installing Delphi 2005 Gives Security Exception..
After installing delphi 2005 I am getting a security exception when trying
to access the reports/report manager/web service of Reporting Services.
I think it is Borland related - the stack trace shows borland in there
now...How do I fix?
======================================================== Description: The application attempted to perform an operation not allowed
by the security policy. To grant this application the required permission
please contact your system administrator or change the application's trust
level in the configuration file.
Exception Details: System.Security.SecurityException: Request for the
permission of type System.Security.Permissions.EnvironmentPermission,
mscorlib, Version=1.0.5000.0, Culture=neutral,
PublicKeyToken=b77a5c561934e089 failed.
Source Error:
An unhandled exception was generated during the execution of the
current web request. Information regarding the origin and location of the
exception can be identified using the exception stack trace below.
Stack Trace:
[SecurityException: Request for the permission of type
System.Security.Permissions.EnvironmentPermission, mscorlib,
Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
failed.]
System.Security.CodeAccessSecurityEngine.CheckHelper(PermissionSet
grantedSet, PermissionSet deniedSet, CodeAccessPermission demand,
PermissionToken permToken) +675
System.Security.CodeAccessSecurityEngine.Check(PermissionToken permToken,
CodeAccessPermission demand, StackCrawlMark& stackMark, Int32 checkFrames,
Int32 unrestrictedOverride) +0
System.Security.CodeAccessSecurityEngine.Check(CodeAccessPermission cap,
StackCrawlMark& stackMark) +88
System.Security.CodeAccessPermission.Demand() +62
System.Environment.GetEnvironmentVariable(String variable) +53
Borland.DbkAsp.DbkConnModule.getInstallRoot() +27
Borland.DbkAsp.DbkConnModule.OnBeginRequest(Object sender, EventArgs e)
+191
System.Web.SyncEventExecutionStep.System.Web.HttpApplication+IExecutionStep.Execute()
+60
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean&
completedSynchronously) +87Hi Wayne,
Thanks for your posting!
It seems that the security module internal reports the error message, I
will make research to see whether others meet this issue before. You are
encouraged to see whether Borland guys have solutions to this issue.
Sincerely yours,
Michael Cheng
Online Partner Support Specialist
Partner Support Group
Microsoft Global Technical Support Center
---
Get Secure! - http://www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!|||Search for 'Security Exception - Article ID : 887787'.
I uninstalled Delphi 2005 and the problem went away immediately.....
I look forward to your solution. (I imagine I just have to give rights to
some borland assembly or something for Rptsvs..)
"Michael Cheng [MSFT]" <v-mingqc@.online.microsoft.com> wrote in message
news:JFbg9w11EHA.1512@.cpmsftngxa10.phx.gbl...
> Hi Wayne,
> Thanks for your posting!
> It seems that the security module internal reports the error message, I
> will make research to see whether others meet this issue before. You are
> encouraged to see whether Borland guys have solutions to this issue.
>
> Sincerely yours,
> Michael Cheng
> Online Partner Support Specialist
> Partner Support Group
> Microsoft Global Technical Support Center
> ---
> Get Secure! - http://www.microsoft.com/security
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only, many thanks!
>|||Hi Wayne,
Unfortunately, I found the only workaround available now is uninstall
Delphi 2005.
Thank you for your patience and corporation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Online Partner Support Specialist
Partner Support Group
Microsoft Global Technical Support Center
---
Get Secure! - http://www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!|||Michael,
Exactly what did you find. What are we 'working around'? The problem
is what exactly? Isn't this an assembly rights issue, like when you install
that URL monitor DLL (security fix) from microsoft (forgot its name). You
would get these same sort of errors, until you put some magic entries into a
config file...
"Michael Cheng [MSFT]" <v-mingqc@.online.microsoft.com> wrote in message
news:g$%23vysC2EHA.3152@.cpmsftngxa10.phx.gbl...
> Hi Wayne,
> Unfortunately, I found the only workaround available now is uninstall
> Delphi 2005.
> Thank you for your patience and corporation. If you have any questions or
> concerns, don't hesitate to let me know. We are always here to be of
> assistance!
>
> Sincerely yours,
> Michael Cheng
> Online Partner Support Specialist
> Partner Support Group
> Microsoft Global Technical Support Center
> ---
> Get Secure! - http://www.microsoft.com/security
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only, many thanks!
>|||Hi Wayne,
Yes, you probably have to change the policy files to include some CAS (Code
Access Security) permissions for the Borland assemblies. See the following
information for more detailed information about how to set the Code Access
Security correctly
Code Access Security
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpguide/htm
l/cpconCodeAccessSecurity.asp
Code Access Security in SQL Server 2000 Reporting Services
http://msdn.microsoft.com/data/default.aspx?pull=/library/en-us/dnsql2k/html
/dngrfCodeAccessSecurityInSQLServer2000ReportingServices.asp
Hope this helps and if you have any questions or concerns, don't hesitate
to let me know. We are always here to be of assistance!
Sincerely yours,
Michael Cheng
Online Partner Support Specialist
Partner Support Group
Microsoft Global Technical Support Center
---
Get Secure! - http://www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!|||Reinstall Delphi 2005 and press "No" when asked:
An entry needs to be added to the machine.config file to enable ASP
debugging for Delphi.
Would you like setup to add this entry for you now?
"Wayne Brantley" wrote:
> Michael,
> Exactly what did you find. What are we 'working around'? The problem
> is what exactly? Isn't this an assembly rights issue, like when you install
> that URL monitor DLL (security fix) from microsoft (forgot its name). You
> would get these same sort of errors, until you put some magic entries into a
> config file...
>
> "Michael Cheng [MSFT]" <v-mingqc@.online.microsoft.com> wrote in message
> news:g$%23vysC2EHA.3152@.cpmsftngxa10.phx.gbl...
> > Hi Wayne,
> >
> > Unfortunately, I found the only workaround available now is uninstall
> > Delphi 2005.
> >
> > Thank you for your patience and corporation. If you have any questions or
> > concerns, don't hesitate to let me know. We are always here to be of
> > assistance!
> >
> >
> > Sincerely yours,
> >
> > Michael Cheng
> >
> > Online Partner Support Specialist
> > Partner Support Group
> > Microsoft Global Technical Support Center
> > ---
> > Get Secure! - http://www.microsoft.com/security
> >
> > This posting is provided "as is" with no warranties and confers no rights.
> > Please reply to newsgroups only, many thanks!
> >
>
>
to access the reports/report manager/web service of Reporting Services.
I think it is Borland related - the stack trace shows borland in there
now...How do I fix?
======================================================== Description: The application attempted to perform an operation not allowed
by the security policy. To grant this application the required permission
please contact your system administrator or change the application's trust
level in the configuration file.
Exception Details: System.Security.SecurityException: Request for the
permission of type System.Security.Permissions.EnvironmentPermission,
mscorlib, Version=1.0.5000.0, Culture=neutral,
PublicKeyToken=b77a5c561934e089 failed.
Source Error:
An unhandled exception was generated during the execution of the
current web request. Information regarding the origin and location of the
exception can be identified using the exception stack trace below.
Stack Trace:
[SecurityException: Request for the permission of type
System.Security.Permissions.EnvironmentPermission, mscorlib,
Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
failed.]
System.Security.CodeAccessSecurityEngine.CheckHelper(PermissionSet
grantedSet, PermissionSet deniedSet, CodeAccessPermission demand,
PermissionToken permToken) +675
System.Security.CodeAccessSecurityEngine.Check(PermissionToken permToken,
CodeAccessPermission demand, StackCrawlMark& stackMark, Int32 checkFrames,
Int32 unrestrictedOverride) +0
System.Security.CodeAccessSecurityEngine.Check(CodeAccessPermission cap,
StackCrawlMark& stackMark) +88
System.Security.CodeAccessPermission.Demand() +62
System.Environment.GetEnvironmentVariable(String variable) +53
Borland.DbkAsp.DbkConnModule.getInstallRoot() +27
Borland.DbkAsp.DbkConnModule.OnBeginRequest(Object sender, EventArgs e)
+191
System.Web.SyncEventExecutionStep.System.Web.HttpApplication+IExecutionStep.Execute()
+60
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean&
completedSynchronously) +87Hi Wayne,
Thanks for your posting!
It seems that the security module internal reports the error message, I
will make research to see whether others meet this issue before. You are
encouraged to see whether Borland guys have solutions to this issue.
Sincerely yours,
Michael Cheng
Online Partner Support Specialist
Partner Support Group
Microsoft Global Technical Support Center
---
Get Secure! - http://www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!|||Search for 'Security Exception - Article ID : 887787'.
I uninstalled Delphi 2005 and the problem went away immediately.....
I look forward to your solution. (I imagine I just have to give rights to
some borland assembly or something for Rptsvs..)
"Michael Cheng [MSFT]" <v-mingqc@.online.microsoft.com> wrote in message
news:JFbg9w11EHA.1512@.cpmsftngxa10.phx.gbl...
> Hi Wayne,
> Thanks for your posting!
> It seems that the security module internal reports the error message, I
> will make research to see whether others meet this issue before. You are
> encouraged to see whether Borland guys have solutions to this issue.
>
> Sincerely yours,
> Michael Cheng
> Online Partner Support Specialist
> Partner Support Group
> Microsoft Global Technical Support Center
> ---
> Get Secure! - http://www.microsoft.com/security
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only, many thanks!
>|||Hi Wayne,
Unfortunately, I found the only workaround available now is uninstall
Delphi 2005.
Thank you for your patience and corporation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Online Partner Support Specialist
Partner Support Group
Microsoft Global Technical Support Center
---
Get Secure! - http://www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!|||Michael,
Exactly what did you find. What are we 'working around'? The problem
is what exactly? Isn't this an assembly rights issue, like when you install
that URL monitor DLL (security fix) from microsoft (forgot its name). You
would get these same sort of errors, until you put some magic entries into a
config file...
"Michael Cheng [MSFT]" <v-mingqc@.online.microsoft.com> wrote in message
news:g$%23vysC2EHA.3152@.cpmsftngxa10.phx.gbl...
> Hi Wayne,
> Unfortunately, I found the only workaround available now is uninstall
> Delphi 2005.
> Thank you for your patience and corporation. If you have any questions or
> concerns, don't hesitate to let me know. We are always here to be of
> assistance!
>
> Sincerely yours,
> Michael Cheng
> Online Partner Support Specialist
> Partner Support Group
> Microsoft Global Technical Support Center
> ---
> Get Secure! - http://www.microsoft.com/security
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only, many thanks!
>|||Hi Wayne,
Yes, you probably have to change the policy files to include some CAS (Code
Access Security) permissions for the Borland assemblies. See the following
information for more detailed information about how to set the Code Access
Security correctly
Code Access Security
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpguide/htm
l/cpconCodeAccessSecurity.asp
Code Access Security in SQL Server 2000 Reporting Services
http://msdn.microsoft.com/data/default.aspx?pull=/library/en-us/dnsql2k/html
/dngrfCodeAccessSecurityInSQLServer2000ReportingServices.asp
Hope this helps and if you have any questions or concerns, don't hesitate
to let me know. We are always here to be of assistance!
Sincerely yours,
Michael Cheng
Online Partner Support Specialist
Partner Support Group
Microsoft Global Technical Support Center
---
Get Secure! - http://www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!|||Reinstall Delphi 2005 and press "No" when asked:
An entry needs to be added to the machine.config file to enable ASP
debugging for Delphi.
Would you like setup to add this entry for you now?
"Wayne Brantley" wrote:
> Michael,
> Exactly what did you find. What are we 'working around'? The problem
> is what exactly? Isn't this an assembly rights issue, like when you install
> that URL monitor DLL (security fix) from microsoft (forgot its name). You
> would get these same sort of errors, until you put some magic entries into a
> config file...
>
> "Michael Cheng [MSFT]" <v-mingqc@.online.microsoft.com> wrote in message
> news:g$%23vysC2EHA.3152@.cpmsftngxa10.phx.gbl...
> > Hi Wayne,
> >
> > Unfortunately, I found the only workaround available now is uninstall
> > Delphi 2005.
> >
> > Thank you for your patience and corporation. If you have any questions or
> > concerns, don't hesitate to let me know. We are always here to be of
> > assistance!
> >
> >
> > Sincerely yours,
> >
> > Michael Cheng
> >
> > Online Partner Support Specialist
> > Partner Support Group
> > Microsoft Global Technical Support Center
> > ---
> > Get Secure! - http://www.microsoft.com/security
> >
> > This posting is provided "as is" with no warranties and confers no rights.
> > Please reply to newsgroups only, many thanks!
> >
>
>
Installing client components
OK, we have a dedicated server with a standard SQL Server license. Weeks ago I ordered the Reporting Service from Microsoft, as it comes free with SQL Server but you still have to order it. It came in a bare-bones white envelope without any documentation, just a CD inside.
No problem -- I was able to install it on our server -- it recognized that we had a qualifying SQL Server installation, and installed Reporting Service.
I wanted to install the client components both on my laptop and my development computer at work, but I was wondering how it would know I was entitled to install, since the qualifying database was on a remote machine. Well, there was no problem on my laptop -- it installed OK. I guess it found what it was looking for.
Now I am trying to install it on my computer at work, and now it is asking for a 25-character product key. Well, the CD did not come with a product key. I was not asked to enter a product key on my laptop.
What is going on here,. anyone know?
I am more than fed up with this product .. but we have to use it.
However, I did find a solution - I installed the SQL Server Developer Edition on my development computer. You know, this is the one that only costs about $50. You can only use it for development, but it is a full version.
When I tried installing Reporting Service after that, it did not ask me for the product key, and it installed successfully. Apparently, it just wants to see a full version of SQL Server.|||Cool!
Just wondering - in ADD or Remove Programs did the CD version of RS install as Microsoft SQL 2000 Reporting Services or Microsoft SQL 2000 Reporting Services Evaluation Edition?
So I wonder why MS makes such a big deal out of getting the production version of RS - especially sinice RS production version only looks for a installed version of SQL because you obviously have two(2) different "keys"
One with the Development Edition
and One for your Server
Interesting!
Best Regards,
joe
sql
No problem -- I was able to install it on our server -- it recognized that we had a qualifying SQL Server installation, and installed Reporting Service.
I wanted to install the client components both on my laptop and my development computer at work, but I was wondering how it would know I was entitled to install, since the qualifying database was on a remote machine. Well, there was no problem on my laptop -- it installed OK. I guess it found what it was looking for.
Now I am trying to install it on my computer at work, and now it is asking for a 25-character product key. Well, the CD did not come with a product key. I was not asked to enter a product key on my laptop.
What is going on here,. anyone know?
I am more than fed up with this product .. but we have to use it.
Good Evening!
You have a least received the CD - I subscribed well over 2 months ago and then again last month and have never received the CD - even though I am in Bangkok and was chaged for shipment....
So since we installed SQL 2005 here I thought I could "backload" the RS in SQL 2005 to SQL 2000 - but forget that - won't happen at least I have not figured out a way after an entire weekend. I was really psyched-up offering the calendar conrols in RS 2005 or (Business Intellingence) to our current users - but when you move an solution project to BI or RS 2005 it converts the RDL and you cannot back-load.
I don't know - but did you try to enter your SQL 2000 key when prompted - because it is 25 bytes long ? I would try that and see what happens... But you would think OK - so I enter a 25 byte key when prompted from the CD of RS - how does the RS CD know if the Key is valid - does it synch with the server?
I am curious how this is resolved - so if you do resolve - will you post back?
Best regards,
Joe
|||Well, I can't enter the SQL 2000 key, because I don't have it. We got our SQL Server through the hosting company from whom we rent the dedicated server, so they are the ones that installed it. I did ask them for the key, but they did not want to give it to me.
However, I did find a solution - I installed the SQL Server Developer Edition on my development computer. You know, this is the one that only costs about $50. You can only use it for development, but it is a full version.
When I tried installing Reporting Service after that, it did not ask me for the product key, and it installed successfully. Apparently, it just wants to see a full version of SQL Server.|||Cool!
Just wondering - in ADD or Remove Programs did the CD version of RS install as Microsoft SQL 2000 Reporting Services or Microsoft SQL 2000 Reporting Services Evaluation Edition?
So I wonder why MS makes such a big deal out of getting the production version of RS - especially sinice RS production version only looks for a installed version of SQL because you obviously have two(2) different "keys"
One with the Development Edition
and One for your Server
Interesting!
Best Regards,
joe
sql
Friday, March 23, 2012
Installing Analysis Services
I installed anaylsis services 6 months after I installed
SQL 2000. Do I need to reinstall the SQL Service Packs?I probably would, also make sure to install the service packs for analysis
services
Ray Higdon MCSE, MCDBA, CCNA
--
"Greg" <anonymous@.discussions.microsoft.com> wrote in message
news:1b7601c3fbfe$5e44d4a0$a101280a@.phx.gbl...
> I installed anaylsis services 6 months after I installed
> SQL 2000. Do I need to reinstall the SQL Service Packs?
SQL 2000. Do I need to reinstall the SQL Service Packs?I probably would, also make sure to install the service packs for analysis
services
Ray Higdon MCSE, MCDBA, CCNA
--
"Greg" <anonymous@.discussions.microsoft.com> wrote in message
news:1b7601c3fbfe$5e44d4a0$a101280a@.phx.gbl...
> I installed anaylsis services 6 months after I installed
> SQL 2000. Do I need to reinstall the SQL Service Packs?
Installing Agent Service
Hi,
I have just installed SQL Server 2005 Express Adv. which I expected to
have the Agent service.
How do I install the agent service and where can I get it from?
Thanks
hi,
WA wrote:
> Hi,
> I have just installed SQL Server 2005 Express Adv. which I expected to
> have the Agent service.
> How do I install the agent service and where can I get it from?
> Thanks
SQLExpress does not feature the SQL Server Agent, so jobs and alerts are not
available as well.. for scheduled "actions" you have to rely on the native
OS scheduler or third party schedulers..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz http://italy.mvps.org
DbaMgr2k ver 0.21.0 - DbaMgr ver 0.65.0 and further SQL Tools
-- remove DMO to reply
I have just installed SQL Server 2005 Express Adv. which I expected to
have the Agent service.
How do I install the agent service and where can I get it from?
Thanks
hi,
WA wrote:
> Hi,
> I have just installed SQL Server 2005 Express Adv. which I expected to
> have the Agent service.
> How do I install the agent service and where can I get it from?
> Thanks
SQLExpress does not feature the SQL Server Agent, so jobs and alerts are not
available as well.. for scheduled "actions" you have to rely on the native
OS scheduler or third party schedulers..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz http://italy.mvps.org
DbaMgr2k ver 0.21.0 - DbaMgr ver 0.65.0 and further SQL Tools
-- remove DMO to reply
Wednesday, March 21, 2012
installed msde database server desktop edition and well...
its sql server 7.0 and im looking for the service network utility and service manager that it didnt come with.. where can i download it?Did you install MSDE 1.0? That is indeed SQL Server 7.0. You should have instead installed MSDE 2000 which is the more recent version and is SQL Server 2000.
Monday, March 19, 2012
Installation SQL Server 2005 Express Edition
My Installation failed for the SQL Server. Is it true that the SQL Server is running only in Windows XP Prof with Service Pack 2.
Thanks!
Hi,That is correct. The software requirements have been explicitly mentioned as Windows XP Service Pack 2 on the download page here.
Regards,
Vikram
Installation sequence
Just want to check whether I have the correct installation sequence...
(1) Windows Server 2003 then updates/service packs
(2) IIS6 then updates/service packs
(3) SQL Server 2000 then updates/service packs
(4) Reporting Services
Is that correct?
Thanks(5) Reporting Services SP1
--
Cheers,
'(' Jeff A. Stucker
\
Business Intelligence
www.criadvantage.com
---
"Keith Macdonald" <keith.macdonald@.mess.doctors.org.uk.nospam> wrote in
message news:1718DAE6-C7AE-4333-B5D6-EB963670124E@.microsoft.com...
> Just want to check whether I have the correct installation sequence...
> (1) Windows Server 2003 then updates/service packs
> (2) IIS6 then updates/service packs
> (3) SQL Server 2000 then updates/service packs
> (4) Reporting Services
> Is that correct?
> Thanks
(1) Windows Server 2003 then updates/service packs
(2) IIS6 then updates/service packs
(3) SQL Server 2000 then updates/service packs
(4) Reporting Services
Is that correct?
Thanks(5) Reporting Services SP1
--
Cheers,
'(' Jeff A. Stucker
\
Business Intelligence
www.criadvantage.com
---
"Keith Macdonald" <keith.macdonald@.mess.doctors.org.uk.nospam> wrote in
message news:1718DAE6-C7AE-4333-B5D6-EB963670124E@.microsoft.com...
> Just want to check whether I have the correct installation sequence...
> (1) Windows Server 2003 then updates/service packs
> (2) IIS6 then updates/service packs
> (3) SQL Server 2000 then updates/service packs
> (4) Reporting Services
> Is that correct?
> Thanks
Installation Question - Service account
Hi All,
We are upgrading from Sql Server Express to SQl Server 2005. As part of the installation process, it is not asking us to specify a service account for various services, and we are not sure what to specify. (This was handled automatically with Express). Any ideas?
Thanks.
Claude.
Hi All,
There was a typo in my original post, it should have read:
We are upgrading from Sql Server Express to SQl Server 2005. As part of the installation process, it is NOW asking us to specify a service account for various services, and we are not sure what to specify. (This was handled automatically with Express). Any ideas?
Thanks.
Claude.
|||Hi Claude,
This service account specifies under what account is this SQL Server instance running.
If your instance might be querying some domain resource, you can specify a domain account. Or you can just select the System Account.
HTH. If this does not answer you question, please feel free to mark it as Not Answered and post your reply. Thanks!
Monday, March 12, 2012
Installation problem: Unable to start service (3) - Error Code: 0x80070003
Hello,
I have Vista x64 and I had been fighting SQL Server for a few days and yesterday I decided for reinstallation. Unfortunately now I am not able to instal the server back!
Each time I got the following error (it refers to SQL Server service):
Code Snippet
<Func Name='LaunchFunction'>
Function=Do_sqlShutDownRANUInstance
<Func Name='GetCAContext'>
<EndFunc Name='GetCAContext' Return='T' GetLastError='203'>
Doing Action: Do_sqlShutDownRANUInstance
PerfTime Start: Do_sqlShutDownRANUInstance : Tue Sep 04 23:32:16 2007
<Func Name='Do_sqlShutDownRANUInstance'>
Service SQLEXPRESS with parameters '' is being started at Tue Sep 04 23:32:16 2007
Unable to start service (3)
Error Code: 0x80070003 (3)
Windows Error Text: System nie mo?e odnale?? okre?lonej ?cie?ki.
Source File Name: sqlsetuplib\service.cpp
Compiler Timestamp: Wed Jun 14 16:29:04 2006
Function Name: sqls::Service::Start
Source Line Number: 316
- Context --
Setting status of unmanaged components and removing unmanaged resources
Error Code: 3
MSI (s) (F4:E4) [23:32:24:490]: I/O on thread 3716 could not be cancelled. Error: 1168
MSI (s) (F4:E4) [23:32:24:493]: I/O on thread 788 could not be cancelled. Error: 1168
MSI (s) (F4:E4) [23:32:24:493]: I/O on thread 2948 could not be cancelled. Error: 1168
MSI (s) (F4:E4) [23:32:24:493]: I/O on thread 4392 could not be cancelled. Error: 1168
MSI (s) (F4:E4) [23:32:24:493]: I/O on thread 5048 could not be cancelled. Error: 1168
MSI (s) (F4:E4) [23:32:24:495]: I/O on thread 4464 could not be cancelled. Error: 1168
MSI (s) (F4:E4) [23:32:24:495]: I/O on thread 4992 could not be cancelled. Error: 1168
MSI (s) (F4:E4) [23:32:24:495]: I/O on thread 4768 could not be cancelled. Error: 1168
MSI (s) (F4:E4) [23:32:24:497]: I/O on thread 3004 could not be cancelled. Error: 1168
MSI (s) (F4!4C) [23:32:24:497]: Product: Microsoft SQL Server 2005 -- Error 29503. The SQL Server service failed to start. For more information, see the SQL Server Books Online topics, "How to: View SQL Server 2005 Setup Log Files" and "Starting SQL Server Manually."
The error is (3) System nie mo?e odnale?? okre?lonej ?cie?ki.
.
Error 29503. The SQL Server service failed to start. For more information, see the SQL Server Books Online topics, "How to: View SQL Server 2005 Setup Log Files" and "Starting SQL Server Manually."
The error is (3) System nie mo?e odnale?? okre?lonej ?cie?ki.
.
<Failure Type='Fatal' Error='3'>
<EndFunc Name='LaunchFunction' Return='3' GetLastError='203'>
MSI (s) (F4:80) [23:32:24:507]: User policy value 'DisableRollback' is 0
MSI (s) (F4:80) [23:32:24:507]: Machine policy value 'DisableRollback' is 0
Action ended 23:32:24: InstallFinalize. Return value 3.
MSI (s) (F4:80) [23:32:24:512]: Executing op: Header(Signature=1397708873,Version=400,Timestamp=925154312,LangId=1033,Platform=0,ScriptType=2,ScriptMajorVersion=21,ScriptMinorVersion=4,ScriptAttributes=1)
MSI (s) (F4:80) [23:32:24:512]: Executing op: DialogInfo(Type=0,Argument=1033)
MSI (s) (F4:80) [23:32:24:513]: Executing op: DialogInfo(Type=1,Argument=Microsoft SQL Server 2005)
MSI (s) (F4:80) [23:32:24:514]: Executing op: RollbackInfo(,RollbackAction=Rollback,RollbackDescription=Rolling back action:,RollbackTemplate=[1],CleanupAction=RollbackCleanup,CleanupDescription=Removing backup files,CleanupTemplate=File: [1])
MSI (s) (F4:80) [23:32:24:516]: Executing op: ActionStart(Name=Do_sqlShutDownRANUInstance.D20239D7_E87C_40C9_9837_E70B8D4882C2,Description=Running action to shutdown instance(Run As Normal User),)
MSI (s) (F4:80) [23:32:24:517]: Executing op: ProductInfo(ProductKey={C3F5DBA5-ABFC-443E-AA60-928223AADF53},ProductName=Microsoft SQL Server 2005,PackageName=sqlrun_sql.msi,Language=1033,Version=151129058,Assignment=1,ObsoleteArg=0,ProductIcon=ARPIcon.ico,PackageMediaPath=\Setup\,PackageCode={08AD0897-0300-4F7D-A3CC-A0CCEDD42E0D},,,InstanceType=1,LUASetting=0,RemoteURTInstalls=0,ProductDeploymentFlags=3)
MSI (s) (F4:80) [23:32:24:518]: Executing op: ActionStart(Name=ProcessComponents,Description=Updating component registration,)
MSI (s) (F4:80) [23:32:24:519]: Executing op: RegOpenKey(Root=-2147483646,Key=SOFTWARE\Microsoft\Windows\CurrentVersion\SharedDLLs,,BinaryType=0,)
MSI (s) (F4:80) [23:32:24:520]: Executing op: RegOpenKey(Root=-2147483646,Key=SOFTWARE\Microsoft\Windows\CurrentVersion\SharedDLLs,,BinaryType=0,)
MSI (s) (F4:80) [23:32:24:520]: Executing op: ComponentUnregister(ComponentId={68C6D258-77E0-11D5-8528-00C04F68155C},ProductKey={C3F5DBA5-ABFC-443E-AA60-928223AADF53},BinaryType=0,)
MSI (s) (F4:80) [23:32:24:520]: Executing op: ComponentUnregister(ComponentId={68C6D257-77E0-11D5-8528-00C04F68155C},ProductKey={C3F5DBA5-ABFC-443E-AA60-928223AADF53},BinaryType=0,)
What can I do solve the problem?
I would run through a manual uninstall procedure:
http://support.microsoft.com/kb/909967
and then try and re-install it.
installation problem in reporting services
Hi, i have problem in installing the reporting services. I'm using a
windows2000 server with service pack4. I also installed the Microsoft .net
and sql 2000 with service pack3a. During the installion of reporting
services, the error appears "the report server requires sql server 2000
with service pack 3a". It seems that he did not recognize the service
pack3a in sequel 2000, although i repeat the procedures of installation
again and again for sequel 2000 and service pack, restart after the
installation but still the problem occurs.
I hope you can help me with my problem.
thanks.
regards,
chubbychai
marygrace.go[AT]digitel.ph
--
Message posted via http://www.sqlmonster.comWhat edition of SQL do you have? What edition of RS do you have? Make sure
that they are supported editions. Use the table on the following to ensure
your setup is correct:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rsinstall/htm/gs_installingrs_v1_8jom.asp
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"chubbychai little via SQLMonster.com" <forum@.SQLMonster.com> wrote in
message news:256222ba6e7e4cc88c8dbdb6d5d585cb@.SQLMonster.com...
> Hi, i have problem in installing the reporting services. I'm using a
> windows2000 server with service pack4. I also installed the Microsoft .net
> and sql 2000 with service pack3a. During the installion of reporting
> services, the error appears "the report server requires sql server 2000
> with service pack 3a". It seems that he did not recognize the service
> pack3a in sequel 2000, although i repeat the procedures of installation
> again and again for sequel 2000 and service pack, restart after the
> installation but still the problem occurs.
> I hope you can help me with my problem.
> thanks.
> regards,
> chubbychai
> marygrace.go[AT]digitel.ph
> --
> Message posted via http://www.sqlmonster.com
windows2000 server with service pack4. I also installed the Microsoft .net
and sql 2000 with service pack3a. During the installion of reporting
services, the error appears "the report server requires sql server 2000
with service pack 3a". It seems that he did not recognize the service
pack3a in sequel 2000, although i repeat the procedures of installation
again and again for sequel 2000 and service pack, restart after the
installation but still the problem occurs.
I hope you can help me with my problem.
thanks.
regards,
chubbychai
marygrace.go[AT]digitel.ph
--
Message posted via http://www.sqlmonster.comWhat edition of SQL do you have? What edition of RS do you have? Make sure
that they are supported editions. Use the table on the following to ensure
your setup is correct:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rsinstall/htm/gs_installingrs_v1_8jom.asp
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"chubbychai little via SQLMonster.com" <forum@.SQLMonster.com> wrote in
message news:256222ba6e7e4cc88c8dbdb6d5d585cb@.SQLMonster.com...
> Hi, i have problem in installing the reporting services. I'm using a
> windows2000 server with service pack4. I also installed the Microsoft .net
> and sql 2000 with service pack3a. During the installion of reporting
> services, the error appears "the report server requires sql server 2000
> with service pack 3a". It seems that he did not recognize the service
> pack3a in sequel 2000, although i repeat the procedures of installation
> again and again for sequel 2000 and service pack, restart after the
> installation but still the problem occurs.
> I hope you can help me with my problem.
> thanks.
> regards,
> chubbychai
> marygrace.go[AT]digitel.ph
> --
> Message posted via http://www.sqlmonster.com
installation problem for SQL 2000 Development Edition
hi all, i dunno should i post it here or not but i cant other place to
post this problem ..
The usernams and password that you specify when you get that message is
the Windows username/password for the SQL Server service account. That is,
the Windows process that runs SQL Server. You can change this after the
installation from the Services node in Computer Management. (Right-click
My Computer, select Manage, find Services, and then the SQL Server Service.
Right-click, Properties and on the second tab, you have log-on information.)
Yes. If you're nervous that the installation will fail, you can choose
LocalSystem and then change to a normal Windows account after the
installation.
I usually suggest that Enterprise manager be used to change the SQL Server
service account after installation because EM will grant additional advanced
user rights that don't get assigned with the Computer Management method.
The advanced rights are needed for functionality like changing security
context to the proxy account and using AWE. The permissions (documented in
the BOL) can be granted manually but it's more work.
>
The usernams and password that you specify when you get that message is
the Windows username/password for the SQL Server service account. That is,
the Windows process that runs SQL Server. You can change this after the
installation from the Services node in Computer Management. (Right-click
My Computer, select Manage, find Services, and then the SQL Server
Service.
Right-click, Properties and on the second tab, you have log-on
information.)
>
If you know that the account is alright, then I would just ignore the
message and move on. I believe, I've seen it when I've installed SQL
Server
as well.
>
>
>
>
--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
>
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||Dan Guzman (guzmanda@.nospam-online.sbcglobal.net) writes:
Interesting, I didn't know that. In fact, I was not even aware of that
you could change the service account through EM. I guess that shows how
much that I use Enterprise Manager. :-)
hi dan.. thanks for ur help but can u tell me more specified how to did
it with the EM ?? i finding whole day there but i cant find the security
part that u mentioning here..:( sorry need ur help again...
Right-click the server node in EM, select Properties. Go the Security tab.
The lower third is for changing the service account.
post this problem ..
i am using windows XP professional service pack 1 .. when i try to
install MS SQL 2000 Developer Edition to my system, it can works fine
except when i try to set the user name and password then it promp out
this msg
error msg : setup cannot verify/grant logon as service right to the sql
server logon account : 1332(0X534)
can any 1 help me with this? if i choose windows authentichal password
then can run, i cannot set the password
--
qintian
----------------------
qintian's Profile: http://www.dbtalk.net/m671
View this thread: http://www.dbtalk.net/t325996qintian (qintian.2cm19z@.no-mx.forums.yourdomain.com.au) writes:
Quote:
Originally Posted by
hi all, i dunno should i post it here or not but i cant other place to
post this problem ..
>
i am using windows XP professional service pack 1 .. when i try to
install MS SQL 2000 Developer Edition to my system, it can works fine
except when i try to set the user name and password then it promp out
this msg
>
error msg : setup cannot verify/grant logon as service right to the sql
server logon account : 1332(0X534)
>
can any 1 help me with this? if i choose windows authentichal password
then can run, i cannot set the password
The usernams and password that you specify when you get that message is
the Windows username/password for the SQL Server service account. That is,
the Windows process that runs SQL Server. You can change this after the
installation from the Services node in Computer Management. (Right-click
My Computer, select Manage, find Services, and then the SQL Server Service.
Right-click, Properties and on the second tab, you have log-on information.)
If you know that the account is alright, then I would just ignore the
message and move on. I believe, I've seen it when I've installed SQL Server
as well.
--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||thank you Erland Sommarskog,
so the time when i installing the MS SQL . i can juz simply choose a
log on mathod? then after that change it by your way? :confused:
--
qintian
----------------------
qintian's Profile: http://www.dbtalk.net/m671
View this thread: http://www.dbtalk.net/t325996|||qintian (qintian.2cnvy0@.no-mx.forums.yourdomain.com.au) writes:
Quote:
Originally Posted by
thank you Erland Sommarskog,
>
so the time when i installing the MS SQL . i can juz simply choose a
log on mathod? then after that change it by your way? :confused:
Yes. If you're nervous that the installation will fail, you can choose
LocalSystem and then change to a normal Windows account after the
installation.
You can also change the choice of allowing SQL Server authentication after
the installation as well. Note that this concerns logging into SQL Server
itself.
--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||You can change this after the
Quote:
Originally Posted by
installation from the Services node in Computer Management.
I usually suggest that Enterprise manager be used to change the SQL Server
service account after installation because EM will grant additional advanced
user rights that don't get assigned with the Computer Management method.
The advanced rights are needed for functionality like changing security
context to the proxy account and using AWE. The permissions (documented in
the BOL) can be granted manually but it's more work.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Erland Sommarskog" <esquel@.sommarskog.sewrote in message
news:Xns9821F12DE4F00Yazorman@.127.0.0.1...
Quote:
Originally Posted by
qintian (qintian.2cm19z@.no-mx.forums.yourdomain.com.au) writes:
Quote:
Originally Posted by
>hi all, i dunno should i post it here or not but i cant other place to
>post this problem ..
>>
>i am using windows XP professional service pack 1 .. when i try to
>install MS SQL 2000 Developer Edition to my system, it can works fine
>except when i try to set the user name and password then it promp out
>this msg
>>
>error msg : setup cannot verify/grant logon as service right to the sql
>server logon account : 1332(0X534)
>>
>can any 1 help me with this? if i choose windows authentichal password
>then can run, i cannot set the password
>
The usernams and password that you specify when you get that message is
the Windows username/password for the SQL Server service account. That is,
the Windows process that runs SQL Server. You can change this after the
installation from the Services node in Computer Management. (Right-click
My Computer, select Manage, find Services, and then the SQL Server
Service.
Right-click, Properties and on the second tab, you have log-on
information.)
>
If you know that the account is alright, then I would just ignore the
message and move on. I believe, I've seen it when I've installed SQL
Server
as well.
>
>
>
>
--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
>
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||Dan Guzman (guzmanda@.nospam-online.sbcglobal.net) writes:
Quote:
Originally Posted by
I usually suggest that Enterprise manager be used to change the SQL
Server service account after installation because EM will grant
additional advanced user rights that don't get assigned with the
Computer Management method. The advanced rights are needed for
functionality like changing security context to the proxy account and
using AWE. The permissions (documented in the BOL) can be granted
manually but it's more work.
Interesting, I didn't know that. In fact, I was not even aware of that
you could change the service account through EM. I guess that shows how
much that I use Enterprise Manager. :-)
Thanks Dan for the information.
--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||Dan Guzman Wrote:
Quote:
Originally Posted by
I usually suggest that Enterprise manager be used to change the SQL
Server
service account after installation because EM will grant additional
advanced
user rights that don't get assigned with the Computer Management
method.
The advanced rights are needed for functionality like changing
security
context to the proxy account and using AWE. The permissions
(documented in
the BOL) can be granted manually but it's more work.
>
--
Hope this helps.
>
Dan Guzman
SQL Server MVP
>
>
hi dan.. thanks for ur help but can u tell me more specified how to did
it with the EM ?? i finding whole day there but i cant find the security
part that u mentioning here..:( sorry need ur help again...
--
qintian
----------------------
qintian's Profile: http://www.dbtalk.net/m671
View this thread: http://www.dbtalk.net/t325996|||qintian (qintian.2cpte2@.no-mx.forums.yourdomain.com.au) writes:
Quote:
Originally Posted by
hi dan.. thanks for ur help but can u tell me more specified how to did
it with the EM ?? i finding whole day there but i cant find the security
part that u mentioning here..:( sorry need ur help again...
Right-click the server node in EM, select Properties. Go the Security tab.
The lower third is for changing the service account.
--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx
Installation Problem -- SQL Server 2005 Standard & Windows XP Professional Service Pack 2
Hi
I am trying to install SQL Server 2005 Standard on my laptop, which has Windows XP Professional with Service Pack 2. I could not able to install properly and i am getting error always. i tried whatever the people mentioned in Google, but I could not able to fix the problem. please some one can help my problem.
Here is the Error I am getting always "The certificate chain was issued by an authority that is not trusted" . I am trying for past few days i could not able to resolve.
please help
Note : I have SQL Server 2000 Client installed in my laptop. this is my development machine
Thanks
Paddy
Here is the Error message from Summary.txt
Product : SQL Server Database Services
Error : SQL Server Setup could not connect to the database service for server configuration. The error was: [Microsoft][SQL Native Client]SSL Provider: The certificate chain was issued by an authority that is not trusted.
Refer to server error logs and setup logs for more information. For details on how to view setup logs, see "How to View Setup Log Files" in SQL Server Books Online.
--
Machine : W4102762
Product : Microsoft SQL Server 2005
Product Version : 9.00.1399.06
Install : Failed
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_w4102762_SQL.log
Last Action : InstallFinalize
Error String : SQL Server Setup could not connect to the database service for server configuration. The error was: {Microsoft}{SQL Native Client}SSL Provider: The certificate chain was issued by an authority that is not trusted.
Error Number : 29515
--
Machine : W4102762
Product : SQLXML4
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_w4102762_SQLXML4_1.log
--
SQL Server Setup failed. For more information, review the Setup log file in %ProgramFiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt.
Please post this question where SQL Server Database Connectivity and Engine issues are discussed. You have better chance of getting an answer in those forums than Setup forum.
thanks
Raja
Installation Problem -- SQL Server 2005 Standard & Windows XP Professional Service Pack 2
Hi
I am trying to install SQL Server 2005 Standard on my laptop, which has
Windows XP Professional with Service Pack 2. I could not able to
install properly and i am getting error always. i tried whatever the
people mentioned in Google, but I could not able to fix the problem.
please some one can help my problem.
Here is the Error I am getting always "The certificate chain was issued
by an authority that is not trusted" . I am trying for past few days i
could not able to resolve.
please help
Note : I have SQL Server 2000 Client installed in my laptop. this is my
development machine
Thanks
Paddy
Here is the Error message from Summary.txt
Product : SQL Server Database Services
Error : SQL Server Setup could not connect to the database
service for server configuration. The error was: [Microsoft][SQL Native
Client]SSL Provider: The certificate chain was issued by an authority
that is not trusted.
Refer to server error logs and setup logs for more information. For
details on how to view setup logs, see "How to View Setup Log Files" in
SQL Server Books Online.
----
Machine : W4102762
Product : Microsoft SQL Server 2005
Product Version : 9.00.1399.06
Install : Failed
Log File : C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0001_w4102762_SQL.log
Last Action : InstallFinalize
Error String : SQL Server Setup could not connect to the database
service for server configuration. The error was: {Microsoft}{SQL Native
Client}SSL Provider: The certificate chain was issued by an authority
that is not trusted.
Error Number : 29515
----
Machine : W4102762
Product : SQLXML4
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0001_w4102762_SQLXML4_1.log
----
SQL Server Setup failed. For more information, review the Setup log
file in %ProgramFiles%\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Summary.txt.Hi
Do you have SSL enabled and have you tried removing it before installing?
John
"Padmanaban" wrote:
> Hi
> I am trying to install SQL Server 2005 Standard on my laptop, which has
> Windows XP Professional with Service Pack 2. I could not able to
> install properly and i am getting error always. i tried whatever the
> people mentioned in Google, but I could not able to fix the problem.
> please some one can help my problem.
> Here is the Error I am getting always "The certificate chain was issued
> by an authority that is not trusted" . I am trying for past few days i
> could not able to resolve.
> please help
> Note : I have SQL Server 2000 Client installed in my laptop. this is my
> development machine
> Thanks
> Paddy
>
> Here is the Error message from Summary.txt
>
> Product : SQL Server Database Services
> Error : SQL Server Setup could not connect to the database
> service for server configuration. The error was: [Microsoft][SQL Native
> Client]SSL Provider: The certificate chain was issued by an authority
> that is not trusted.
> Refer to server error logs and setup logs for more information. For
> details on how to view setup logs, see "How to View Setup Log Files" in
> SQL Server Books Online.
>
> ----
> Machine : W4102762
> Product : Microsoft SQL Server 2005
> Product Version : 9.00.1399.06
> Install : Failed
> Log File : C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Files\SQLSetup0001_w4102762_SQL.log
> Last Action : InstallFinalize
> Error String : SQL Server Setup could not connect to the database
> service for server configuration. The error was: {Microsoft}{SQL Native
> Client}SSL Provider: The certificate chain was issued by an authority
> that is not trusted.
> Error Number : 29515
> ----
> Machine : W4102762
> Product : SQLXML4
> Product Version : 9.00.1399.06
> Install : Successful
> Log File : C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Files\SQLSetup0001_w4102762_SQLXML4_1.log
> ----
>
> SQL Server Setup failed. For more information, review the Setup log
> file in %ProgramFiles%\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Summary.txt.
>|||Thanks John Bell
I dont have SSL in my Laptop, Do I have to enable SSL in my laptop?.
Is it possible to install SQL Server 2005 Standard without SSL. I dont
think our IT guys going to allow installing SSL in laptop (my work
development system)
Please help me
Thanks
Paddy
John Bell wrote:
> Hi
> Do you have SSL enabled and have you tried removing it before installing?
> John
> "Padmanaban" wrote:
> > Hi
> >
> > I am trying to install SQL Server 2005 Standard on my laptop, which has
> > Windows XP Professional with Service Pack 2. I could not able to
> > install properly and i am getting error always. i tried whatever the
> > people mentioned in Google, but I could not able to fix the problem.
> > please some one can help my problem.
> >
> > Here is the Error I am getting always "The certificate chain was issued
> > by an authority that is not trusted" . I am trying for past few days i
> > could not able to resolve.
> >
> > please help
> >
> > Note : I have SQL Server 2000 Client installed in my laptop. this is my
> > development machine
> >
> > Thanks
> >
> > Paddy
> >
> >
> > Here is the Error message from Summary.txt
> >
> >
> >
> > Product : SQL Server Database Services
> > Error : SQL Server Setup could not connect to the database
> > service for server configuration. The error was: [Microsoft][SQL Native
> > Client]SSL Provider: The certificate chain was issued by an authority
> > that is not trusted.
> > Refer to server error logs and setup logs for more information. For
> > details on how to view setup logs, see "How to View Setup Log Files" in
> > SQL Server Books Online.
> >
> >
> > ----
> > Machine : W4102762
> > Product : Microsoft SQL Server 2005
> > Product Version : 9.00.1399.06
> > Install : Failed
> > Log File : C:\Program Files\Microsoft SQL Server\90\Setup
> > Bootstrap\LOG\Files\SQLSetup0001_w4102762_SQL.log
> > Last Action : InstallFinalize
> > Error String : SQL Server Setup could not connect to the database
> > service for server configuration. The error was: {Microsoft}{SQL Native
> > Client}SSL Provider: The certificate chain was issued by an authority
> > that is not trusted.
> > Error Number : 29515
> > ----
> >
> > Machine : W4102762
> > Product : SQLXML4
> > Product Version : 9.00.1399.06
> > Install : Successful
> > Log File : C:\Program Files\Microsoft SQL Server\90\Setup
> > Bootstrap\LOG\Files\SQLSetup0001_w4102762_SQLXML4_1.log
> > ----
> >
> >
> > SQL Server Setup failed. For more information, review the Setup log
> > file in %ProgramFiles%\Microsoft SQL Server\90\Setup
> > Bootstrap\LOG\Summary.txt.
> >
> >|||Hi
SSL is not necessary, but as your error talks about certificates it is one
of the most likely uses for them.
Has this media been used to install on any other machines?
John
"Padmanaban" wrote:
> Thanks John Bell
> I dont have SSL in my Laptop, Do I have to enable SSL in my laptop?.
> Is it possible to install SQL Server 2005 Standard without SSL. I dont
> think our IT guys going to allow installing SSL in laptop (my work
> development system)
> Please help me
> Thanks
> Paddy
> John Bell wrote:
> > Hi
> >
> > Do you have SSL enabled and have you tried removing it before installing?
> >
> > John
> >
> > "Padmanaban" wrote:
> >
> > > Hi
> > >
> > > I am trying to install SQL Server 2005 Standard on my laptop, which has
> > > Windows XP Professional with Service Pack 2. I could not able to
> > > install properly and i am getting error always. i tried whatever the
> > > people mentioned in Google, but I could not able to fix the problem.
> > > please some one can help my problem.
> > >
> > > Here is the Error I am getting always "The certificate chain was issued
> > > by an authority that is not trusted" . I am trying for past few days i
> > > could not able to resolve.
> > >
> > > please help
> > >
> > > Note : I have SQL Server 2000 Client installed in my laptop. this is my
> > > development machine
> > >
> > > Thanks
> > >
> > > Paddy
> > >
> > >
> > > Here is the Error message from Summary.txt
> > >
> > >
> > >
> > > Product : SQL Server Database Services
> > > Error : SQL Server Setup could not connect to the database
> > > service for server configuration. The error was: [Microsoft][SQL Native
> > > Client]SSL Provider: The certificate chain was issued by an authority
> > > that is not trusted.
> > > Refer to server error logs and setup logs for more information. For
> > > details on how to view setup logs, see "How to View Setup Log Files" in
> > > SQL Server Books Online.
> > >
> > >
> > > ----
> > > Machine : W4102762
> > > Product : Microsoft SQL Server 2005
> > > Product Version : 9.00.1399.06
> > > Install : Failed
> > > Log File : C:\Program Files\Microsoft SQL Server\90\Setup
> > > Bootstrap\LOG\Files\SQLSetup0001_w4102762_SQL.log
> > > Last Action : InstallFinalize
> > > Error String : SQL Server Setup could not connect to the database
> > > service for server configuration. The error was: {Microsoft}{SQL Native
> > > Client}SSL Provider: The certificate chain was issued by an authority
> > > that is not trusted.
> > > Error Number : 29515
> > > ----
> > >
> > > Machine : W4102762
> > > Product : SQLXML4
> > > Product Version : 9.00.1399.06
> > > Install : Successful
> > > Log File : C:\Program Files\Microsoft SQL Server\90\Setup
> > > Bootstrap\LOG\Files\SQLSetup0001_w4102762_SQLXML4_1.log
> > > ----
> > >
> > >
> > > SQL Server Setup failed. For more information, review the Setup log
> > > file in %ProgramFiles%\Microsoft SQL Server\90\Setup
> > > Bootstrap\LOG\Summary.txt.
> > >
> > >
>|||Hi,
No, i created CD from MSDN subcription and using
Thanks
Paddy
John Bell wrote:
> Hi
> SSL is not necessary, but as your error talks about certificates it is one
> of the most likely uses for them.
> Has this media been used to install on any other machines?
> John
> "Padmanaban" wrote:
> > Thanks John Bell
> >
> > I dont have SSL in my Laptop, Do I have to enable SSL in my laptop?.
> >
> > Is it possible to install SQL Server 2005 Standard without SSL. I dont
> > think our IT guys going to allow installing SSL in laptop (my work
> > development system)
> >
> > Please help me
> >
> > Thanks
> >
> > Paddy
> >
> > John Bell wrote:
> > > Hi
> > >
> > > Do you have SSL enabled and have you tried removing it before installing?
> > >
> > > John
> > >
> > > "Padmanaban" wrote:
> > >
> > > > Hi
> > > >
> > > > I am trying to install SQL Server 2005 Standard on my laptop, which has
> > > > Windows XP Professional with Service Pack 2. I could not able to
> > > > install properly and i am getting error always. i tried whatever the
> > > > people mentioned in Google, but I could not able to fix the problem.
> > > > please some one can help my problem.
> > > >
> > > > Here is the Error I am getting always "The certificate chain was issued
> > > > by an authority that is not trusted" . I am trying for past few days i
> > > > could not able to resolve.
> > > >
> > > > please help
> > > >
> > > > Note : I have SQL Server 2000 Client installed in my laptop. this is my
> > > > development machine
> > > >
> > > > Thanks
> > > >
> > > > Paddy
> > > >
> > > >
> > > > Here is the Error message from Summary.txt
> > > >
> > > >
> > > >
> > > > Product : SQL Server Database Services
> > > > Error : SQL Server Setup could not connect to the database
> > > > service for server configuration. The error was: [Microsoft][SQL Native
> > > > Client]SSL Provider: The certificate chain was issued by an authority
> > > > that is not trusted.
> > > > Refer to server error logs and setup logs for more information. For
> > > > details on how to view setup logs, see "How to View Setup Log Files" in
> > > > SQL Server Books Online.
> > > >
> > > >
> > > > ----
> > > > Machine : W4102762
> > > > Product : Microsoft SQL Server 2005
> > > > Product Version : 9.00.1399.06
> > > > Install : Failed
> > > > Log File : C:\Program Files\Microsoft SQL Server\90\Setup
> > > > Bootstrap\LOG\Files\SQLSetup0001_w4102762_SQL.log
> > > > Last Action : InstallFinalize
> > > > Error String : SQL Server Setup could not connect to the database
> > > > service for server configuration. The error was: {Microsoft}{SQL Native
> > > > Client}SSL Provider: The certificate chain was issued by an authority
> > > > that is not trusted.
> > > > Error Number : 29515
> > > > ----
> > > >
> > > > Machine : W4102762
> > > > Product : SQLXML4
> > > > Product Version : 9.00.1399.06
> > > > Install : Successful
> > > > Log File : C:\Program Files\Microsoft SQL Server\90\Setup
> > > > Bootstrap\LOG\Files\SQLSetup0001_w4102762_SQLXML4_1.log
> > > > ----
> > > >
> > > >
> > > > SQL Server Setup failed. For more information, review the Setup log
> > > > file in %ProgramFiles%\Microsoft SQL Server\90\Setup
> > > > Bootstrap\LOG\Summary.txt.
> > > >
> > > >
> >
> >|||Hi
It may be worth trying to install on another pc to see if the error occurs,
or possibly download the non-iso version.
John
"Padmanaban" wrote:
> Hi,
> No, i created CD from MSDN subcription and using
>
> Thanks
> Paddy
>
> John Bell wrote:
> > Hi
> >
> > SSL is not necessary, but as your error talks about certificates it is one
> > of the most likely uses for them.
> >
> > Has this media been used to install on any other machines?
> >
> > John
> >
> > "Padmanaban" wrote:
> >
> > > Thanks John Bell
> > >
> > > I dont have SSL in my Laptop, Do I have to enable SSL in my laptop?.
> > >
> > > Is it possible to install SQL Server 2005 Standard without SSL. I dont
> > > think our IT guys going to allow installing SSL in laptop (my work
> > > development system)
> > >
> > > Please help me
> > >
> > > Thanks
> > >
> > > Paddy
> > >
> > > John Bell wrote:
> > > > Hi
> > > >
> > > > Do you have SSL enabled and have you tried removing it before installing?
> > > >
> > > > John
> > > >
> > > > "Padmanaban" wrote:
> > > >
> > > > > Hi
> > > > >
> > > > > I am trying to install SQL Server 2005 Standard on my laptop, which has
> > > > > Windows XP Professional with Service Pack 2. I could not able to
> > > > > install properly and i am getting error always. i tried whatever the
> > > > > people mentioned in Google, but I could not able to fix the problem.
> > > > > please some one can help my problem.
> > > > >
> > > > > Here is the Error I am getting always "The certificate chain was issued
> > > > > by an authority that is not trusted" . I am trying for past few days i
> > > > > could not able to resolve.
> > > > >
> > > > > please help
> > > > >
> > > > > Note : I have SQL Server 2000 Client installed in my laptop. this is my
> > > > > development machine
> > > > >
> > > > > Thanks
> > > > >
> > > > > Paddy
> > > > >
> > > > >
> > > > > Here is the Error message from Summary.txt
> > > > >
> > > > >
> > > > >
> > > > > Product : SQL Server Database Services
> > > > > Error : SQL Server Setup could not connect to the database
> > > > > service for server configuration. The error was: [Microsoft][SQL Native
> > > > > Client]SSL Provider: The certificate chain was issued by an authority
> > > > > that is not trusted.
> > > > > Refer to server error logs and setup logs for more information. For
> > > > > details on how to view setup logs, see "How to View Setup Log Files" in
> > > > > SQL Server Books Online.
> > > > >
> > > > >
> > > > > ----
> > > > > Machine : W4102762
> > > > > Product : Microsoft SQL Server 2005
> > > > > Product Version : 9.00.1399.06
> > > > > Install : Failed
> > > > > Log File : C:\Program Files\Microsoft SQL Server\90\Setup
> > > > > Bootstrap\LOG\Files\SQLSetup0001_w4102762_SQL.log
> > > > > Last Action : InstallFinalize
> > > > > Error String : SQL Server Setup could not connect to the database
> > > > > service for server configuration. The error was: {Microsoft}{SQL Native
> > > > > Client}SSL Provider: The certificate chain was issued by an authority
> > > > > that is not trusted.
> > > > > Error Number : 29515
> > > > > ----
> > > > >
> > > > > Machine : W4102762
> > > > > Product : SQLXML4
> > > > > Product Version : 9.00.1399.06
> > > > > Install : Successful
> > > > > Log File : C:\Program Files\Microsoft SQL Server\90\Setup
> > > > > Bootstrap\LOG\Files\SQLSetup0001_w4102762_SQLXML4_1.log
> > > > > ----
> > > > >
> > > > >
> > > > > SQL Server Setup failed. For more information, review the Setup log
> > > > > file in %ProgramFiles%\Microsoft SQL Server\90\Setup
> > > > > Bootstrap\LOG\Summary.txt.
> > > > >
> > > > >
> > >
> > >
>
I am trying to install SQL Server 2005 Standard on my laptop, which has
Windows XP Professional with Service Pack 2. I could not able to
install properly and i am getting error always. i tried whatever the
people mentioned in Google, but I could not able to fix the problem.
please some one can help my problem.
Here is the Error I am getting always "The certificate chain was issued
by an authority that is not trusted" . I am trying for past few days i
could not able to resolve.
please help
Note : I have SQL Server 2000 Client installed in my laptop. this is my
development machine
Thanks
Paddy
Here is the Error message from Summary.txt
Product : SQL Server Database Services
Error : SQL Server Setup could not connect to the database
service for server configuration. The error was: [Microsoft][SQL Native
Client]SSL Provider: The certificate chain was issued by an authority
that is not trusted.
Refer to server error logs and setup logs for more information. For
details on how to view setup logs, see "How to View Setup Log Files" in
SQL Server Books Online.
----
Machine : W4102762
Product : Microsoft SQL Server 2005
Product Version : 9.00.1399.06
Install : Failed
Log File : C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0001_w4102762_SQL.log
Last Action : InstallFinalize
Error String : SQL Server Setup could not connect to the database
service for server configuration. The error was: {Microsoft}{SQL Native
Client}SSL Provider: The certificate chain was issued by an authority
that is not trusted.
Error Number : 29515
----
Machine : W4102762
Product : SQLXML4
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0001_w4102762_SQLXML4_1.log
----
SQL Server Setup failed. For more information, review the Setup log
file in %ProgramFiles%\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Summary.txt.Hi
Do you have SSL enabled and have you tried removing it before installing?
John
"Padmanaban" wrote:
> Hi
> I am trying to install SQL Server 2005 Standard on my laptop, which has
> Windows XP Professional with Service Pack 2. I could not able to
> install properly and i am getting error always. i tried whatever the
> people mentioned in Google, but I could not able to fix the problem.
> please some one can help my problem.
> Here is the Error I am getting always "The certificate chain was issued
> by an authority that is not trusted" . I am trying for past few days i
> could not able to resolve.
> please help
> Note : I have SQL Server 2000 Client installed in my laptop. this is my
> development machine
> Thanks
> Paddy
>
> Here is the Error message from Summary.txt
>
> Product : SQL Server Database Services
> Error : SQL Server Setup could not connect to the database
> service for server configuration. The error was: [Microsoft][SQL Native
> Client]SSL Provider: The certificate chain was issued by an authority
> that is not trusted.
> Refer to server error logs and setup logs for more information. For
> details on how to view setup logs, see "How to View Setup Log Files" in
> SQL Server Books Online.
>
> ----
> Machine : W4102762
> Product : Microsoft SQL Server 2005
> Product Version : 9.00.1399.06
> Install : Failed
> Log File : C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Files\SQLSetup0001_w4102762_SQL.log
> Last Action : InstallFinalize
> Error String : SQL Server Setup could not connect to the database
> service for server configuration. The error was: {Microsoft}{SQL Native
> Client}SSL Provider: The certificate chain was issued by an authority
> that is not trusted.
> Error Number : 29515
> ----
> Machine : W4102762
> Product : SQLXML4
> Product Version : 9.00.1399.06
> Install : Successful
> Log File : C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Files\SQLSetup0001_w4102762_SQLXML4_1.log
> ----
>
> SQL Server Setup failed. For more information, review the Setup log
> file in %ProgramFiles%\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Summary.txt.
>|||Thanks John Bell
I dont have SSL in my Laptop, Do I have to enable SSL in my laptop?.
Is it possible to install SQL Server 2005 Standard without SSL. I dont
think our IT guys going to allow installing SSL in laptop (my work
development system)
Please help me
Thanks
Paddy
John Bell wrote:
> Hi
> Do you have SSL enabled and have you tried removing it before installing?
> John
> "Padmanaban" wrote:
> > Hi
> >
> > I am trying to install SQL Server 2005 Standard on my laptop, which has
> > Windows XP Professional with Service Pack 2. I could not able to
> > install properly and i am getting error always. i tried whatever the
> > people mentioned in Google, but I could not able to fix the problem.
> > please some one can help my problem.
> >
> > Here is the Error I am getting always "The certificate chain was issued
> > by an authority that is not trusted" . I am trying for past few days i
> > could not able to resolve.
> >
> > please help
> >
> > Note : I have SQL Server 2000 Client installed in my laptop. this is my
> > development machine
> >
> > Thanks
> >
> > Paddy
> >
> >
> > Here is the Error message from Summary.txt
> >
> >
> >
> > Product : SQL Server Database Services
> > Error : SQL Server Setup could not connect to the database
> > service for server configuration. The error was: [Microsoft][SQL Native
> > Client]SSL Provider: The certificate chain was issued by an authority
> > that is not trusted.
> > Refer to server error logs and setup logs for more information. For
> > details on how to view setup logs, see "How to View Setup Log Files" in
> > SQL Server Books Online.
> >
> >
> > ----
> > Machine : W4102762
> > Product : Microsoft SQL Server 2005
> > Product Version : 9.00.1399.06
> > Install : Failed
> > Log File : C:\Program Files\Microsoft SQL Server\90\Setup
> > Bootstrap\LOG\Files\SQLSetup0001_w4102762_SQL.log
> > Last Action : InstallFinalize
> > Error String : SQL Server Setup could not connect to the database
> > service for server configuration. The error was: {Microsoft}{SQL Native
> > Client}SSL Provider: The certificate chain was issued by an authority
> > that is not trusted.
> > Error Number : 29515
> > ----
> >
> > Machine : W4102762
> > Product : SQLXML4
> > Product Version : 9.00.1399.06
> > Install : Successful
> > Log File : C:\Program Files\Microsoft SQL Server\90\Setup
> > Bootstrap\LOG\Files\SQLSetup0001_w4102762_SQLXML4_1.log
> > ----
> >
> >
> > SQL Server Setup failed. For more information, review the Setup log
> > file in %ProgramFiles%\Microsoft SQL Server\90\Setup
> > Bootstrap\LOG\Summary.txt.
> >
> >|||Hi
SSL is not necessary, but as your error talks about certificates it is one
of the most likely uses for them.
Has this media been used to install on any other machines?
John
"Padmanaban" wrote:
> Thanks John Bell
> I dont have SSL in my Laptop, Do I have to enable SSL in my laptop?.
> Is it possible to install SQL Server 2005 Standard without SSL. I dont
> think our IT guys going to allow installing SSL in laptop (my work
> development system)
> Please help me
> Thanks
> Paddy
> John Bell wrote:
> > Hi
> >
> > Do you have SSL enabled and have you tried removing it before installing?
> >
> > John
> >
> > "Padmanaban" wrote:
> >
> > > Hi
> > >
> > > I am trying to install SQL Server 2005 Standard on my laptop, which has
> > > Windows XP Professional with Service Pack 2. I could not able to
> > > install properly and i am getting error always. i tried whatever the
> > > people mentioned in Google, but I could not able to fix the problem.
> > > please some one can help my problem.
> > >
> > > Here is the Error I am getting always "The certificate chain was issued
> > > by an authority that is not trusted" . I am trying for past few days i
> > > could not able to resolve.
> > >
> > > please help
> > >
> > > Note : I have SQL Server 2000 Client installed in my laptop. this is my
> > > development machine
> > >
> > > Thanks
> > >
> > > Paddy
> > >
> > >
> > > Here is the Error message from Summary.txt
> > >
> > >
> > >
> > > Product : SQL Server Database Services
> > > Error : SQL Server Setup could not connect to the database
> > > service for server configuration. The error was: [Microsoft][SQL Native
> > > Client]SSL Provider: The certificate chain was issued by an authority
> > > that is not trusted.
> > > Refer to server error logs and setup logs for more information. For
> > > details on how to view setup logs, see "How to View Setup Log Files" in
> > > SQL Server Books Online.
> > >
> > >
> > > ----
> > > Machine : W4102762
> > > Product : Microsoft SQL Server 2005
> > > Product Version : 9.00.1399.06
> > > Install : Failed
> > > Log File : C:\Program Files\Microsoft SQL Server\90\Setup
> > > Bootstrap\LOG\Files\SQLSetup0001_w4102762_SQL.log
> > > Last Action : InstallFinalize
> > > Error String : SQL Server Setup could not connect to the database
> > > service for server configuration. The error was: {Microsoft}{SQL Native
> > > Client}SSL Provider: The certificate chain was issued by an authority
> > > that is not trusted.
> > > Error Number : 29515
> > > ----
> > >
> > > Machine : W4102762
> > > Product : SQLXML4
> > > Product Version : 9.00.1399.06
> > > Install : Successful
> > > Log File : C:\Program Files\Microsoft SQL Server\90\Setup
> > > Bootstrap\LOG\Files\SQLSetup0001_w4102762_SQLXML4_1.log
> > > ----
> > >
> > >
> > > SQL Server Setup failed. For more information, review the Setup log
> > > file in %ProgramFiles%\Microsoft SQL Server\90\Setup
> > > Bootstrap\LOG\Summary.txt.
> > >
> > >
>|||Hi,
No, i created CD from MSDN subcription and using
Thanks
Paddy
John Bell wrote:
> Hi
> SSL is not necessary, but as your error talks about certificates it is one
> of the most likely uses for them.
> Has this media been used to install on any other machines?
> John
> "Padmanaban" wrote:
> > Thanks John Bell
> >
> > I dont have SSL in my Laptop, Do I have to enable SSL in my laptop?.
> >
> > Is it possible to install SQL Server 2005 Standard without SSL. I dont
> > think our IT guys going to allow installing SSL in laptop (my work
> > development system)
> >
> > Please help me
> >
> > Thanks
> >
> > Paddy
> >
> > John Bell wrote:
> > > Hi
> > >
> > > Do you have SSL enabled and have you tried removing it before installing?
> > >
> > > John
> > >
> > > "Padmanaban" wrote:
> > >
> > > > Hi
> > > >
> > > > I am trying to install SQL Server 2005 Standard on my laptop, which has
> > > > Windows XP Professional with Service Pack 2. I could not able to
> > > > install properly and i am getting error always. i tried whatever the
> > > > people mentioned in Google, but I could not able to fix the problem.
> > > > please some one can help my problem.
> > > >
> > > > Here is the Error I am getting always "The certificate chain was issued
> > > > by an authority that is not trusted" . I am trying for past few days i
> > > > could not able to resolve.
> > > >
> > > > please help
> > > >
> > > > Note : I have SQL Server 2000 Client installed in my laptop. this is my
> > > > development machine
> > > >
> > > > Thanks
> > > >
> > > > Paddy
> > > >
> > > >
> > > > Here is the Error message from Summary.txt
> > > >
> > > >
> > > >
> > > > Product : SQL Server Database Services
> > > > Error : SQL Server Setup could not connect to the database
> > > > service for server configuration. The error was: [Microsoft][SQL Native
> > > > Client]SSL Provider: The certificate chain was issued by an authority
> > > > that is not trusted.
> > > > Refer to server error logs and setup logs for more information. For
> > > > details on how to view setup logs, see "How to View Setup Log Files" in
> > > > SQL Server Books Online.
> > > >
> > > >
> > > > ----
> > > > Machine : W4102762
> > > > Product : Microsoft SQL Server 2005
> > > > Product Version : 9.00.1399.06
> > > > Install : Failed
> > > > Log File : C:\Program Files\Microsoft SQL Server\90\Setup
> > > > Bootstrap\LOG\Files\SQLSetup0001_w4102762_SQL.log
> > > > Last Action : InstallFinalize
> > > > Error String : SQL Server Setup could not connect to the database
> > > > service for server configuration. The error was: {Microsoft}{SQL Native
> > > > Client}SSL Provider: The certificate chain was issued by an authority
> > > > that is not trusted.
> > > > Error Number : 29515
> > > > ----
> > > >
> > > > Machine : W4102762
> > > > Product : SQLXML4
> > > > Product Version : 9.00.1399.06
> > > > Install : Successful
> > > > Log File : C:\Program Files\Microsoft SQL Server\90\Setup
> > > > Bootstrap\LOG\Files\SQLSetup0001_w4102762_SQLXML4_1.log
> > > > ----
> > > >
> > > >
> > > > SQL Server Setup failed. For more information, review the Setup log
> > > > file in %ProgramFiles%\Microsoft SQL Server\90\Setup
> > > > Bootstrap\LOG\Summary.txt.
> > > >
> > > >
> >
> >|||Hi
It may be worth trying to install on another pc to see if the error occurs,
or possibly download the non-iso version.
John
"Padmanaban" wrote:
> Hi,
> No, i created CD from MSDN subcription and using
>
> Thanks
> Paddy
>
> John Bell wrote:
> > Hi
> >
> > SSL is not necessary, but as your error talks about certificates it is one
> > of the most likely uses for them.
> >
> > Has this media been used to install on any other machines?
> >
> > John
> >
> > "Padmanaban" wrote:
> >
> > > Thanks John Bell
> > >
> > > I dont have SSL in my Laptop, Do I have to enable SSL in my laptop?.
> > >
> > > Is it possible to install SQL Server 2005 Standard without SSL. I dont
> > > think our IT guys going to allow installing SSL in laptop (my work
> > > development system)
> > >
> > > Please help me
> > >
> > > Thanks
> > >
> > > Paddy
> > >
> > > John Bell wrote:
> > > > Hi
> > > >
> > > > Do you have SSL enabled and have you tried removing it before installing?
> > > >
> > > > John
> > > >
> > > > "Padmanaban" wrote:
> > > >
> > > > > Hi
> > > > >
> > > > > I am trying to install SQL Server 2005 Standard on my laptop, which has
> > > > > Windows XP Professional with Service Pack 2. I could not able to
> > > > > install properly and i am getting error always. i tried whatever the
> > > > > people mentioned in Google, but I could not able to fix the problem.
> > > > > please some one can help my problem.
> > > > >
> > > > > Here is the Error I am getting always "The certificate chain was issued
> > > > > by an authority that is not trusted" . I am trying for past few days i
> > > > > could not able to resolve.
> > > > >
> > > > > please help
> > > > >
> > > > > Note : I have SQL Server 2000 Client installed in my laptop. this is my
> > > > > development machine
> > > > >
> > > > > Thanks
> > > > >
> > > > > Paddy
> > > > >
> > > > >
> > > > > Here is the Error message from Summary.txt
> > > > >
> > > > >
> > > > >
> > > > > Product : SQL Server Database Services
> > > > > Error : SQL Server Setup could not connect to the database
> > > > > service for server configuration. The error was: [Microsoft][SQL Native
> > > > > Client]SSL Provider: The certificate chain was issued by an authority
> > > > > that is not trusted.
> > > > > Refer to server error logs and setup logs for more information. For
> > > > > details on how to view setup logs, see "How to View Setup Log Files" in
> > > > > SQL Server Books Online.
> > > > >
> > > > >
> > > > > ----
> > > > > Machine : W4102762
> > > > > Product : Microsoft SQL Server 2005
> > > > > Product Version : 9.00.1399.06
> > > > > Install : Failed
> > > > > Log File : C:\Program Files\Microsoft SQL Server\90\Setup
> > > > > Bootstrap\LOG\Files\SQLSetup0001_w4102762_SQL.log
> > > > > Last Action : InstallFinalize
> > > > > Error String : SQL Server Setup could not connect to the database
> > > > > service for server configuration. The error was: {Microsoft}{SQL Native
> > > > > Client}SSL Provider: The certificate chain was issued by an authority
> > > > > that is not trusted.
> > > > > Error Number : 29515
> > > > > ----
> > > > >
> > > > > Machine : W4102762
> > > > > Product : SQLXML4
> > > > > Product Version : 9.00.1399.06
> > > > > Install : Successful
> > > > > Log File : C:\Program Files\Microsoft SQL Server\90\Setup
> > > > > Bootstrap\LOG\Files\SQLSetup0001_w4102762_SQLXML4_1.log
> > > > > ----
> > > > >
> > > > >
> > > > > SQL Server Setup failed. For more information, review the Setup log
> > > > > file in %ProgramFiles%\Microsoft SQL Server\90\Setup
> > > > > Bootstrap\LOG\Summary.txt.
> > > > >
> > > > >
> > >
> > >
>
Friday, March 9, 2012
Installation of SQL server 2005 SP1
Hi,
We have the Windows server 2003 R2 Service PAck 2 , we got updated to this version after i installed automatic updates today,and i am having problems with setting up maintenance plan in SQL server 2005 (9.0.1399)
Hence i am trying to install Sql server 2005 SP1, but the read me file says that this installation is compatible only with Windows server 2003 SP1
Also, i received this error when i tried to install SQL server 2005 SP1 yesterday
"The image file hotfix.exe is valid, but is for a machine type other than the current machine"
I am confused, Can someone help me out in this regard?
Thanks in advance
The second part of the post (valid for another type of machine) typically refers to an error you see when you try to install an X64 (64-bit) service pack on an X86 machine (32-bit). For that one, I'd just suggest to double check that you have the corrent installation package for your machine.
Wednesday, March 7, 2012
Installation of Service Pack 4 for SQL 2000
All,
I have a problem with installing SQL 2000 Sevice Pack 4. Please see Part II.
Service Pack 4 comes in four parts and each one is to be used to apply to different SQL server components.
Part I - Analysis Service Pack - Complete.
Part II - MSDE component - Problems. The original problem was that it needed a strong password. I got around that by supplying the sa password. Now it says that the sql server instance name specified is invalid. I spent some time researching this and have tried to add parameters in an ini file to specify the instance to be updated. So far everything I tried has failed. Currently, I am not sure what to try next. Setup will not run from the dos prompt.
Here is what my setup.ini file looks like:
[Options]
SAPWD="nochange"
TARGETDIR="C:\Program Files\Microsoft SQL Server\Mssql$Mssqlserver$RPMS\Binn\"
DATADIR="D:\Mssql\Mssql$RPMS\Data\"
INSTANCENAME="FHDP1IRMPA01\RPMS"
Part III - SQL Server 2000 (64-bit) - No need to install since it does not apply to the machine.
Part IV - Database Components - Complete.
I would appreciate any help or suggestions anyone can provide. Thanks in advance.
PeterJR
there is a switch BLANKPASSWORD=1.
also - try just using "MSSQLServer" for your instance name.
|||You cannot have "\" in the instance name. I am guessing the first part in your instancename is the machine name, but that is not necessary, nor correct.Installation of hotfix package (build 2153) fails
Hello.
I am attempting to install the first of the cumulative hotfix packages ( SQL2005-KB918222-x64-ENU.exe) after applying Service Pack 1 to a SQL Server 2005 std edn 64-bit installation. The service pack installed no problem but the hot fix fails with the following errors in the log file below.
I have installed the 32-bit versions of the hotfix packages onto a different server and I did not get these errors.
Any help on how to sort this out would be much appreciated!
08/23/2006 15:03:44.592 ================================================================================
08/23/2006 15:03:44.608 Hotfix package launched
08/23/2006 15:03:45.842 Product discovery successfully completed during the install process for MSSQLSERVER
08/23/2006 15:03:45.858 SP Level check successfully completed during the install process for MSSQLSERVER
08/23/2006 15:03:45.889 Product language check successfully completed during the install process for MSSQLSERVER
08/23/2006 15:03:45.905 Product version check successfully completed during the install process for MSSQLSERVER
08/23/2006 15:03:45.920 Command-line instance name check completed during the install process
08/23/2006 15:03:45.936 Baseline build check completed during the install process
08/23/2006 15:03:52.107 Attempting to install instance: MSSQLSERVER
08/23/2006 15:03:52.154 Attempting to install target: SRVLEBIZTALK
08/23/2006 15:03:52.170 Attempting to check for locked files: sqlrun_sql.msp
08/23/2006 15:03:52.232 Attempting to check for locked files: \\SRVLEBIZTALK\d$\dd32a156dacc8dbe70a862647d70\hotfixsql\Files\sqlrun_sql.msp
08/23/2006 15:03:52.248 Creating MSP locked file check log at: C:\WINDOWS\Hotfix\SQL9\Logs\SQL9_Hotfix_KB918222_sqlrun_sql.msp.out
08/23/2006 15:04:02.107 MSP returned 1602: The user cancels installation.
08/23/2006 15:04:02.310 Successfully checked file: \\SRVLEBIZTALK\d$\dd32a156dacc8dbe70a862647d70\hotfixsql\Files\sqlrun_sql.msp
08/23/2006 15:04:02.326 Successfully opened registry key: System\CurrentControlSet\Control\Session Manager
08/23/2006 15:04:02.357 Failed to read registry key: PendingFileRenameOperations
08/23/2006 15:04:02.373 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\xmlfilt.dll
08/23/2006 15:04:02.388 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\ThaWBrkr.dll
08/23/2006 15:04:02.435 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\query.dll
08/23/2006 15:04:02.451 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\nls400.dll.
--
It carries on with errors like the above but my post will be massive if I include it all, so below is the last few lines of the log file.
--
08/23/2006 15:04:07.591 Failed to read associated hotfix build information for the following file: C:\Program Files (x86)\Microsoft SQL Server\90\Shared\Microsoft.SqlSac.Public.dll
08/23/2006 15:04:07.653 Attempting to install file: sqlrun_sql.msp
08/23/2006 15:04:07.700 Attempting to install file: \\SRVLEBIZTALK\d$\dd32a156dacc8dbe70a862647d70\hotfixsql\Files\sqlrun_sql.msp
08/23/2006 15:04:07.716 Creating MSP install log file at: C:\WINDOWS\Hotfix\SQL9\Logs\SQL9_Hotfix_KB918222_sqlrun_sql.msp.log
08/23/2006 15:04:07.732 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
08/23/2006 15:04:07.747 Failed to read registry key: Debug
08/23/2006 15:05:11.197 MSP returned 1603: A fatal error occurred during installation.
08/23/2006 15:05:11.212 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
08/23/2006 15:05:11.244 Failed to read registry key: Debug
08/23/2006 15:05:11.259 Unable to install MSP file: \\SRVLEBIZTALK\d$\dd32a156dacc8dbe70a862647d70\hotfixsql\Files\sqlrun_sql.msp
08/23/2006 15:05:11.275 The following exception occurred: Unable to install Windows Installer MSP file Date: 08/23/2006 15:05:11.275 File: \depot\sqlvault\stable\setupmainl1\setup\sqlse\sqlsedll\copyengine.cpp Line: 856
08/23/2006 15:05:11.322
08/23/2006 15:05:11.353 Product Status Summary:
08/23/2006 15:05:11.369 Product: SQL Server Database Services 2005 (64-bit)
08/23/2006 15:05:11.384 MSSQLSERVER - Failure
08/23/2006 15:05:11.415 Details: Unable to install Windows Installer MSP file
These "failed to read associated hotfix version" error messages are misleading and do not necessary denote a failed install. I've had lots of successful installs that also contained these messages. Can you search you %WINDIR%\hotfix\hotfixsql\Files\sqlrun_sql.msp log for the text string "value 3" and see if there is a more descriptive message?
Thanks,
Sam Lester (MSFT)
Are you installing the hotfixes in the correct order?
SQL Server 2005
SQL Server 2005 Analysis Services
SQL Server 2005 Integration Services
SQL Server 2005 Notification Services
SQL Server 2005 Reporting Services
SQL Server 2005 Tools
http://support.microsoft.com/kb/919224/
|||I am also getting the same error with Enterprise Edition on a cluster while installing build 2153.
The first remote node is successful and then the local node fails
11/02/2006 16:26:51.032 ================================================================================
11/02/2006 16:26:51.042 Hotfix package launched
11/02/2006 16:26:53.009 Product discovery successfully completed during the install process for MSSQLSERVER
11/02/2006 16:26:53.020 SP Level check successfully completed during the install process for MSSQLSERVER
11/02/2006 16:26:53.030 Product language check successfully completed during the install process for MSSQLSERVER
11/02/2006 16:26:53.040 Product version check successfully completed during the install process for MSSQLSERVER
11/02/2006 16:26:53.227 Product discovery successfully completed during the install process for VSQL06
11/02/2006 16:26:53.237 SP Level check successfully completed during the install process for VSQL06
11/02/2006 16:26:53.258 Product language check successfully completed during the install process for VSQL06
11/02/2006 16:26:53.268 Product version check successfully completed during the install process for VSQL06
11/02/2006 16:26:53.278 Command-line instance name check completed during the install process
11/02/2006 16:26:53.320 Baseline build check completed during the install process
11/02/2006 16:27:49.750 Attempting to install instance: MSSQLSERVER
11/02/2006 16:27:49.781 Enumerating passive cluster nodes
11/02/2006 16:27:49.812 Patching available passive node: FMEZ1TMP201
11/02/2006 16:27:49.823 Attempting to patch running passive node: FMEZ1TMP201
11/02/2006 16:27:49.833 Waiting for first successfully completed passive node
11/02/2006 16:27:49.916 Successfully created remote folder for product instance target \\FMEZ1TMP201
11/02/2006 16:27:51.666 Successfully transferred payload to remote product instance target \\FMEZ1TMP201
11/02/2006 16:27:51.676 Successfully transferred payload to remote product instance target \\FMEZ1TMP201
11/02/2006 16:27:51.718 Successfully created new scheduled task for product instance target \\FMEZ1TMP201
11/02/2006 16:27:52.453 Successfully saved new scheduled task for product instance target \\FMEZ1TMP201
11/02/2006 16:27:52.484 Successfully created scheduled task for product instance target \\FMEZ1TMP201
11/02/2006 16:27:52.505 Successfully started scheduled task for product instance target \\FMEZ1TMP201
11/02/2006 16:27:52.515 Successfully started scheduled task for product instance target \\FMEZ1TMP201
11/02/2006 16:30:23.543 Scheduled task for product instance target has completed
11/02/2006 16:30:23.563 Waiting for exit code from scheduled task for product instance target \\FMEZ1TMP201
11/02/2006 16:30:28.581 Received exit code 0 from scheduled task for product instance target \\FMEZ1TMP201
11/02/2006 16:30:28.591 Result code for scheduled task for product instance target has been received
11/02/2006 16:30:28.611 Removed scheduled task for product instance target \\FMEZ1TMP201
11/02/2006 16:30:28.911 Successfully removed remote folder for product instance target \\FMEZ1TMP201
11/02/2006 16:30:28.931 Remote process completed for product instance target
11/02/2006 16:30:28.941 Exit code for passive node: FMEZ1TMP201 = 0
11/02/2006 16:30:30.941 First successful passive node has been completed
11/02/2006 16:30:30.961 Attempting to install target: FMEZ1TMP200
11/02/2006 16:30:35.190 Attempting to check for locked files: sqlrun_sql.msp
11/02/2006 16:30:35.240 Attempting to check for locked files: \\FMEZ1TMP200\c$\4abf7684d30ce4aeb614ce\hotfixsql\Files\sqlrun_sql.msp
11/02/2006 16:30:35.260 Creating MSP locked file check log at: C:\WINDOWS\Hotfix\SQL9\Logs\SQL9_Hotfix_KB918222_sqlrun_sql.msp.out
11/02/2006 16:31:03.862 MSP returned 1602: The user cancels installation.
11/02/2006 16:31:04.101 Successfully checked file: \\FMEZ1TMP200\c$\4abf7684d30ce4aeb614ce\hotfixsql\Files\sqlrun_sql.msp
11/02/2006 16:31:04.121 Successfully opened registry key: System\CurrentControlSet\Control\Session Manager
11/02/2006 16:31:04.141 Failed to read registry key: PendingFileRenameOperations
11/02/2006 16:31:04.151 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\xmlfilt.dll
~~~~~~~~
~~~~~~~~
11/02/2006 16:31:08.180 Failed to read associated hotfix build information for the following file: C:\Program Files (x86)\Microsoft SQL Server\90\Shared\Microsoft.SqlSac.Public.dll
11/02/2006 16:31:08.300 Attempting to install file: sqlrun_sql.msp
11/02/2006 16:31:08.360 Attempting to install file: \\FMEZ1TMP200\c$\4abf7684d30ce4aeb614ce\hotfixsql\Files\sqlrun_sql.msp
11/02/2006 16:31:08.370 Creating MSP install log file at: C:\WINDOWS\Hotfix\SQL9\Logs\SQL9_Hotfix_KB918222_sqlrun_sql.msp.log
11/02/2006 16:31:08.380 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
11/02/2006 16:31:08.400 Failed to read registry key: Debug
11/02/2006 16:33:02.798 MSP returned 1603: A fatal error occurred during installation.
11/02/2006 16:33:03.098 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
11/02/2006 16:33:03.108 Failed to read registry key: Debug
11/02/2006 16:33:03.128 Unable to install MSP file: \\FMEZ1TMP200\c$\4abf7684d30ce4aeb614ce\hotfixsql\Files\sqlrun_sql.msp
11/02/2006 16:33:03.138 The following exception occurred: Unable to install Windows Installer MSP file Date: 11/02/2006 16:33:03.138 File: \depot\sqlvault\stable\setupmainl1\setup\sqlse\sqlsedll\copyengine.cpp Line: 856
11/02/2006 16:33:03.218
11/02/2006 16:33:03.228 Product Status Summary:
11/02/2006 16:33:03.248 Product: SQL Server Database Services 2005 (64-bit)
11/02/2006 16:33:03.258 MSSQLSERVER - Failure
11/02/2006 16:33:03.278 Details: Unable to install Windows Installer MSP file
11/02/2006 16:33:03.288 VSQL06 - Not Selected
11/02/2006 16:33:03.308
11/02/2006 16:37:36.262 Hotfix package closed
Any ideas?
|||From the hotfix log it may appear that these two issues are the same, however, 1603 is a generic error code for MSP installation which basically just means the install failed. You have to look specifically in the log generated for the MSP to determine the actual cause of failure.
It turns out though that the log with the error for both reports will be located here:
C:\WINDOWS\Hotfix\SQL9\Logs\SQL9_Hotfix_KB918222_sqlrun_sql.msp.log
You can determine this from these lines in the hotfix log:
11/02/2006 16:31:08.300 Attempting to install file: sqlrun_sql.msp
11/02/2006 16:31:08.360 Attempting to install file: \\FMEZ1TMP200\c$\4abf7684d30ce4aeb614ce\hotfixsql\Files\sqlrun_sql.msp
11/02/2006 16:31:08.370 Creating MSP install log file at: C:\WINDOWS\Hotfix\SQL9\Logs\SQL9_Hotfix_KB918222_sqlrun_sql.msp.log
As Sam suggests, search for "value 3" to try and locate the specific issue causing the failure in both cases. Once you have located it, please post the details so we can troubleshoot this further. Thanks!!
|||bobbins wrote:
Hello.
I am attempting to install the first of the cumulative hotfix packages ( SQL2005-KB918222-x64-ENU.exe) after applying Service Pack 1 to a SQL Server 2005 std edn 64-bit installation. The service pack installed no problem but the hot fix fails with the following errors in the log file below.
I have installed the 32-bit versions of the hotfix packages onto a different server and I did not get these errors.
Any help on how to sort this out would be much appreciated!
08/23/2006 15:03:44.592 ================================================================================
08/23/2006 15:03:44.608 Hotfix package launched
08/23/2006 15:03:45.842 Product discovery successfully completed during the install process for MSSQLSERVER
08/23/2006 15:03:45.858 SP Level check successfully completed during the install process for MSSQLSERVER
08/23/2006 15:03:45.889 Product language check successfully completed during the install process for MSSQLSERVER
08/23/2006 15:03:45.905 Product version check successfully completed during the install process for MSSQLSERVER
08/23/2006 15:03:45.920 Command-line instance name check completed during the install process
08/23/2006 15:03:45.936 Baseline build check completed during the install process
08/23/2006 15:03:52.107 Attempting to install instance: MSSQLSERVER
08/23/2006 15:03:52.154 Attempting to install target: SRVLEBIZTALK
08/23/2006 15:03:52.170 Attempting to check for locked files: sqlrun_sql.msp
08/23/2006 15:03:52.232 Attempting to check for locked files: \\SRVLEBIZTALK\d$\dd32a156dacc8dbe70a862647d70\hotfixsql\Files\sqlrun_sql.msp
08/23/2006 15:03:52.248 Creating MSP locked file check log at: C:\WINDOWS\Hotfix\SQL9\Logs\SQL9_Hotfix_KB918222_sqlrun_sql.msp.out
08/23/2006 15:04:02.107 MSP returned 1602: The user cancels installation.
08/23/2006 15:04:02.310 Successfully checked file: \\SRVLEBIZTALK\d$\dd32a156dacc8dbe70a862647d70\hotfixsql\Files\sqlrun_sql.msp
08/23/2006 15:04:02.326 Successfully opened registry key: System\CurrentControlSet\Control\Session Manager
08/23/2006 15:04:02.357 Failed to read registry key: PendingFileRenameOperations
08/23/2006 15:04:02.373 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\xmlfilt.dll
08/23/2006 15:04:02.388 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\ThaWBrkr.dll
08/23/2006 15:04:02.435 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\query.dll
08/23/2006 15:04:02.451 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\nls400.dll.--
It carries on with errors like the above but my post will be massive if I include it all, so below is the last few lines of the log file.
--
08/23/2006 15:04:07.591 Failed to read associated hotfix build information for the following file: C:\Program Files (x86)\Microsoft SQL Server\90\Shared\Microsoft.SqlSac.Public.dll
08/23/2006 15:04:07.653 Attempting to install file: sqlrun_sql.msp
08/23/2006 15:04:07.700 Attempting to install file: \\SRVLEBIZTALK\d$\dd32a156dacc8dbe70a862647d70\hotfixsql\Files\sqlrun_sql.msp
08/23/2006 15:04:07.716 Creating MSP install log file at: C:\WINDOWS\Hotfix\SQL9\Logs\SQL9_Hotfix_KB918222_sqlrun_sql.msp.log
08/23/2006 15:04:07.732 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
08/23/2006 15:04:07.747 Failed to read registry key: Debug
08/23/2006 15:05:11.197 MSP returned 1603: A fatal error occurred during installation.
08/23/2006 15:05:11.212 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
08/23/2006 15:05:11.244 Failed to read registry key: Debug
08/23/2006 15:05:11.259 Unable to install MSP file: \\SRVLEBIZTALK\d$\dd32a156dacc8dbe70a862647d70\hotfixsql\Files\sqlrun_sql.msp
08/23/2006 15:05:11.275 The following exception occurred: Unable to install Windows Installer MSP file Date: 08/23/2006 15:05:11.275 File: \depot\sqlvault\stable\setupmainl1\setup\sqlse\sqlsedll\copyengine.cpp Line: 856
08/23/2006 15:05:11.322
08/23/2006 15:05:11.353 Product Status Summary:
08/23/2006 15:05:11.369 Product: SQL Server Database Services 2005 (64-bit)
08/23/2006 15:05:11.384 MSSQLSERVER - Failure
08/23/2006 15:05:11.415 Details: Unable to install Windows Installer MSP file
Installation of hotfix package (build 2153) fails
Hello.
I am attempting to install the first of the cumulative hotfix packages ( SQL2005-KB918222-x64-ENU.exe) after applying Service Pack 1 to a SQL Server 2005 std edn 64-bit installation. The service pack installed no problem but the hot fix fails with the following errors in the log file below.
I have installed the 32-bit versions of the hotfix packages onto a different server and I did not get these errors.
Any help on how to sort this out would be much appreciated!
08/23/2006 15:03:44.592 ================================================================================
08/23/2006 15:03:44.608 Hotfix package launched
08/23/2006 15:03:45.842 Product discovery successfully completed during the install process for MSSQLSERVER
08/23/2006 15:03:45.858 SP Level check successfully completed during the install process for MSSQLSERVER
08/23/2006 15:03:45.889 Product language check successfully completed during the install process for MSSQLSERVER
08/23/2006 15:03:45.905 Product version check successfully completed during the install process for MSSQLSERVER
08/23/2006 15:03:45.920 Command-line instance name check completed during the install process
08/23/2006 15:03:45.936 Baseline build check completed during the install process
08/23/2006 15:03:52.107 Attempting to install instance: MSSQLSERVER
08/23/2006 15:03:52.154 Attempting to install target: SRVLEBIZTALK
08/23/2006 15:03:52.170 Attempting to check for locked files: sqlrun_sql.msp
08/23/2006 15:03:52.232 Attempting to check for locked files: \\SRVLEBIZTALK\d$\dd32a156dacc8dbe70a862647d70\hotfixsql\Files\sqlrun_sql.msp
08/23/2006 15:03:52.248 Creating MSP locked file check log at: C:\WINDOWS\Hotfix\SQL9\Logs\SQL9_Hotfix_KB918222_sqlrun_sql.msp.out
08/23/2006 15:04:02.107 MSP returned 1602: The user cancels installation.
08/23/2006 15:04:02.310 Successfully checked file: \\SRVLEBIZTALK\d$\dd32a156dacc8dbe70a862647d70\hotfixsql\Files\sqlrun_sql.msp
08/23/2006 15:04:02.326 Successfully opened registry key: System\CurrentControlSet\Control\Session Manager
08/23/2006 15:04:02.357 Failed to read registry key: PendingFileRenameOperations
08/23/2006 15:04:02.373 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\xmlfilt.dll
08/23/2006 15:04:02.388 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\ThaWBrkr.dll
08/23/2006 15:04:02.435 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\query.dll
08/23/2006 15:04:02.451 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\nls400.dll.
--
It carries on with errors like the above but my post will be massive if I include it all, so below is the last few lines of the log file.
--
08/23/2006 15:04:07.591 Failed to read associated hotfix build information for the following file: C:\Program Files (x86)\Microsoft SQL Server\90\Shared\Microsoft.SqlSac.Public.dll
08/23/2006 15:04:07.653 Attempting to install file: sqlrun_sql.msp
08/23/2006 15:04:07.700 Attempting to install file: \\SRVLEBIZTALK\d$\dd32a156dacc8dbe70a862647d70\hotfixsql\Files\sqlrun_sql.msp
08/23/2006 15:04:07.716 Creating MSP install log file at: C:\WINDOWS\Hotfix\SQL9\Logs\SQL9_Hotfix_KB918222_sqlrun_sql.msp.log
08/23/2006 15:04:07.732 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
08/23/2006 15:04:07.747 Failed to read registry key: Debug
08/23/2006 15:05:11.197 MSP returned 1603: A fatal error occurred during installation.
08/23/2006 15:05:11.212 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
08/23/2006 15:05:11.244 Failed to read registry key: Debug
08/23/2006 15:05:11.259 Unable to install MSP file: \\SRVLEBIZTALK\d$\dd32a156dacc8dbe70a862647d70\hotfixsql\Files\sqlrun_sql.msp
08/23/2006 15:05:11.275 The following exception occurred: Unable to install Windows Installer MSP file Date: 08/23/2006 15:05:11.275 File: \depot\sqlvault\stable\setupmainl1\setup\sqlse\sqlsedll\copyengine.cpp Line: 856
08/23/2006 15:05:11.322
08/23/2006 15:05:11.353 Product Status Summary:
08/23/2006 15:05:11.369 Product: SQL Server Database Services 2005 (64-bit)
08/23/2006 15:05:11.384 MSSQLSERVER - Failure
08/23/2006 15:05:11.415 Details: Unable to install Windows Installer MSP file
These "failed to read associated hotfix version" error messages are misleading and do not necessary denote a failed install. I've had lots of successful installs that also contained these messages. Can you search you %WINDIR%\hotfix\hotfixsql\Files\sqlrun_sql.msp log for the text string "value 3" and see if there is a more descriptive message?
Thanks,
Sam Lester (MSFT)
Are you installing the hotfixes in the correct order?
SQL Server 2005
SQL Server 2005 Analysis Services
SQL Server 2005 Integration Services
SQL Server 2005 Notification Services
SQL Server 2005 Reporting Services
SQL Server 2005 Tools
http://support.microsoft.com/kb/919224/
|||I am also getting the same error with Enterprise Edition on a cluster while installing build 2153.
The first remote node is successful and then the local node fails
11/02/2006 16:26:51.032 ================================================================================
11/02/2006 16:26:51.042 Hotfix package launched
11/02/2006 16:26:53.009 Product discovery successfully completed during the install process for MSSQLSERVER
11/02/2006 16:26:53.020 SP Level check successfully completed during the install process for MSSQLSERVER
11/02/2006 16:26:53.030 Product language check successfully completed during the install process for MSSQLSERVER
11/02/2006 16:26:53.040 Product version check successfully completed during the install process for MSSQLSERVER
11/02/2006 16:26:53.227 Product discovery successfully completed during the install process for VSQL06
11/02/2006 16:26:53.237 SP Level check successfully completed during the install process for VSQL06
11/02/2006 16:26:53.258 Product language check successfully completed during the install process for VSQL06
11/02/2006 16:26:53.268 Product version check successfully completed during the install process for VSQL06
11/02/2006 16:26:53.278 Command-line instance name check completed during the install process
11/02/2006 16:26:53.320 Baseline build check completed during the install process
11/02/2006 16:27:49.750 Attempting to install instance: MSSQLSERVER
11/02/2006 16:27:49.781 Enumerating passive cluster nodes
11/02/2006 16:27:49.812 Patching available passive node: FMEZ1TMP201
11/02/2006 16:27:49.823 Attempting to patch running passive node: FMEZ1TMP201
11/02/2006 16:27:49.833 Waiting for first successfully completed passive node
11/02/2006 16:27:49.916 Successfully created remote folder for product instance target \\FMEZ1TMP201
11/02/2006 16:27:51.666 Successfully transferred payload to remote product instance target \\FMEZ1TMP201
11/02/2006 16:27:51.676 Successfully transferred payload to remote product instance target \\FMEZ1TMP201
11/02/2006 16:27:51.718 Successfully created new scheduled task for product instance target \\FMEZ1TMP201
11/02/2006 16:27:52.453 Successfully saved new scheduled task for product instance target \\FMEZ1TMP201
11/02/2006 16:27:52.484 Successfully created scheduled task for product instance target \\FMEZ1TMP201
11/02/2006 16:27:52.505 Successfully started scheduled task for product instance target \\FMEZ1TMP201
11/02/2006 16:27:52.515 Successfully started scheduled task for product instance target \\FMEZ1TMP201
11/02/2006 16:30:23.543 Scheduled task for product instance target has completed
11/02/2006 16:30:23.563 Waiting for exit code from scheduled task for product instance target \\FMEZ1TMP201
11/02/2006 16:30:28.581 Received exit code 0 from scheduled task for product instance target \\FMEZ1TMP201
11/02/2006 16:30:28.591 Result code for scheduled task for product instance target has been received
11/02/2006 16:30:28.611 Removed scheduled task for product instance target \\FMEZ1TMP201
11/02/2006 16:30:28.911 Successfully removed remote folder for product instance target \\FMEZ1TMP201
11/02/2006 16:30:28.931 Remote process completed for product instance target
11/02/2006 16:30:28.941 Exit code for passive node: FMEZ1TMP201 = 0
11/02/2006 16:30:30.941 First successful passive node has been completed
11/02/2006 16:30:30.961 Attempting to install target: FMEZ1TMP200
11/02/2006 16:30:35.190 Attempting to check for locked files: sqlrun_sql.msp
11/02/2006 16:30:35.240 Attempting to check for locked files: \\FMEZ1TMP200\c$\4abf7684d30ce4aeb614ce\hotfixsql\Files\sqlrun_sql.msp
11/02/2006 16:30:35.260 Creating MSP locked file check log at: C:\WINDOWS\Hotfix\SQL9\Logs\SQL9_Hotfix_KB918222_sqlrun_sql.msp.out
11/02/2006 16:31:03.862 MSP returned 1602: The user cancels installation.
11/02/2006 16:31:04.101 Successfully checked file: \\FMEZ1TMP200\c$\4abf7684d30ce4aeb614ce\hotfixsql\Files\sqlrun_sql.msp
11/02/2006 16:31:04.121 Successfully opened registry key: System\CurrentControlSet\Control\Session Manager
11/02/2006 16:31:04.141 Failed to read registry key: PendingFileRenameOperations
11/02/2006 16:31:04.151 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\xmlfilt.dll
~~~~~~~~
~~~~~~~~
11/02/2006 16:31:08.180 Failed to read associated hotfix build information for the following file: C:\Program Files (x86)\Microsoft SQL Server\90\Shared\Microsoft.SqlSac.Public.dll
11/02/2006 16:31:08.300 Attempting to install file: sqlrun_sql.msp
11/02/2006 16:31:08.360 Attempting to install file: \\FMEZ1TMP200\c$\4abf7684d30ce4aeb614ce\hotfixsql\Files\sqlrun_sql.msp
11/02/2006 16:31:08.370 Creating MSP install log file at: C:\WINDOWS\Hotfix\SQL9\Logs\SQL9_Hotfix_KB918222_sqlrun_sql.msp.log
11/02/2006 16:31:08.380 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
11/02/2006 16:31:08.400 Failed to read registry key: Debug
11/02/2006 16:33:02.798 MSP returned 1603: A fatal error occurred during installation.
11/02/2006 16:33:03.098 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
11/02/2006 16:33:03.108 Failed to read registry key: Debug
11/02/2006 16:33:03.128 Unable to install MSP file: \\FMEZ1TMP200\c$\4abf7684d30ce4aeb614ce\hotfixsql\Files\sqlrun_sql.msp
11/02/2006 16:33:03.138 The following exception occurred: Unable to install Windows Installer MSP file Date: 11/02/2006 16:33:03.138 File: \depot\sqlvault\stable\setupmainl1\setup\sqlse\sqlsedll\copyengine.cpp Line: 856
11/02/2006 16:33:03.218
11/02/2006 16:33:03.228 Product Status Summary:
11/02/2006 16:33:03.248 Product: SQL Server Database Services 2005 (64-bit)
11/02/2006 16:33:03.258 MSSQLSERVER - Failure
11/02/2006 16:33:03.278 Details: Unable to install Windows Installer MSP file
11/02/2006 16:33:03.288 VSQL06 - Not Selected
11/02/2006 16:33:03.308
11/02/2006 16:37:36.262 Hotfix package closed
Any ideas?
|||From the hotfix log it may appear that these two issues are the same, however, 1603 is a generic error code for MSP installation which basically just means the install failed. You have to look specifically in the log generated for the MSP to determine the actual cause of failure.
It turns out though that the log with the error for both reports will be located here:
C:\WINDOWS\Hotfix\SQL9\Logs\SQL9_Hotfix_KB918222_sqlrun_sql.msp.log
You can determine this from these lines in the hotfix log:
11/02/2006 16:31:08.300 Attempting to install file: sqlrun_sql.msp
11/02/2006 16:31:08.360 Attempting to install file: \\FMEZ1TMP200\c$\4abf7684d30ce4aeb614ce\hotfixsql\Files\sqlrun_sql.msp
11/02/2006 16:31:08.370 Creating MSP install log file at: C:\WINDOWS\Hotfix\SQL9\Logs\SQL9_Hotfix_KB918222_sqlrun_sql.msp.log
As Sam suggests, search for "value 3" to try and locate the specific issue causing the failure in both cases. Once you have located it, please post the details so we can troubleshoot this further. Thanks!!
|||Hello.
I am attempting to install the first of the cumulative hotfix packages ( SQL2005-KB918222-x64-ENU.exe) after applying Service Pack 1 to a SQL Server 2005 std edn 64-bit installation. The service pack installed no problem but the hot fix fails with the following errors in the log file below.
I have installed the 32-bit versions of the hotfix packages onto a different server and I did not get these errors.
Any help on how to sort this out would be much appreciated!
08/23/2006 15:03:44.592 ================================================================================
08/23/2006 15:03:44.608 Hotfix package launched
08/23/2006 15:03:45.842 Product discovery successfully completed during the install process for MSSQLSERVER
08/23/2006 15:03:45.858 SP Level check successfully completed during the install process for MSSQLSERVER
08/23/2006 15:03:45.889 Product language check successfully completed during the install process for MSSQLSERVER
08/23/2006 15:03:45.905 Product version check successfully completed during the install process for MSSQLSERVER
08/23/2006 15:03:45.920 Command-line instance name check completed during the install process
08/23/2006 15:03:45.936 Baseline build check completed during the install process
08/23/2006 15:03:52.107 Attempting to install instance: MSSQLSERVER
08/23/2006 15:03:52.154 Attempting to install target: SRVLEBIZTALK
08/23/2006 15:03:52.170 Attempting to check for locked files: sqlrun_sql.msp
08/23/2006 15:03:52.232 Attempting to check for locked files: \\SRVLEBIZTALK\d$\dd32a156dacc8dbe70a862647d70\hotfixsql\Files\sqlrun_sql.msp
08/23/2006 15:03:52.248 Creating MSP locked file check log at: C:\WINDOWS\Hotfix\SQL9\Logs\SQL9_Hotfix_KB918222_sqlrun_sql.msp.out
08/23/2006 15:04:02.107 MSP returned 1602: The user cancels installation.
08/23/2006 15:04:02.310 Successfully checked file: \\SRVLEBIZTALK\d$\dd32a156dacc8dbe70a862647d70\hotfixsql\Files\sqlrun_sql.msp
08/23/2006 15:04:02.326 Successfully opened registry key: System\CurrentControlSet\Control\Session Manager
08/23/2006 15:04:02.357 Failed to read registry key: PendingFileRenameOperations
08/23/2006 15:04:02.373 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\xmlfilt.dll
08/23/2006 15:04:02.388 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\ThaWBrkr.dll
08/23/2006 15:04:02.435 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\query.dll
08/23/2006 15:04:02.451 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\nls400.dll.--
It carries on with errors like the above but my post will be massive if I include it all, so below is the last few lines of the log file.
--
08/23/2006 15:04:07.591 Failed to read associated hotfix build information for the following file: C:\Program Files (x86)\Microsoft SQL Server\90\Shared\Microsoft.SqlSac.Public.dll
08/23/2006 15:04:07.653 Attempting to install file: sqlrun_sql.msp
08/23/2006 15:04:07.700 Attempting to install file: \\SRVLEBIZTALK\d$\dd32a156dacc8dbe70a862647d70\hotfixsql\Files\sqlrun_sql.msp
08/23/2006 15:04:07.716 Creating MSP install log file at: C:\WINDOWS\Hotfix\SQL9\Logs\SQL9_Hotfix_KB918222_sqlrun_sql.msp.log
08/23/2006 15:04:07.732 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
08/23/2006 15:04:07.747 Failed to read registry key: Debug
08/23/2006 15:05:11.197 MSP returned 1603: A fatal error occurred during installation.
08/23/2006 15:05:11.212 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
08/23/2006 15:05:11.244 Failed to read registry key: Debug
08/23/2006 15:05:11.259 Unable to install MSP file: \\SRVLEBIZTALK\d$\dd32a156dacc8dbe70a862647d70\hotfixsql\Files\sqlrun_sql.msp
08/23/2006 15:05:11.275 The following exception occurred: Unable to install Windows Installer MSP file Date: 08/23/2006 15:05:11.275 File: \depot\sqlvault\stable\setupmainl1\setup\sqlse\sqlsedll\copyengine.cpp Line: 856
08/23/2006 15:05:11.322
08/23/2006 15:05:11.353 Product Status Summary:
08/23/2006 15:05:11.369 Product: SQL Server Database Services 2005 (64-bit)
08/23/2006 15:05:11.384 MSSQLSERVER - Failure
08/23/2006 15:05:11.415 Details: Unable to install Windows Installer MSP file
Installation of hotfix package (build 2153) fails
Hello.
I am attempting to install the first of the cumulative hotfix packages ( SQL2005-KB918222-x64-ENU.exe) after applying Service Pack 1 to a SQL Server 2005 std edn 64-bit installation. The service pack installed no problem but the hot fix fails with the following errors in the log file below.
I have installed the 32-bit versions of the hotfix packages onto a different server and I did not get these errors.
Any help on how to sort this out would be much appreciated!
08/23/2006 15:03:44.592 ================================================================================
08/23/2006 15:03:44.608 Hotfix package launched
08/23/2006 15:03:45.842 Product discovery successfully completed during the install process for MSSQLSERVER
08/23/2006 15:03:45.858 SP Level check successfully completed during the install process for MSSQLSERVER
08/23/2006 15:03:45.889 Product language check successfully completed during the install process for MSSQLSERVER
08/23/2006 15:03:45.905 Product version check successfully completed during the install process for MSSQLSERVER
08/23/2006 15:03:45.920 Command-line instance name check completed during the install process
08/23/2006 15:03:45.936 Baseline build check completed during the install process
08/23/2006 15:03:52.107 Attempting to install instance: MSSQLSERVER
08/23/2006 15:03:52.154 Attempting to install target: SRVLEBIZTALK
08/23/2006 15:03:52.170 Attempting to check for locked files: sqlrun_sql.msp
08/23/2006 15:03:52.232 Attempting to check for locked files: \\SRVLEBIZTALK\d$\dd32a156dacc8dbe70a862647d70\hotfixsql\Files\sqlrun_sql.msp
08/23/2006 15:03:52.248 Creating MSP locked file check log at: C:\WINDOWS\Hotfix\SQL9\Logs\SQL9_Hotfix_KB918222_sqlrun_sql.msp.out
08/23/2006 15:04:02.107 MSP returned 1602: The user cancels installation.
08/23/2006 15:04:02.310 Successfully checked file: \\SRVLEBIZTALK\d$\dd32a156dacc8dbe70a862647d70\hotfixsql\Files\sqlrun_sql.msp
08/23/2006 15:04:02.326 Successfully opened registry key: System\CurrentControlSet\Control\Session Manager
08/23/2006 15:04:02.357 Failed to read registry key: PendingFileRenameOperations
08/23/2006 15:04:02.373 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\xmlfilt.dll
08/23/2006 15:04:02.388 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\ThaWBrkr.dll
08/23/2006 15:04:02.435 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\query.dll
08/23/2006 15:04:02.451 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\nls400.dll.
--
It carries on with errors like the above but my post will be massive if I include it all, so below is the last few lines of the log file.
--
08/23/2006 15:04:07.591 Failed to read associated hotfix build information for the following file: C:\Program Files (x86)\Microsoft SQL Server\90\Shared\Microsoft.SqlSac.Public.dll
08/23/2006 15:04:07.653 Attempting to install file: sqlrun_sql.msp
08/23/2006 15:04:07.700 Attempting to install file: \\SRVLEBIZTALK\d$\dd32a156dacc8dbe70a862647d70\hotfixsql\Files\sqlrun_sql.msp
08/23/2006 15:04:07.716 Creating MSP install log file at: C:\WINDOWS\Hotfix\SQL9\Logs\SQL9_Hotfix_KB918222_sqlrun_sql.msp.log
08/23/2006 15:04:07.732 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
08/23/2006 15:04:07.747 Failed to read registry key: Debug
08/23/2006 15:05:11.197 MSP returned 1603: A fatal error occurred during installation.
08/23/2006 15:05:11.212 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
08/23/2006 15:05:11.244 Failed to read registry key: Debug
08/23/2006 15:05:11.259 Unable to install MSP file: \\SRVLEBIZTALK\d$\dd32a156dacc8dbe70a862647d70\hotfixsql\Files\sqlrun_sql.msp
08/23/2006 15:05:11.275 The following exception occurred: Unable to install Windows Installer MSP file Date: 08/23/2006 15:05:11.275 File: \depot\sqlvault\stable\setupmainl1\setup\sqlse\sqlsedll\copyengine.cpp Line: 856
08/23/2006 15:05:11.322
08/23/2006 15:05:11.353 Product Status Summary:
08/23/2006 15:05:11.369 Product: SQL Server Database Services 2005 (64-bit)
08/23/2006 15:05:11.384 MSSQLSERVER - Failure
08/23/2006 15:05:11.415 Details: Unable to install Windows Installer MSP file
These "failed to read associated hotfix version" error messages are misleading and do not necessary denote a failed install. I've had lots of successful installs that also contained these messages. Can you search you %WINDIR%\hotfix\hotfixsql\Files\sqlrun_sql.msp log for the text string "value 3" and see if there is a more descriptive message?
Thanks,
Sam Lester (MSFT)
Are you installing the hotfixes in the correct order?
SQL Server 2005
SQL Server 2005 Analysis Services
SQL Server 2005 Integration Services
SQL Server 2005 Notification Services
SQL Server 2005 Reporting Services
SQL Server 2005 Tools
http://support.microsoft.com/kb/919224/
|||I am also getting the same error with Enterprise Edition on a cluster while installing build 2153.
The first remote node is successful and then the local node fails
11/02/2006 16:26:51.032 ================================================================================
11/02/2006 16:26:51.042 Hotfix package launched
11/02/2006 16:26:53.009 Product discovery successfully completed during the install process for MSSQLSERVER
11/02/2006 16:26:53.020 SP Level check successfully completed during the install process for MSSQLSERVER
11/02/2006 16:26:53.030 Product language check successfully completed during the install process for MSSQLSERVER
11/02/2006 16:26:53.040 Product version check successfully completed during the install process for MSSQLSERVER
11/02/2006 16:26:53.227 Product discovery successfully completed during the install process for VSQL06
11/02/2006 16:26:53.237 SP Level check successfully completed during the install process for VSQL06
11/02/2006 16:26:53.258 Product language check successfully completed during the install process for VSQL06
11/02/2006 16:26:53.268 Product version check successfully completed during the install process for VSQL06
11/02/2006 16:26:53.278 Command-line instance name check completed during the install process
11/02/2006 16:26:53.320 Baseline build check completed during the install process
11/02/2006 16:27:49.750 Attempting to install instance: MSSQLSERVER
11/02/2006 16:27:49.781 Enumerating passive cluster nodes
11/02/2006 16:27:49.812 Patching available passive node: FMEZ1TMP201
11/02/2006 16:27:49.823 Attempting to patch running passive node: FMEZ1TMP201
11/02/2006 16:27:49.833 Waiting for first successfully completed passive node
11/02/2006 16:27:49.916 Successfully created remote folder for product instance target \\FMEZ1TMP201
11/02/2006 16:27:51.666 Successfully transferred payload to remote product instance target \\FMEZ1TMP201
11/02/2006 16:27:51.676 Successfully transferred payload to remote product instance target \\FMEZ1TMP201
11/02/2006 16:27:51.718 Successfully created new scheduled task for product instance target \\FMEZ1TMP201
11/02/2006 16:27:52.453 Successfully saved new scheduled task for product instance target \\FMEZ1TMP201
11/02/2006 16:27:52.484 Successfully created scheduled task for product instance target \\FMEZ1TMP201
11/02/2006 16:27:52.505 Successfully started scheduled task for product instance target \\FMEZ1TMP201
11/02/2006 16:27:52.515 Successfully started scheduled task for product instance target \\FMEZ1TMP201
11/02/2006 16:30:23.543 Scheduled task for product instance target has completed
11/02/2006 16:30:23.563 Waiting for exit code from scheduled task for product instance target \\FMEZ1TMP201
11/02/2006 16:30:28.581 Received exit code 0 from scheduled task for product instance target \\FMEZ1TMP201
11/02/2006 16:30:28.591 Result code for scheduled task for product instance target has been received
11/02/2006 16:30:28.611 Removed scheduled task for product instance target \\FMEZ1TMP201
11/02/2006 16:30:28.911 Successfully removed remote folder for product instance target \\FMEZ1TMP201
11/02/2006 16:30:28.931 Remote process completed for product instance target
11/02/2006 16:30:28.941 Exit code for passive node: FMEZ1TMP201 = 0
11/02/2006 16:30:30.941 First successful passive node has been completed
11/02/2006 16:30:30.961 Attempting to install target: FMEZ1TMP200
11/02/2006 16:30:35.190 Attempting to check for locked files: sqlrun_sql.msp
11/02/2006 16:30:35.240 Attempting to check for locked files: \\FMEZ1TMP200\c$\4abf7684d30ce4aeb614ce\hotfixsql\Files\sqlrun_sql.msp
11/02/2006 16:30:35.260 Creating MSP locked file check log at: C:\WINDOWS\Hotfix\SQL9\Logs\SQL9_Hotfix_KB918222_sqlrun_sql.msp.out
11/02/2006 16:31:03.862 MSP returned 1602: The user cancels installation.
11/02/2006 16:31:04.101 Successfully checked file: \\FMEZ1TMP200\c$\4abf7684d30ce4aeb614ce\hotfixsql\Files\sqlrun_sql.msp
11/02/2006 16:31:04.121 Successfully opened registry key: System\CurrentControlSet\Control\Session Manager
11/02/2006 16:31:04.141 Failed to read registry key: PendingFileRenameOperations
11/02/2006 16:31:04.151 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\xmlfilt.dll
~~~~~~~~
~~~~~~~~
11/02/2006 16:31:08.180 Failed to read associated hotfix build information for the following file: C:\Program Files (x86)\Microsoft SQL Server\90\Shared\Microsoft.SqlSac.Public.dll
11/02/2006 16:31:08.300 Attempting to install file: sqlrun_sql.msp
11/02/2006 16:31:08.360 Attempting to install file: \\FMEZ1TMP200\c$\4abf7684d30ce4aeb614ce\hotfixsql\Files\sqlrun_sql.msp
11/02/2006 16:31:08.370 Creating MSP install log file at: C:\WINDOWS\Hotfix\SQL9\Logs\SQL9_Hotfix_KB918222_sqlrun_sql.msp.log
11/02/2006 16:31:08.380 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
11/02/2006 16:31:08.400 Failed to read registry key: Debug
11/02/2006 16:33:02.798 MSP returned 1603: A fatal error occurred during installation.
11/02/2006 16:33:03.098 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
11/02/2006 16:33:03.108 Failed to read registry key: Debug
11/02/2006 16:33:03.128 Unable to install MSP file: \\FMEZ1TMP200\c$\4abf7684d30ce4aeb614ce\hotfixsql\Files\sqlrun_sql.msp
11/02/2006 16:33:03.138 The following exception occurred: Unable to install Windows Installer MSP file Date: 11/02/2006 16:33:03.138 File: \depot\sqlvault\stable\setupmainl1\setup\sqlse\sqlsedll\copyengine.cpp Line: 856
11/02/2006 16:33:03.218
11/02/2006 16:33:03.228 Product Status Summary:
11/02/2006 16:33:03.248 Product: SQL Server Database Services 2005 (64-bit)
11/02/2006 16:33:03.258 MSSQLSERVER - Failure
11/02/2006 16:33:03.278 Details: Unable to install Windows Installer MSP file
11/02/2006 16:33:03.288 VSQL06 - Not Selected
11/02/2006 16:33:03.308
11/02/2006 16:37:36.262 Hotfix package closed
Any ideas?
|||From the hotfix log it may appear that these two issues are the same, however, 1603 is a generic error code for MSP installation which basically just means the install failed. You have to look specifically in the log generated for the MSP to determine the actual cause of failure.
It turns out though that the log with the error for both reports will be located here:
C:\WINDOWS\Hotfix\SQL9\Logs\SQL9_Hotfix_KB918222_sqlrun_sql.msp.log
You can determine this from these lines in the hotfix log:
11/02/2006 16:31:08.300 Attempting to install file: sqlrun_sql.msp
11/02/2006 16:31:08.360 Attempting to install file: \\FMEZ1TMP200\c$\4abf7684d30ce4aeb614ce\hotfixsql\Files\sqlrun_sql.msp
11/02/2006 16:31:08.370 Creating MSP install log file at: C:\WINDOWS\Hotfix\SQL9\Logs\SQL9_Hotfix_KB918222_sqlrun_sql.msp.log
As Sam suggests, search for "value 3" to try and locate the specific issue causing the failure in both cases. Once you have located it, please post the details so we can troubleshoot this further. Thanks!!
|||
bobbins wrote:
Hello.
I am attempting to install the first of the cumulative hotfix packages ( SQL2005-KB918222-x64-ENU.exe) after applying Service Pack 1 to a SQL Server 2005 std edn 64-bit installation. The service pack installed no problem but the hot fix fails with the following errors in the log file below.
I have installed the 32-bit versions of the hotfix packages onto a different server and I did not get these errors.
Any help on how to sort this out would be much appreciated!
08/23/2006 15:03:44.592 ================================================================================
08/23/2006 15:03:44.608 Hotfix package launched
08/23/2006 15:03:45.842 Product discovery successfully completed during the install process for MSSQLSERVER
08/23/2006 15:03:45.858 SP Level check successfully completed during the install process for MSSQLSERVER
08/23/2006 15:03:45.889 Product language check successfully completed during the install process for MSSQLSERVER
08/23/2006 15:03:45.905 Product version check successfully completed during the install process for MSSQLSERVER
08/23/2006 15:03:45.920 Command-line instance name check completed during the install process
08/23/2006 15:03:45.936 Baseline build check completed during the install process
08/23/2006 15:03:52.107 Attempting to install instance: MSSQLSERVER
08/23/2006 15:03:52.154 Attempting to install target: SRVLEBIZTALK
08/23/2006 15:03:52.170 Attempting to check for locked files: sqlrun_sql.msp
08/23/2006 15:03:52.232 Attempting to check for locked files: \\SRVLEBIZTALK\d$\dd32a156dacc8dbe70a862647d70\hotfixsql\Files\sqlrun_sql.msp
08/23/2006 15:03:52.248 Creating MSP locked file check log at: C:\WINDOWS\Hotfix\SQL9\Logs\SQL9_Hotfix_KB918222_sqlrun_sql.msp.out
08/23/2006 15:04:02.107 MSP returned 1602: The user cancels installation.
08/23/2006 15:04:02.310 Successfully checked file: \\SRVLEBIZTALK\d$\dd32a156dacc8dbe70a862647d70\hotfixsql\Files\sqlrun_sql.msp
08/23/2006 15:04:02.326 Successfully opened registry key: System\CurrentControlSet\Control\Session Manager
08/23/2006 15:04:02.357 Failed to read registry key: PendingFileRenameOperations
08/23/2006 15:04:02.373 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\xmlfilt.dll
08/23/2006 15:04:02.388 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\ThaWBrkr.dll
08/23/2006 15:04:02.435 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\query.dll
08/23/2006 15:04:02.451 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\nls400.dll.--
It carries on with errors like the above but my post will be massive if I include it all, so below is the last few lines of the log file.
--
08/23/2006 15:04:07.591 Failed to read associated hotfix build information for the following file: C:\Program Files (x86)\Microsoft SQL Server\90\Shared\Microsoft.SqlSac.Public.dll
08/23/2006 15:04:07.653 Attempting to install file: sqlrun_sql.msp
08/23/2006 15:04:07.700 Attempting to install file: \\SRVLEBIZTALK\d$\dd32a156dacc8dbe70a862647d70\hotfixsql\Files\sqlrun_sql.msp
08/23/2006 15:04:07.716 Creating MSP install log file at: C:\WINDOWS\Hotfix\SQL9\Logs\SQL9_Hotfix_KB918222_sqlrun_sql.msp.log
08/23/2006 15:04:07.732 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
08/23/2006 15:04:07.747 Failed to read registry key: Debug
08/23/2006 15:05:11.197 MSP returned 1603: A fatal error occurred during installation.
08/23/2006 15:05:11.212 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
08/23/2006 15:05:11.244 Failed to read registry key: Debug
08/23/2006 15:05:11.259 Unable to install MSP file: \\SRVLEBIZTALK\d$\dd32a156dacc8dbe70a862647d70\hotfixsql\Files\sqlrun_sql.msp
08/23/2006 15:05:11.275 The following exception occurred: Unable to install Windows Installer MSP file Date: 08/23/2006 15:05:11.275 File: \depot\sqlvault\stable\setupmainl1\setup\sqlse\sqlsedll\copyengine.cpp Line: 856
08/23/2006 15:05:11.322
08/23/2006 15:05:11.353 Product Status Summary:
08/23/2006 15:05:11.369 Product: SQL Server Database Services 2005 (64-bit)
08/23/2006 15:05:11.384 MSSQLSERVER - Failure
08/23/2006 15:05:11.415 Details: Unable to install Windows Installer MSP file
Subscribe to:
Posts (Atom)