Installation Error: pack

Showing posts with label pack. Show all posts

Wednesday, March 28, 2012

Installing feature Pack components with an Application

Hi,

I have developed an application the uses SMO and RMO, now it is time to write the setup for it.

For the setup experience I want to be able to install my application on a clean copy of XP SP2 which has dotnet 2.0 already installed. As such I have downloaded the following from the Feature Pack for Sql 2005 (http://www.microsoft.com/downloads/details.aspx?familyid=d09c1d60-a13c-4479-9b91-9e8b9d835cdc&displaylang=en):

msxml6.msi

sqlncli.msi

sqlserver2005_xmo.msi

Now I'm thinking that I need to launch these msi's from within my own application msi, however, I don't want any UI displayed and I want my own msi to include these msi's when it's calculating the cost of the install.

Is this the correct way to go about getting these components on to a clients machine, i.e. nested msi install, or is there a better way?

Does anyone know what command line args (msiexec) or other options I need to provide for a UI less install of the above?

FYI I'm using VS 2005 to author the install.

Thanks for your help

Graham

Infact, why aren't msm (merge modules) given anymore?

Graham

|||

To get a silent install, use the "\qn" flag for MSIExec. In order to 'chain' MSI installations, you'll need to create a setup.exe wrapper that will launch the MSIs in series.

Here's an example from VS.Net: http://www.microsoft.com/downloads/details.aspx?FamilyId=BF253CFD-1EFC-4FC5-BA7E-6A6F21403495&displaylang=en that installs the .NET Framework (hardcoded) then installs your MSI using a settings.ini file. It'll need to be changed to remove the hardcoded installation and then to perhaps iterate through the .ini file to install multiple MSIs.

In response to why we don't ship MSMs any more, it is because we can't service them. If we discover a security (or other) problem with one of the files in the redist packages, we can't issue a QFE for MSMs, but we can issue a QFE for the MSIs that we send out. So it's a servicibility issue.

Monday, March 26, 2012

Installing Exchange Pack for Reporting Services

Has anyone successfully installed the Exchange Pack for Reporting Services?
I've attempted a couple of times and continue to get "Object Reference not
set to an instance of object", which causes the install to rollback.
Does anyone know how to correct this problem?
This question was originally posted in 10\04, but there was never an answer
posted.Do you have a default instance of SQL Server? What OS are you running? We
have never been able to repro this here.
--
Brian Welcker
Group Program Manager
SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"winkle60" <winkle60@.discussions.microsoft.com> wrote in message
news:22141FD2-86C1-4CBC-87F1-6E09FD77CC94@.microsoft.com...
> Has anyone successfully installed the Exchange Pack for Reporting
> Services?
> I've attempted a couple of times and continue to get "Object Reference not
> set to an instance of object", which causes the install to rollback.
> Does anyone know how to correct this problem?
> This question was originally posted in 10\04, but there was never an
> answer
> posted.
>|||Yes, I have the default instance running on SQL Server. The Reporting Service
installed fine. We are running Server 2003 STD (ver. 5.2.3790). .NET
Framework 1.1 (ver 1.1.4322.573). No Visual Studio installed.
"Brian Welcker [MSFT]" wrote:
> Do you have a default instance of SQL Server? What OS are you running? We
> have never been able to repro this here.
> --
> Brian Welcker
> Group Program Manager
> SQL Server Reporting Services
> This posting is provided "AS IS" with no warranties, and confers no rights.
> "winkle60" <winkle60@.discussions.microsoft.com> wrote in message
> news:22141FD2-86C1-4CBC-87F1-6E09FD77CC94@.microsoft.com...
> > Has anyone successfully installed the Exchange Pack for Reporting
> > Services?
> >
> > I've attempted a couple of times and continue to get "Object Reference not
> > set to an instance of object", which causes the install to rollback.
> >
> > Does anyone know how to correct this problem?
> >
> > This question was originally posted in 10\04, but there was never an
> > answer
> > posted.
> >
>
>|||I had this error, and it went away once I installed Visual Studio.NET Pro on
the PC, so there must be some object missing without it.
Michael
"winkle60" <winkle60@.discussions.microsoft.com> wrote in message
news:22141FD2-86C1-4CBC-87F1-6E09FD77CC94@.microsoft.com...
> Has anyone successfully installed the Exchange Pack for Reporting
Services?
> I've attempted a couple of times and continue to get "Object Reference not
> set to an instance of object", which causes the install to rollback.
> Does anyone know how to correct this problem?
> This question was originally posted in 10\04, but there was never an
answer
> posted.
>|||I have not tried installing Visual Studio, but I had a feeling that it might
be the issue even though it is supposed to be optional. I will try it when I
get the chance and see what happens.
"michael@.civis.com" wrote:
> I had this error, and it went away once I installed Visual Studio.NET Pro on
> the PC, so there must be some object missing without it.
> Michael
> "winkle60" <winkle60@.discussions.microsoft.com> wrote in message
> news:22141FD2-86C1-4CBC-87F1-6E09FD77CC94@.microsoft.com...
> > Has anyone successfully installed the Exchange Pack for Reporting
> Services?
> >
> > I've attempted a couple of times and continue to get "Object Reference not
> > set to an instance of object", which causes the install to rollback.
> >
> > Does anyone know how to correct this problem?
> >
> > This question was originally posted in 10\04, but there was never an
> answer
> > posted.
> >
>
>|||I installed Visual Studio .NET 2003 and was able to complete the install.
Another question, is there anyway to actually pull data from the Exchange
system without installing the SSW softeware extraction piece on the Exchange
server?
"michael@.civis.com" wrote:
> I had this error, and it went away once I installed Visual Studio.NET Pro on
> the PC, so there must be some object missing without it.
> Michael
> "winkle60" <winkle60@.discussions.microsoft.com> wrote in message
> news:22141FD2-86C1-4CBC-87F1-6E09FD77CC94@.microsoft.com...
> > Has anyone successfully installed the Exchange Pack for Reporting
> Services?
> >
> > I've attempted a couple of times and continue to get "Object Reference not
> > set to an instance of object", which causes the install to rollback.
> >
> > Does anyone know how to correct this problem?
> >
> > This question was originally posted in 10\04, but there was never an
> answer
> > posted.
> >
>
>|||I'm wondering the same thing. Is the SSQ software piece required? If so, is
that a seperate product you have to buy? I'd be curious to hear from anyone
who made this work. Thanks.
"winkle60" wrote:
> I installed Visual Studio .NET 2003 and was able to complete the install.
> Another question, is there anyway to actually pull data from the Exchange
> system without installing the SSW softeware extraction piece on the Exchange
> server?
> "michael@.civis.com" wrote:
> > I had this error, and it went away once I installed Visual Studio.NET Pro on
> > the PC, so there must be some object missing without it.
> >
> > Michael
> >
> > "winkle60" <winkle60@.discussions.microsoft.com> wrote in message
> > news:22141FD2-86C1-4CBC-87F1-6E09FD77CC94@.microsoft.com...
> > > Has anyone successfully installed the Exchange Pack for Reporting
> > Services?
> > >
> > > I've attempted a couple of times and continue to get "Object Reference not
> > > set to an instance of object", which causes the install to rollback.
> > >
> > > Does anyone know how to correct this problem?
> > >
> > > This question was originally posted in 10\04, but there was never an
> > answer
> > > posted.
> > >
> >
> >
> >

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

Monday, March 12, 2012

Installation Problems - sqlspars.dll

I'm trying to install Reporting Services onto a Win2k3 SBS from the MSDN CD
pack and cannot get past the initial Setup application.
Looking in the event log, I see the following error:
Faulting application SETUP.EXE, version 2000.80.743.0, faulting module
sqlspars.dll, version 2000.80.743.0, fault address 0x00059cf8.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
I just install the app onto a different SBS last week without any issues. I
just updated the machine with the latest Hotfixes from Windows Update.
Any info or troubleshooting suggestions would be appreciated.For those who are interested, a solution was found...
Article #840219 - connecting to SQL Server running on Win2k3
"Kevin D" <kevin@.threeriverstech.com> wrote in message
news:%23l$g442TFHA.584@.TK2MSFTNGP15.phx.gbl...
> I'm trying to install Reporting Services onto a Win2k3 SBS from the MSDN
CD
> pack and cannot get past the initial Setup application.
> Looking in the event log, I see the following error:
> Faulting application SETUP.EXE, version 2000.80.743.0, faulting module
> sqlspars.dll, version 2000.80.743.0, fault address 0x00059cf8.
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
>
> I just install the app onto a different SBS last week without any issues.
I
> just updated the machine with the latest Hotfixes from Windows Update.
> Any info or troubleshooting suggestions would be appreciated.
>

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 ..

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.

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.

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

Right-click the server node in EM, select Properties. Go the Security tab.
The lower third is for changing the service account.

Installation Problem -- SQL Server 2005 Standard & Windows XP Professional Service Pack 2

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.
> > > > >
> > > > >
> > >
> > >
>

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 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!

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.

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

Any ideas?

|||

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

|||

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 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!

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.

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

Any ideas?

|||

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

|||

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

Wednesday, March 28, 2012

Installing feature Pack components with an Application

Monday, March 26, 2012

Installing Exchange Pack for Reporting Services

Monday, March 19, 2012

Installation SQL Server 2005 Express Edition

Monday, March 12, 2012

Installation Problems - sqlspars.dll

installation problem for SQL 2000 Development Edition

Installation Problem -- SQL Server 2005 Standard & Windows XP Professional Service Pack 2

Installation Problem -- SQL Server 2005 Standard & Windows XP Professional Service Pack 2

Friday, March 9, 2012

Installation of SQL server 2005 SP1

Wednesday, March 7, 2012

Installation of Service Pack 4 for SQL 2000

Installation of hotfix package (build 2153) fails

Installation of hotfix package (build 2153) fails

Installation of hotfix package (build 2153) fails

Installation Error

Blog Archive

About Me