Footer rows to skip: windows

Showing posts with label windows. Show all posts

Monday, March 19, 2012

Fatal error exception after SP installation

Hello, I installed one week ago the last SQL SP on SQL 2k5 64 bit / Windows
2003 64 bit. The actual version 9.0.2047. Starting from that day the service
restart periodically (one time a day) because a fatal exception. The
application works well until unexpected shutdown. I tried to look at SQL log
and the log files... Most of them are like in chinese for me...
I had nothing of this before I installed the SP. Probably it is not directly
linked to SP, but I don't kow where to start from? Could it the memory (I
intend to upgrade to 9GB anyway...)
What I can see for instance is the SQL log and dump file:
2006-10-25 09:01:19.32 spid9s SQL Trace stopped. Trace ID = '2'. Login
Name = 'sa'.
2006-10-25 10:50:22.32 spid402 ex_raise2: Exception raised, major=86,
minor=24, state=116, severity=16, attempting to create symptom dump
2006-10-25 10:50:22.35 spid402 Using 'dbghelp.dll' version '4.0.5'
2006-10-25 10:50:23.91 spid402 **Dump thread - spid = 402, PSS = 0x00000000DEC8BF00, EC = 0x00000000DEC8BF10
2006-10-25 10:50:23.91 spid402 *
2006-10-25 10:50:23.91 spid402 * User initiated stack dump. This is not
a server exception dump.
2006-10-25 10:50:23.91 spid402 *
2006-10-25 10:50:23.94 spid402 ***Stack Dump being sent to C:\Program
Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\SQLDump1347.txt
2006-10-25 10:50:23.94 spid402 *
*******************************************************************************
2006-10-25 10:50:23.94 spid402 *
2006-10-25 10:50:23.94 spid402 * BEGIN STACK DUMP:
2006-10-25 10:50:23.94 spid402 * 10/25/06 10:50:23 spid 402
2006-10-25 10:50:23.94 spid402 *
2006-10-25 10:50:23.94 spid402 * ex_raise2: Exception raised, major=86,
minor=24, state=116, severity=16
2006-10-25 10:50:23.94 spid402 *
2006-10-25 10:50:23.94 spid402 * Input Buffer 510 bytes -
2006-10-25 10:50:23.94 spid402 * select doc.RefDoc,
RefDocDet_Manque = (select top 1 D.RefDoc
.....
2006-10-25 10:50:27.12 spid402 Error: 8624, Severity: 16, State: 116.
2006-10-25 10:50:27.12 spid402 Internal Query Processor Error: The query
processor could not produce a query plan. For more information, contact
Customer Support Services.
2006-10-25 10:50:34.04 spid402 ex_raise2: Exception raised, major=86,
minor=24, state=116, severity=16, attempting to create symptom dump
and in the dump file:
=====================================================================
BugCheck Dump
=====================================================================
This file is generated by Microsoft SQL Server
version 9.00.2047.00
upon detection of fatal unexpected error. Please return this file,
the query or program that produced the bugcheck, the database and
the error log, and any other pertinent information with a Service Request.
Computer type is AT/AT COMPATIBLE.
Current time is 10:50:34 10/25/06.
4 Unknown CPU 9., 2205 Mhz processor (s).
Windows NT 5.2 Build 3790 CSD Service Pack 1.
Memory
MemoryLoad = 96%
Total Physical = 4951 MB
Available Physical = 180 MB
Total Page File = 6629 MB
Available Page File = 1933 MB
Total Virtual = 8388607 MB
Available Virtual = 8383305 MB
**Dump thread - spid = 402, PSS = 0x00000000DEC8BF00, EC = 0x00000000DEC8BF10
*
* User initiated stack dump. This is not a server exception dump.
*
***Stack Dump being sent to C:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\LOG\SQLDump1348.txt
*
*******************************************************************************
*
* BEGIN STACK DUMP:
* 10/25/06 10:50:34 spid 402
*
* ex_raise2: Exception raised, major=86, minor=24, state=116, severity=16
*
* Input Buffer 510 bytes -
* select doc.RefDoc, RefDocDet_Manque = (select top 1 D.RefDo
Thnaks in advance for any helpHi
Error 8624 is an internal SQL Server error so you may want to contact PSS.
Where is the query select doc.RefDoc, RefDocDet_Manque = (select top 1
D.RefDoc...?
John
"Catalin NASTAC" wrote:
> Hello, I installed one week ago the last SQL SP on SQL 2k5 64 bit / Windows
> 2003 64 bit. The actual version 9.0.2047. Starting from that day the service
> restart periodically (one time a day) because a fatal exception. The
> application works well until unexpected shutdown. I tried to look at SQL log
> and the log files... Most of them are like in chinese for me...
> I had nothing of this before I installed the SP. Probably it is not directly
> linked to SP, but I don't kow where to start from? Could it the memory (I
> intend to upgrade to 9GB anyway...)
> What I can see for instance is the SQL log and dump file:
> 2006-10-25 09:01:19.32 spid9s SQL Trace stopped. Trace ID = '2'. Login
> Name = 'sa'.
> 2006-10-25 10:50:22.32 spid402 ex_raise2: Exception raised, major=86,
> minor=24, state=116, severity=16, attempting to create symptom dump
> 2006-10-25 10:50:22.35 spid402 Using 'dbghelp.dll' version '4.0.5'
> 2006-10-25 10:50:23.91 spid402 **Dump thread - spid = 402, PSS => 0x00000000DEC8BF00, EC = 0x00000000DEC8BF10
> 2006-10-25 10:50:23.91 spid402 *
> 2006-10-25 10:50:23.91 spid402 * User initiated stack dump. This is not
> a server exception dump.
> 2006-10-25 10:50:23.91 spid402 *
> 2006-10-25 10:50:23.94 spid402 ***Stack Dump being sent to C:\Program
> Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\SQLDump1347.txt
> 2006-10-25 10:50:23.94 spid402 *
> *******************************************************************************
> 2006-10-25 10:50:23.94 spid402 *
> 2006-10-25 10:50:23.94 spid402 * BEGIN STACK DUMP:
> 2006-10-25 10:50:23.94 spid402 * 10/25/06 10:50:23 spid 402
> 2006-10-25 10:50:23.94 spid402 *
> 2006-10-25 10:50:23.94 spid402 * ex_raise2: Exception raised, major=86,
> minor=24, state=116, severity=16
> 2006-10-25 10:50:23.94 spid402 *
> 2006-10-25 10:50:23.94 spid402 * Input Buffer 510 bytes -
> 2006-10-25 10:50:23.94 spid402 * select doc.RefDoc,
> RefDocDet_Manque = (select top 1 D.RefDoc
> .....
> 2006-10-25 10:50:27.12 spid402 Error: 8624, Severity: 16, State: 116.
> 2006-10-25 10:50:27.12 spid402 Internal Query Processor Error: The query
> processor could not produce a query plan. For more information, contact
> Customer Support Services.
> 2006-10-25 10:50:34.04 spid402 ex_raise2: Exception raised, major=86,
> minor=24, state=116, severity=16, attempting to create symptom dump
>
> and in the dump file:
> =====================================================================> BugCheck Dump
> =====================================================================>
> This file is generated by Microsoft SQL Server
> version 9.00.2047.00
> upon detection of fatal unexpected error. Please return this file,
> the query or program that produced the bugcheck, the database and
> the error log, and any other pertinent information with a Service Request.
>
>
> Computer type is AT/AT COMPATIBLE.
> Current time is 10:50:34 10/25/06.
> 4 Unknown CPU 9., 2205 Mhz processor (s).
> Windows NT 5.2 Build 3790 CSD Service Pack 1.
>
> Memory
> MemoryLoad = 96%
> Total Physical = 4951 MB
> Available Physical = 180 MB
> Total Page File = 6629 MB
> Available Page File = 1933 MB
> Total Virtual = 8388607 MB
> Available Virtual = 8383305 MB
> **Dump thread - spid = 402, PSS = 0x00000000DEC8BF00, EC => 0x00000000DEC8BF10
> *
> * User initiated stack dump. This is not a server exception dump.
> *
> ***Stack Dump being sent to C:\Program Files\Microsoft SQL
> Server\MSSQL.1\MSSQL\LOG\SQLDump1348.txt
> *
> *******************************************************************************
> *
> * BEGIN STACK DUMP:
> * 10/25/06 10:50:34 spid 402
> *
> * ex_raise2: Exception raised, major=86, minor=24, state=116, severity=16
> *
> * Input Buffer 510 bytes -
> * select doc.RefDoc, RefDocDet_Manque = (select top 1 D.RefDo
>
>
> Thnaks in advance for any help|||That query is a script file that I execute occasionally. It worked without
problems and it makes no problem except that day.
But all the others fatal errors are generated not by file scripts, but by
stored procs. But it is not the same each time... For example in the next log
is stated dbo.ts3_clsAPI_Membres_Upt.
I will install today the patch kb918222 (buid 2153) to see if it will change
something...
I also verify all my SPs and views, functions to use ANSI_NULL ON
Another log file:
Memory
MemoryLoad = 94%
Total Physical = 4951 MB
Available Physical = 273 MB
Total Page File = 6629 MB
Available Page File = 1585 MB
Total Virtual = 8388607 MB
Available Virtual = 8383233 MB
***Stack Dump being sent to C:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\LOG\SQLDump2164.txt
SqlDumpExceptionHandler: Process 61 generated fatal exception c0000005
EXCEPTION_ACCESS_VIOLATION. SQL Server is
terminating this process.
*
*******************************************************************************
*
* BEGIN STACK DUMP:
* 10/26/06 16:32:32 spid 61
*
*
* Exception Address = 0000000001595ECD Module(sqlservr+0000000000595ECD)
* Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
* Access Violation occurred writing address 000000016CBF3010
* Input Buffer 255 bytes -
* d b o . t s 3 _ 1a 00 64 00 62 00 6f 00 2e 00 74 00 73 00 33 00 5f 00
* c l s A P I _ M e 63 00 6c 00 73 00 41 00 50 00 49 00 5f 00 4d 00 65 00
* m b r e s _ U p t 6d 00 62 00 72 00 65 00 73 00 5f 00 55 00 70 00 74 00
* & & 00 00 00 00 26 01 01 01 00 02 1f 00 00 26 04 00 00 02
* & Â§2 2 1f 00 00 26 01 01 02 00 00 a7 32 00 09 04 00 01 32 08
* AVETSIAN Â§2 00 41 56 45 54 53 49 41 4e 00 00 a7 32 00 09 04 00 01
* 2 Rousana Â§Â? 32 07 00 52 6f 75 73 61 6e 61 00 00 a7 96 00 09 04 00
* 2 527 DUDEMAINE 01 32 14 00 35 32 37 20 44 55 44 45 4d 41 49 4e 45 20
* APP.16 & ? & 41 50 50 2e 31 36 00 00 26 04 04 3f 01 00 00 00 00 26
"John Bell" wrote:
> Hi
> Error 8624 is an internal SQL Server error so you may want to contact PSS.
> Where is the query select doc.RefDoc, RefDocDet_Manque = (select top 1
> D.RefDoc...?
> John
>|||Hi
If installing the hotfix does not cure this I would call PSS.
John
"Catalin NASTAC" wrote:
> That query is a script file that I execute occasionally. It worked without
> problems and it makes no problem except that day.
> But all the others fatal errors are generated not by file scripts, but by
> stored procs. But it is not the same each time... For example in the next log
> is stated dbo.ts3_clsAPI_Membres_Upt.
> I will install today the patch kb918222 (buid 2153) to see if it will change
> something...
> I also verify all my SPs and views, functions to use ANSI_NULL ON
> Another log file:
> Memory
> MemoryLoad = 94%
> Total Physical = 4951 MB
> Available Physical = 273 MB
> Total Page File = 6629 MB
> Available Page File = 1585 MB
> Total Virtual = 8388607 MB
> Available Virtual = 8383233 MB
> ***Stack Dump being sent to C:\Program Files\Microsoft SQL
> Server\MSSQL.1\MSSQL\LOG\SQLDump2164.txt
> SqlDumpExceptionHandler: Process 61 generated fatal exception c0000005
> EXCEPTION_ACCESS_VIOLATION. SQL Server is
> terminating this process.
> *
> *******************************************************************************
> *
> * BEGIN STACK DUMP:
> * 10/26/06 16:32:32 spid 61
> *
> *
> * Exception Address = 0000000001595ECD Module(sqlservr+0000000000595ECD)
> * Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
> * Access Violation occurred writing address 000000016CBF3010
> * Input Buffer 255 bytes -
> * d b o . t s 3 _ 1a 00 64 00 62 00 6f 00 2e 00 74 00 73 00 33 00 5f 00
> * c l s A P I _ M e 63 00 6c 00 73 00 41 00 50 00 49 00 5f 00 4d 00 65 00
> * m b r e s _ U p t 6d 00 62 00 72 00 65 00 73 00 5f 00 55 00 70 00 74 00
> * & & 00 00 00 00 26 01 01 01 00 02 1f 00 00 26 04 00 00 02
> * & Â§2 2 1f 00 00 26 01 01 02 00 00 a7 32 00 09 04 00 01 32 08
> * AVETSIAN Â§2 00 41 56 45 54 53 49 41 4e 00 00 a7 32 00 09 04 00 01
> * 2 Rousana Â§Â? 32 07 00 52 6f 75 73 61 6e 61 00 00 a7 96 00 09 04 00
> * 2 527 DUDEMAINE 01 32 14 00 35 32 37 20 44 55 44 45 4d 41 49 4e 45 20
> * APP.16 & ? & 41 50 50 2e 31 36 00 00 26 04 04 3f 01 00 00 00 00 26
>
>
> "John Bell" wrote:
> > Hi
> >
> > Error 8624 is an internal SQL Server error so you may want to contact PSS.
> >
> > Where is the query select doc.RefDoc, RefDocDet_Manque = (select top 1
> > D.RefDoc...?
> >
> > John
> >
>|||Finally, I think that I find the problem. I have a function like GetParam
(@.ParamName as varchar) as int and a procedure that it was called very often,
and it contains:
select Param1 = dbo.GetParam (@.Param1),
Param2 = dbo.GetParam (@.Param2),
Param3 = dbo.GetParam (@.Param3),
...
and so on, around 100 parammeters is the same select, using the same
function (don't tell me that makes nosense to return 100 columns. It is an
old application made by others :o(
The function GetParam called another function which called another funtion
and so on. It seems the the optimizer crashes because of the complexity of
this. It works with some users connected in the same time, but with arround
100 users is the same time...
I rewrite the procedure to store each value in scalar variables (set
@.ParamValue1 = dbo.GetParam (@.Param1) and so on) and select @.ParamValue1,
@.ParamValue2 etc.
Now it works 5 times faster (the SP) and without crashes. Seems that I have
to consider all old SPs, views and functions to try to eliminate this kind of
complexity...
"John Bell" wrote:
> Hi
> If installing the hotfix does not cure this I would call PSS.
> John
> "Catalin NASTAC" wrote:
> > That query is a script file that I execute occasionally. It worked without
> > problems and it makes no problem except that day.
> >
> > But all the others fatal errors are generated not by file scripts, but by
> > stored procs. But it is not the same each time... For example in the next log
> > is stated dbo.ts3_clsAPI_Membres_Upt.
> >
> > I will install today the patch kb918222 (buid 2153) to see if it will change
> > something...
> > I also verify all my SPs and views, functions to use ANSI_NULL ON
> >
> > Another log file:
> > Memory
> > MemoryLoad = 94%
> > Total Physical = 4951 MB
> > Available Physical = 273 MB
> > Total Page File = 6629 MB
> > Available Page File = 1585 MB
> > Total Virtual = 8388607 MB
> > Available Virtual = 8383233 MB
> > ***Stack Dump being sent to C:\Program Files\Microsoft SQL
> > Server\MSSQL.1\MSSQL\LOG\SQLDump2164.txt
> > SqlDumpExceptionHandler: Process 61 generated fatal exception c0000005
> > EXCEPTION_ACCESS_VIOLATION. SQL Server is
> > terminating this process.
> >
> > *
> > *******************************************************************************
> > *
> >
> > * BEGIN STACK DUMP:
> >
> > * 10/26/06 16:32:32 spid 61
> >
> > *
> >
> > *
> >
> > * Exception Address = 0000000001595ECD Module(sqlservr+0000000000595ECD)
> >
> > * Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
> >
> > * Access Violation occurred writing address 000000016CBF3010
> >
> > * Input Buffer 255 bytes -
> >
> > * d b o . t s 3 _ 1a 00 64 00 62 00 6f 00 2e 00 74 00 73 00 33 00 5f 00
> >
> > * c l s A P I _ M e 63 00 6c 00 73 00 41 00 50 00 49 00 5f 00 4d 00 65 00
> >
> > * m b r e s _ U p t 6d 00 62 00 72 00 65 00 73 00 5f 00 55 00 70 00 74 00
> >
> > * & & 00 00 00 00 26 01 01 01 00 02 1f 00 00 26 04 00 00 02
> >
> > * & Â§2 2 1f 00 00 26 01 01 02 00 00 a7 32 00 09 04 00 01 32 08
> >
> > * AVETSIAN Â§2 00 41 56 45 54 53 49 41 4e 00 00 a7 32 00 09 04 00 01
> >
> > * 2 Rousana Â§Â? 32 07 00 52 6f 75 73 61 6e 61 00 00 a7 96 00 09 04 00
> >
> > * 2 527 DUDEMAINE 01 32 14 00 35 32 37 20 44 55 44 45 4d 41 49 4e 45 20
> >
> > * APP.16 & ? & 41 50 50 2e 31 36 00 00 26 04 04 3f 01 00 00 00 00 26
> >
> >
> >
> >
> > "John Bell" wrote:
> >
> > > Hi
> > >
> > > Error 8624 is an internal SQL Server error so you may want to contact PSS.
> > >
> > > Where is the query select doc.RefDoc, RefDocDet_Manque = (select top 1
> > > D.RefDoc...?
> > >
> > > John
> > >
> >

Fatal error

Dear All,
I got a WIndows 2000 Server running MSDE. Recently it keep crashing with
this error in event viewer:
Error: 0, Severity: 19, State: 0
SqlDumpExceptionHandler: Process 58 generated fatal exception c0000005
EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
I have updated it to SP4 still the same problem. Does anyone know
anything about this error message please
Thank you very muchHi Andrew
Have you checked the windows event log for any messages that may indicate an
issue, also it is probably worth running CHKDSK to make sure that there is no
corruption on the disc drives.
John
"Huy (Andrew) V Nguyen" wrote:
> Dear All,
> I got a WIndows 2000 Server running MSDE. Recently it keep crashing with
> this error in event viewer:
> Error: 0, Severity: 19, State: 0
> SqlDumpExceptionHandler: Process 58 generated fatal exception c0000005
> EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
> I have updated it to SP4 still the same problem. Does anyone know
> anything about this error message please
> Thank you very much
>|||Hi John,
The error message is from Events Viewer. I check everything else at
around the same time nothing special. I had scheduled a CHKDSK to run
yesterday with no issues found. Any other idea please?
Andrew
John Bell wrote:
> Hi Andrew
> Have you checked the windows event log for any messages that may indicate an
> issue, also it is probably worth running CHKDSK to make sure that there is no
> corruption on the disc drives.
> John
> "Huy (Andrew) V Nguyen" wrote:
>> Dear All,
>> I got a WIndows 2000 Server running MSDE. Recently it keep crashing with
>> this error in event viewer:
>> Error: 0, Severity: 19, State: 0
>> SqlDumpExceptionHandler: Process 58 generated fatal exception c0000005
>> EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
>> I have updated it to SP4 still the same problem. Does anyone know
>> anything about this error message please
>> Thank you very much|||Hi Andrew
Without knowing what was actually happening on the server at the time, it is
almost impossible to say what has caused this error. There are many issues
where the message may have been generated http://tinyurl.com/7kglf but I have
not found one that was not cured prior to SP4. You may want to raise a call
with PSS if this persists
http://support.microsoft.com/common/international.aspx?rdpath=1&gprid=2855&c1=508
John
"Huy (Andrew) V Nguyen" wrote:
> Hi John,
> The error message is from Events Viewer. I check everything else at
> around the same time nothing special. I had scheduled a CHKDSK to run
> yesterday with no issues found. Any other idea please?
> Andrew
> John Bell wrote:
> > Hi Andrew
> >
> > Have you checked the windows event log for any messages that may indicate an
> > issue, also it is probably worth running CHKDSK to make sure that there is no
> > corruption on the disc drives.
> >
> > John
> >
> > "Huy (Andrew) V Nguyen" wrote:
> >
> >> Dear All,
> >>
> >> I got a WIndows 2000 Server running MSDE. Recently it keep crashing with
> >> this error in event viewer:
> >>
> >> Error: 0, Severity: 19, State: 0
> >> SqlDumpExceptionHandler: Process 58 generated fatal exception c0000005
> >> EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
> >>
> >> I have updated it to SP4 still the same problem. Does anyone know
> >> anything about this error message please
> >>
> >> Thank you very much
> >>
>|||I am getting the same error
SqlDumpExceptionHandler: Process 58 generated fatal exception running sQL
2000 sp4 and latest windows 2000 OS updates.
But I am also running in a clustered environment.
One of my servers never crashes (with pretty much the same patches etc.)
while the other server continues to crash.
I starting to think it has something to do with the actual machine hardware
and not the software.

Fatal error

Dear All,
I got a Windows 2000 Server running MSDE. Recently it keep crashing with
this error in event viewer:
Error: 0, Severity: 19, State: 0
SqlDumpExceptionHandler: Process 58 generated fatal exception c0000005
EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
I have updated it to SP4 still the same problem. Does anyone know
anything about this error message please
Thank you very muchHi Andrew
Have you checked the windows event log for any messages that may indicate an
issue, also it is probably worth running CHKDSK to make sure that there is n
o
corruption on the disc drives.
John
"Huy (Andrew) V Nguyen" wrote:

> Dear All,
> I got a Windows 2000 Server running MSDE. Recently it keep crashing with
> this error in event viewer:
> Error: 0, Severity: 19, State: 0
> SqlDumpExceptionHandler: Process 58 generated fatal exception c0000005
> EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
> I have updated it to SP4 still the same problem. Does anyone know
> anything about this error message please
> Thank you very much
>|||Hi John,
The error message is from Events Viewer. I check everything else at
around the same time nothing special. I had scheduled a CHKDSK to run
yesterday with no issues found. Any other idea please?
Andrew
John Bell wrote:[vbcol=seagreen]
> Hi Andrew
> Have you checked the windows event log for any messages that may indicate
an
> issue, also it is probably worth running CHKDSK to make sure that there is
no
> corruption on the disc drives.
> John
> "Huy (Andrew) V Nguyen" wrote:
>|||Hi Andrew
Without knowing what was actually happening on the server at the time, it is
almost impossible to say what has caused this error. There are many issues
where the message may have been generated http://tinyurl.com/7kglf but I hav
e
not found one that was not cured prior to SP4. You may want to raise a call
with PSS if this persists
[url]http://support.microsoft.com/common/international.aspx?rdpath=1&gprid=2855&c1=508[
/url]
John
"Huy (Andrew) V Nguyen" wrote:

> Hi John,
> The error message is from Events Viewer. I check everything else at
> around the same time nothing special. I had scheduled a CHKDSK to run
> yesterday with no issues found. Any other idea please?
> Andrew
> John Bell wrote:
>|||I am getting the same error
SqlDumpExceptionHandler: Process 58 generated fatal exception running sQL
2000 sp4 and latest Windows 2000 OS updates.
But I am also running in a clustered environment.
One of my servers never crashes (with pretty much the same patches etc.)
while the other server continues to crash.
I starting to think it has something to do with the actual machine hardware
and not the software.

Friday, February 24, 2012

Failure when installing SQL 2005 SP1 on Windows 2003 Server

Hello.

When I installed SQL 2005 SP1 on Windows 2003 Server, I received the following message:

"A recently applied update, KB913090, failed to install."

At the end, "Database Services" was marked as "Failure".

I have tried everything I could find in the knowledge base and on the forums, but still

was not able to install SP1.

For example:

http://support.microsoft.com/default.aspx?scid=kb;en-us;918357

Any insights would be greatly appreciated.

Can you search your hotfix logs (%WINDIR%/hotfix directory) for the text string "value 3" and include the 10-20 lines above it? That should give us a more descriptive error.

Thanks,
Sam Lester (MSFT)|||

MSI (s) (B0!C0) [22:08:08:355]: Note: 1: 2262 2: _sqlAction 3: -2147287038
MSI (s) (B0!C0) [22:08:08:355]: Transforming table _sqlAction.

MSI (s) (B0!C0) [22:08:08:355]: Note: 1: 2262 2: _sqlAction 3: -2147287038
<Func Name='SetCAContext'>
<EndFunc Name='SetCAContext' Return='T' GetLastError='0'>
Doing Action: CommitSqlUpgrade
PerfTime Start: CommitSqlUpgrade : Sat Sep 23 22:08:08 2006
<Func Name='ComponentUpgrade'>
There was a failure during installation search up in this log file for this message:
SQL Server Setup failed to parse the SQL script "C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Upgrade\procsyst.sql". The error code is The system cannot find the file specified.
. To continue, correct the problem, and then run SQL Server Setup again.
<EndFunc Name='ComponentUpgrade' Return='2' GetLastError='0'>
PerfTime Stop: CommitSqlUpgrade : Sat Sep 23 22:08:08 2006
Gathering darwin properties for failure handling.
<EndFunc Name='LaunchFunction' Return='2' GetLastError='0'>
MSI (s) (B0:A8) [22:08:09:370]: Transforming table InstallExecuteSequence.

MSI (s) (B0:A8) [22:08:09:370]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (B0:A8) [22:08:09:370]: Transforming table InstallExecuteSequence.

MSI (s) (B0:A8) [22:08:09:370]: Transforming table InstallExecuteSequence.

MSI (s) (B0:A8) [22:08:09:370]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (B0:A8) [22:08:09:370]: Transforming table InstallExecuteSequence.

MSI (s) (B0:A8) [22:08:09:370]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
Action ended 22:08:09: CommitSqlUpgrade.D20239D7_E87C_40C9_9837_E70B8D4882C2. Return value 3.

|||

It seams there was a failure during previous upgrade. At this point I would suggest that you go to AddRemove Programs select MS SQL Server 2005 and Change. Then you select the SQL instance that failed and Database Engine. Proceed to Change or Remove Instance dialog and I assume there is an option Complete the suspended installation so select that one.

It is possible that setup needs access to the original installation media so if you installed from CD insert it before launching the setup.

|||

That did the trick!

Many thanks for the help.

|||

I ran into this issue and resolved it by changing the registry. Under: Software\Policies\Microsoft\Windows\Installer, I found that DisableMSI was not set to 0. For some reason it was set to 2. After changing this to 0, SP1 installed fine.

What's strange is there is nothing that should've set this to registry entry to 2.

Failure when installing SQL 2005 SP1 on Windows 2003 Server

Hello.

When I installed SQL 2005 SP1 on Windows 2003 Server, I received the following message:

"A recently applied update, KB913090, failed to install."

At the end, "Database Services" was marked as "Failure".

I have tried everything I could find in the knowledge base and on the forums, but still

was not able to install SP1.

For example:

http://support.microsoft.com/default.aspx?scid=kb;en-us;918357

Any insights would be greatly appreciated.

Can you search your hotfix logs (%WINDIR%/hotfix directory) for the text string "value 3" and include the 10-20 lines above it? That should give us a more descriptive error.

Thanks,
Sam Lester (MSFT)|||

MSI (s) (B0!C0) [22:08:08:355]: Note: 1: 2262 2: _sqlAction 3: -2147287038
MSI (s) (B0!C0) [22:08:08:355]: Transforming table _sqlAction.

MSI (s) (B0:A8) [22:08:09:370]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (B0:A8) [22:08:09:370]: Transforming table InstallExecuteSequence.

MSI (s) (B0:A8) [22:08:09:370]: Transforming table InstallExecuteSequence.

MSI (s) (B0:A8) [22:08:09:370]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (B0:A8) [22:08:09:370]: Transforming table InstallExecuteSequence.

MSI (s) (B0:A8) [22:08:09:370]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
Action ended 22:08:09: CommitSqlUpgrade.D20239D7_E87C_40C9_9837_E70B8D4882C2. Return value 3.

|||

It is possible that setup needs access to the original installation media so if you installed from CD insert it before launching the setup.

|||

That did the trick!

Many thanks for the help.

|||

What's strange is there is nothing that should've set this to registry entry to 2.

Failure when installing SQL 2005 SP1 on Windows 2003 Server

Hello.

When I installed SQL 2005 SP1 on Windows 2003 Server, I received the following message:

"A recently applied update, KB913090, failed to install."

At the end, "Database Services" was marked as "Failure".

I have tried everything I could find in the knowledge base and on the forums, but still

was not able to install SP1.

For example:

http://support.microsoft.com/default.aspx?scid=kb;en-us;918357

Any insights would be greatly appreciated.

Can you search your hotfix logs (%WINDIR%/hotfix directory) for the text string "value 3" and include the 10-20 lines above it? That should give us a more descriptive error.

Thanks,
Sam Lester (MSFT)|||

MSI (s) (B0!C0) [22:08:08:355]: Note: 1: 2262 2: _sqlAction 3: -2147287038
MSI (s) (B0!C0) [22:08:08:355]: Transforming table _sqlAction.

MSI (s) (B0:A8) [22:08:09:370]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (B0:A8) [22:08:09:370]: Transforming table InstallExecuteSequence.

MSI (s) (B0:A8) [22:08:09:370]: Transforming table InstallExecuteSequence.

MSI (s) (B0:A8) [22:08:09:370]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (B0:A8) [22:08:09:370]: Transforming table InstallExecuteSequence.

MSI (s) (B0:A8) [22:08:09:370]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
Action ended 22:08:09: CommitSqlUpgrade.D20239D7_E87C_40C9_9837_E70B8D4882C2. Return value 3.

|||

It is possible that setup needs access to the original installation media so if you installed from CD insert it before launching the setup.

|||

That did the trick!

Many thanks for the help.

|||

What's strange is there is nothing that should've set this to registry entry to 2.

Failure to Install SQL Server 2005 SP1

I am trying to apply MS SQL Server 2005 SP1 onto a 2 node cluster running Windows Server 2003, but it fails for SQL and the Analysis Services components of SQL Server, the error I am getting is MSP returned 1603 for both components. I have tried rebooting the machines but still get the same issue, the only additional dependency for SQL that I have added is for a 2nd physical disk. log details are below.

Many thanks in advance for any help you can provide on this problem.

01/15/2007 12:26:26.937 ================================================================================
01/15/2007 12:26:26.953 Hotfix package launched
01/15/2007 12:26:27.703 Product discovery successfully completed during the install process for MSSQLSERVER
01/15/2007 12:26:27.703 SP Level check successfully completed during the install process for MSSQLSERVER
01/15/2007 12:26:27.734 Product language check successfully completed during the install process for MSSQLSERVER
01/15/2007 12:26:27.750 Product version check successfully completed during the install process for MSSQLSERVER
01/15/2007 12:26:27.765 Command-line instance name check completed during the install process
01/15/2007 12:26:27.781 Baseline build check completed during the install process
01/15/2007 12:29:31.734 Attempting to install instance: MSSQLSERVER
01/15/2007 12:29:31.750 Enumerating passive cluster nodes
01/15/2007 12:29:31.765 Patching available passive node: GBCONV1A002N03
01/15/2007 12:29:31.781 Attempting to patch running passive node: GBCONV1A002N03
01/15/2007 12:29:31.796 Waiting for first successfully completed passive node
01/15/2007 12:29:31.812 Successfully created remote folder for product instance target \\GBCONV1A002N03
01/15/2007 12:29:45.859 Successfully transferred payload to remote product instance target \\GBCONV1A002N03
01/15/2007 12:29:45.921 Successfully transferred payload to remote product instance target \\GBCONV1A002N03
01/15/2007 12:29:45.953 Successfully created new scheduled task for product instance target \\GBCONV1A002N03
01/15/2007 12:29:46.562 Successfully saved new scheduled task for product instance target \\GBCONV1A002N03
01/15/2007 12:29:46.625 Successfully created scheduled task for product instance target \\GBCONV1A002N03
01/15/2007 12:29:46.640 Successfully started scheduled task for product instance target \\GBCONV1A002N03
01/15/2007 12:29:46.656 Successfully started scheduled task for product instance target \\GBCONV1A002N03
01/15/2007 12:30:28.671 Scheduled task for product instance target has completed
01/15/2007 12:30:28.687 Waiting for exit code from scheduled task for product instance target \\GBCONV1A002N03
01/15/2007 12:30:33.718 Received exit code 0 from scheduled task for product instance target \\GBCONV1A002N03
01/15/2007 12:30:33.734 Result code for scheduled task for product instance target has been received
01/15/2007 12:30:33.734 Removed scheduled task for product instance target \\GBCONV1A002N03
01/15/2007 12:30:33.921 Successfully removed remote folder for product instance target \\GBCONV1A002N03
01/15/2007 12:30:33.953 Remote process completed for product instance target
01/15/2007 12:30:33.968 Exit code for passive node: GBCONV1A002N03 = 0
01/15/2007 12:30:36.812 First successful passive node has been completed
01/15/2007 12:30:36.828 Attempting to install target: GBCONV1A002N01
01/15/2007 12:30:36.843 Attempting to check for locked files: sqlrun_as.msp
01/15/2007 12:30:36.890 Attempting to check for locked files: \\GBCONV1A002N01\d$\bbf7e520a98fb7a70c268b90\HotFixAS\Files\sqlrun_as.msp
01/15/2007 12:30:36.906 Creating MSP locked file check log at: C:\WINDOWS\Hotfix\OLAP9\Logs\OLAP9_Hotfix_KB913090_sqlrun_as.msp.out
01/15/2007 12:30:41.015 MSP returned 1603: A fatal error occurred during installation.
01/15/2007 12:30:41.140 Unable to check MSP file: \\GBCONV1A002N01\d$\bbf7e520a98fb7a70c268b90\HotFixAS\Files\sqlrun_as.msp
01/15/2007 12:30:41.156 The following exception occurred: Unable to install Windows Installer MSP file Date: 01/15/2007 12:30:41.156 File: \depot\sqlvault\setupmain\setup\sqlse\sqlsedll\copyengine.cpp Line: 689
01/15/2007 12:30:41.187 Attempting to finalize cluster instance: MSSQLSERVER
01/15/2007 12:30:41.203 Waiting for all running passive nodes to complete their patch
01/15/2007 12:30:41.218 All running passive nodes have completed their patch
01/15/2007 12:30:41.234 Successfully finalized cluster instance: MSSQLSERVER
01/15/2007 12:30:41.234 Failed to install instance: MSSQLSERVER
01/15/2007 12:30:41.250
01/15/2007 12:30:41.281 Product Status Summary:
01/15/2007 12:30:41.296 Product: SQL Server Native Client (64-bit)
01/15/2007 12:30:41.312 SQL Server Native Client (64-bit) (RTM ) - Success
01/15/2007 12:30:41.312
01/15/2007 12:30:41.328 Product: Setup Support Files (64-bit)
01/15/2007 12:30:41.343 Setup Support Files (64-bit) (RTM ) - Success
01/15/2007 12:30:41.359
01/15/2007 12:30:41.375 Product: Database Services (64-bit)
01/15/2007 12:30:41.390 Database Services (64-bit) (SP1 2047 ENU GBCONV1A002V03) - Failure
01/15/2007 12:30:41.406 Analysis Services (64-bit) (RTM 1399 ENU GBCONV1A002V04) - Failure
01/15/2007 12:30:41.406
01/15/2007 12:30:41.421 Product: Integration Services (64-bit)
01/15/2007 12:30:41.437 Integration Services (64-bit) (SP1 2047 ENU) - Not Applied
01/15/2007 12:30:41.453
01/15/2007 12:30:41.468 Product: MSXML 6.0 Parser (64-bit)
01/15/2007 12:30:41.484 MSXML 6.0 Parser (64-bit) (RTM ) - Not Applied
01/15/2007 12:30:41.484
01/15/2007 12:30:41.515 Product: Backward Compatibility (64-bit)
01/15/2007 12:30:41.531 Backward Compatibility (64-bit) (RTM ) - Not Applied
01/15/2007 12:30:41.546
01/15/2007 12:30:41.546 Product: Microsoft SQL Server VSS Writer (64-bit)
01/15/2007 12:30:41.578 Microsoft SQL Server VSS Writer (64-bit) (RTM ) - Not Applied
01/15/2007 12:30:41.593
01/15/2007 12:48:34.562 Hotfix package closed

Based on the provided log file, it finishes successfully on the passive node but fails on the

01/15/2007 12:29:31.796 Waiting for first successfully completed passive node
01/15/2007 12:29:31.812 Successfully created remote folder for product instance target \\GBCONV1A002N03
01/15/2007 12:29:45.859 Successfully transferred payload to remote product instance target \\GBCONV1A002N03
01/15/2007 12:29:45.921 Successfully transferred payload to remote product instance target \\GBCONV1A002N03
01/15/2007 12:29:45.953 Successfully created new scheduled task for product instance target \\GBCONV1A002N03
01/15/2007 12:29:46.562 Successfully saved new scheduled task for product instance target \\GBCONV1A002N03
01/15/2007 12:29:46.625 Successfully created scheduled task for product instance target \\GBCONV1A002N03
01/15/2007 12:29:46.640 Successfully started scheduled task for product instance target \\GBCONV1A002N03
01/15/2007 12:29:46.656 Successfully started scheduled task for product instance target \\GBCONV1A002N03
01/15/2007 12:30:28.671 Scheduled task for product instance target has completed
01/15/2007 12:30:28.687 Waiting for exit code from scheduled task for product instance target \\GBCONV1A002N03
01/15/2007 12:30:33.718 Received exit code 0 from scheduled task for product instance target \\GBCONV1A002N03
01/15/2007 12:30:33.734 Result code for scheduled task for product instance target has been received
01/15/2007 12:30:33.734 Removed scheduled task for product instance target \\GBCONV1A002N03
01/15/2007 12:30:33.921 Successfully removed remote folder for product instance target \\GBCONV1A002N03
01/15/2007 12:30:33.953 Remote process completed for product instance target
01/15/2007 12:30:33.968 Exit code for passive node: GBCONV1A002N03 = 0
01/15/2007 12:30:36.812 First successful passive node has been completed

The error is recorded in the following section. It seems that the package is corrupted. For more details, more log files should be provided for further investigation. The log files are located under %Windows%\HOTFIX\.

01/15/2007 12:30:36.843 Attempting to check for locked files: sqlrun_as.msp
01/15/2007 12:30:36.890 Attempting to check for locked files: \\GBCONV1A002N01\d$\bbf7e520a98fb7a70c268b90\HotFixAS\Files\sqlrun_as.msp
01/15/2007 12:30:36.906 Creating MSP locked file check log at: C:\WINDOWS\Hotfix\OLAP9\Logs\OLAP9_Hotfix_KB913090_sqlrun_as.msp.out
01/15/2007 12:30:41.015 MSP returned 1603: A fatal error occurred during installation.
01/15/2007 12:30:41.140 Unable to check MSP file: \\GBCONV1A002N01\d$\bbf7e520a98fb7a70c268b90\HotFixAS\Files\sqlrun_as.msp
01/15/2007 12:30:41.156 The following exception occurred: Unable to install Windows Installer MSP file Date: 01/15/2007 12:30:41.156 File: \depot\sqlvault\setupmain\setup\sqlse\sqlsedll\copyengine.cpp Line: 689
01/15/2007 12:30:41.187 Attempting to finalize cluster instance: MSSQLSERVER
01/15/2007 12:30:41.203 Waiting for all running passive nodes to complete their patch
01/15/2007 12:30:41.218 All running passive nodes have completed their patch
01/15/2007 12:30:41.234 Successfully finalized cluster instance: MSSQLSERVER
01/15/2007 12:30:41.234 Failed to install instance: MSSQLSERVER
01/15/2007 12:30:41.250

failure to install SQL Agent for SQL Express

I just tried to install the file:

D:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\InstallUtil.exe SQLAgent.exe by running it from a command prompt.

and got an error that the system could not find the file or one of its components. It is a farily new install. I do not think I've lost any files any time.

What is the problem?

Thanks.

SQL Express does not include SQL Agent, you need to purchase at least SQL Server Workgroup to get that component.

Mike

Failure to install - XOLEHLP.dll not found

Hello,

I'm trying to install CTP3 of katmai on Windows Server 2004 running inside Virtual PC.

It installs the setup files OK. Straight after that I get an error message box saying "The application has failed to start because XOLEHLP.DLL was not found. Re-installing the application may fix this problem"

Clicking OK gives me another message box with the message "TITLE: Microsoft SQL Server code name Katmai Setup

Failed to load SqlSpars.dll

For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&ProdVer=10.0.1019.17&EvtSrc=setup.rll&EvtID=50005&EvtType=setup%5csqlsetupactions.cpp%40InvokeSqlSetupDllAction%40sqls%3a%3aInvokeSqlSetupDllAction%3a%3aperform%400x57

BUTTONS:

The link doesn't give me anything useful.

Then I get the familiar 'Send Error Report' dialog. I DID send the error report.

I'm stumped. Anyone got any ideas?

Thanks

Jamie

Moving over to the new Katmai forums|||Jamie,

I assume you tried to instell it on a Win 2003 box (not 2004) :-)

Anyway, that box (or rather VM in your case), how was it created in the first place? Have you done any funky stuff with MSDTC, as xolehlp.dll is a helper file for the DTC. Also, the Katmai installation, was it from the iso or a "normal" installation?

Niels
|||

Hey there Niels,

You're right. Win2k3. DOH!!!

Interesting your comments about DTC - I'll have a play around with that. I certainly haven't done any changes on the box - its as vanilla as it gets. Standard OS install. I'm using the katmai executable - i.e. not the .iso

This is all at home and I am now at work. I'll have another play around later this evening.

Thanks

Jamie

|||OK, try the ISO and see if it helps.

Niels

Failure to install - XOLEHLP.dll not found

Hello,

I'm trying to install CTP3 of katmai on Windows Server 2004 running inside Virtual PC.

Clicking OK gives me another message box with the message "TITLE: Microsoft SQL Server code name Katmai Setup

Failed to load SqlSpars.dll

BUTTONS:

The link doesn't give me anything useful.

Then I get the familiar 'Send Error Report' dialog. I DID send the error report.

I'm stumped. Anyone got any ideas?

Thanks

Jamie

Moving over to the new Katmai forums|||Jamie,

I assume you tried to instell it on a Win 2003 box (not 2004) :-)

Niels
|||

Hey there Niels,

You're right. Win2k3. DOH!!!

This is all at home and I am now at work. I'll have another play around later this evening.

Thanks

Jamie

|||OK, try the ISO and see if it helps.

Niels

Failure setting security rights on user account SQLServer2005BrowserUser${computerName}

I'm trying to install SQL Server 2005 Express on a Windows 2000 server, but I'm getting the following error message:

"Failure setting security rights on user account SQLServer2005BrowserUser${computerName}"

Can anyone help me please?

Help!! Need to get the sql server installed so I can demo to my client!

Sunday, February 19, 2012

Failure sending email in subscriptions

I am running SQL 2005, I have the latest service pack on SQL 2005 and also on
the Windows 2003 server. This is on a single server. I am using my Exchange
2003 server as my SMTP server which is on a different server with the same
subnet.
-When a domain user schedules a subscription it won't send an email.
-When a domain admin schdules a subscription the email will get sent.
-When a domain user schedules a subscription with ONLY the link option, it
will send an email and the user can access the link.
- I tried setting my RS config to use Local System and also Network Service,
and that did not make a difference.
In the RS logs I get the error...
Success: False, Status: Failure sending mail: The report server has
encountered a configuration error. See the report server log files for more
information., DeliveryExtension: Report Server Email, Report: Purchase
Requests Ordered But Not Received, Attempt 0
I also get an error in the Windows event log when a subscription is created
or editted, but I'm not sure if it is related. The error is..
Report Server (MSSQLSERVER) cannot load the Report Server DocumentLibrary
extension.
Here is my RS config file..
<RSEmailDPConfiguration>
<SMTPServer>192.168.100.200</SMTPServer>
<SMTPServerPort></SMTPServerPort>
<SMTPAccountName></SMTPAccountName>
<SMTPConnectionTimeout></SMTPConnectionTimeout>
<SMTPServerPickupDirectory></SMTPServerPickupDirectory>
<SMTPUseSSL></SMTPUseSSL>
<SendUsing>2</SendUsing>
<SMTPAuthenticate></SMTPAuthenticate>
<From>hqjobs01Reports@.trinitystairs.com</From>
<EmbeddedRenderFormats>
<RenderingExtension>MHTML</RenderingExtension>
</EmbeddedRenderFormats>
<PrivilegedUserRenderFormats></PrivilegedUserRenderFormats>
<ExcludedRenderFormats>
<RenderingExtension>HTMLOWC</RenderingExtension>
<RenderingExtension>NULL</RenderingExtension>
<RenderingExtension>RGDI</RenderingExtension>
</ExcludedRenderFormats>
<SendEmailToUserAlias>False</SendEmailToUserAlias>
<DefaultHostName>trinitystairs.com</DefaultHostName>
<PermittedHosts></PermittedHosts>
</RSEmailDPConfiguration>
Please Help!Having the same problem. Tried everything and nothing worked. Next week I
will try transferring all my services to run under domain admin account to
see if that helps.
These are some of the links where I have explained my problem. Read just to
make sure that we have same problem.
http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=1769187&SiteID=17
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?dg=microsoft.public.opsmgr.reporting&mid=c1fdce30-5db0-487d-931e-1e17cb0c387b
"Pablo" wrote:
> I am running SQL 2005, I have the latest service pack on SQL 2005 and also on
> the Windows 2003 server. This is on a single server. I am using my Exchange
> 2003 server as my SMTP server which is on a different server with the same
> subnet.
> -When a domain user schedules a subscription it won't send an email.
> -When a domain admin schdules a subscription the email will get sent.
> -When a domain user schedules a subscription with ONLY the link option, it
> will send an email and the user can access the link.
> - I tried setting my RS config to use Local System and also Network Service,
> and that did not make a difference.
> In the RS logs I get the error...
> Success: False, Status: Failure sending mail: The report server has
> encountered a configuration error. See the report server log files for more
> information., DeliveryExtension: Report Server Email, Report: Purchase
> Requests Ordered But Not Received, Attempt 0
>
> I also get an error in the Windows event log when a subscription is created
> or editted, but I'm not sure if it is related. The error is..
> Report Server (MSSQLSERVER) cannot load the Report Server DocumentLibrary
> extension.
> Here is my RS config file..
> <RSEmailDPConfiguration>
> <SMTPServer>192.168.100.200</SMTPServer>
> <SMTPServerPort></SMTPServerPort>
> <SMTPAccountName></SMTPAccountName>
> <SMTPConnectionTimeout></SMTPConnectionTimeout>
> <SMTPServerPickupDirectory></SMTPServerPickupDirectory>
> <SMTPUseSSL></SMTPUseSSL>
> <SendUsing>2</SendUsing>
> <SMTPAuthenticate></SMTPAuthenticate>
> <From>hqjobs01Reports@.trinitystairs.com</From>
> <EmbeddedRenderFormats>
> <RenderingExtension>MHTML</RenderingExtension>
> </EmbeddedRenderFormats>
> <PrivilegedUserRenderFormats></PrivilegedUserRenderFormats>
> <ExcludedRenderFormats>
> <RenderingExtension>HTMLOWC</RenderingExtension>
> <RenderingExtension>NULL</RenderingExtension>
> <RenderingExtension>RGDI</RenderingExtension>
> </ExcludedRenderFormats>
> <SendEmailToUserAlias>False</SendEmailToUserAlias>
> <DefaultHostName>trinitystairs.com</DefaultHostName>
> <PermittedHosts></PermittedHosts>
> </RSEmailDPConfiguration>
>
> Please Help!

Failure installing SQL Server 2005 SP 1

Windows XP Pro
SQL Server 2005 Express
SQL Server 2005 Standard

I installed the service pack for SQL Server Express first.
Then I tried to install the service pack for SQL Server. I got the error message, "A recently applied update, KB913090, failed to install.", while it was upgrading the Setup Support Files.

Jonathan Allen

Log follows...

04/22/2006 10:52:34.781 ================================================================================
04/22/2006 10:52:34.875 Hotfix package launched
04/22/2006 10:53:47.546 Attempting to install instance: SQL Server Native Client
04/22/2006 10:53:47.578 Attempting to install target: RADICALJAY
04/22/2006 10:53:47.593 Attempting to install file: sqlncli.msi
04/22/2006 10:53:47.687 Attempting to install file: \\RADICALJAY\c$\b1f5502657526de4ed0c\HotFixSqlncli\Files\sqlncli.msi
04/22/2006 10:53:47.687 Creating MSI install log file at: C:\WINDOWS\Hotfix\Redist9\Logs\Redist9_Hotfix_KB913090_sqlncli.msi.log
04/22/2006 10:53:47.703 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
04/22/2006 10:53:47.718 Failed to read registry key: Debug
04/22/2006 10:53:49.578 MSP returned 0: The action completed successfully.
04/22/2006 10:53:49.765 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
04/22/2006 10:53:49.781 Failed to read registry key: Debug
04/22/2006 10:53:49.781 Successfully installed file: \\RADICALJAY\c$\b1f5502657526de4ed0c\HotFixSqlncli\Files\sqlncli.msi
04/22/2006 10:53:49.796 Successfully installed target: RADICALJAY
04/22/2006 10:53:49.812 Successfully installed instance: SQL Server Native Client
04/22/2006 10:53:49.828
04/22/2006 10:53:49.828 Product Status Summary:
04/22/2006 10:53:49.843 Product: SQL Server Native Client
04/22/2006 10:53:49.859 SQL Server Native Client (RTM ) - Success
04/22/2006 10:53:49.859
04/22/2006 10:53:49.875 Product: Setup Support Files
04/22/2006 10:53:49.890 Setup Support Files (RTM ) - Not Applied
04/22/2006 10:53:49.890
04/22/2006 10:53:49.906 Product: Database Services
04/22/2006 10:53:49.921 Database Services (RTM 1399 ENU) - Not Applied
04/22/2006 10:53:49.937 Analysis Services (RTM 1399 ENU) - Not Applied
04/22/2006 10:53:49.937 Reporting Services (RTM 1399 ENU) - Not Applied
04/22/2006 10:53:49.953
04/22/2006 10:53:49.968 Product: Database Services
04/22/2006 10:53:49.968 Database Services (SP1 2047 ENU) - NA
04/22/2006 10:53:49.984 Details: Instances of SQL Server Express cannot be updated by using this Service Pack installer. To update instances of SQL Server Express, use the SQL Server Express Service Pack installer.
04/22/2006 10:53:50.000
04/22/2006 10:53:50.015 Product: Notification Services
04/22/2006 10:53:50.015 Notification Services (RTM 1399 ENU) - Not Applied
04/22/2006 10:53:50.031
04/22/2006 10:53:50.046 Product: Integration Services
04/22/2006 10:53:50.046 Integration Services (RTM 1399 ENU) - Not Applied
04/22/2006 10:53:50.062
04/22/2006 10:53:50.078 Product: Client Components
04/22/2006 10:53:50.093 Client Components (RTM 1399 ENU) - Not Applied
04/22/2006 10:53:50.093
04/22/2006 10:53:50.109 Product: MSXML 6.0 Parser
04/22/2006 10:53:50.125 MSXML 6.0 Parser (RTM ) - Not Applied
04/22/2006 10:53:50.125
04/22/2006 10:53:50.140 Product: SQLXML4
04/22/2006 10:53:50.156 SQLXML4 (RTM ) - Not Applied
04/22/2006 10:53:50.171
04/22/2006 10:53:50.171 Product: Backward Compatibility
04/22/2006 10:53:50.187 Backward Compatibility (RTM ) - Not Applied
04/22/2006 10:53:50.203
04/22/2006 10:53:50.203 Product: Microsoft SQL Server VSS Writer
04/22/2006 10:53:50.218 Microsoft SQL Server VSS Writer (RTM ) - Not Applied
04/22/2006 10:53:50.234

This appears to be the log from trying to apply SP1 to your Express instance.

04/22/2006 10:53:49.968 Database Services (SP1 2047 ENU) - NA
04/22/2006 10:53:49.984 Details: Instances of SQL Server Express cannot be updated by using this Service Pack installer. To update instances of SQL Server Express, use the SQL Server Express Service Pack installer.

Can you share out the msp log from the second attempt? The logs are in the %windir%\hotfix folder. If you do a search for "return value 3", that may lead you to the failed component log.

Thanks,
Samuel Lester (MSFT)

|||

This is the new log file from the Service Pack GUI...

04/23/2006 23:12:21.656 ================================================================================
04/23/2006 23:12:21.671 Hotfix package launched
04/23/2006 23:13:02.750 Attempting to install instance: SQL Server Native Client
04/23/2006 23:13:02.796 Attempting to install target: RADICALJAY
04/23/2006 23:13:02.812 Attempting to install file: sqlncli.msi
04/23/2006 23:13:03.031 Attempting to install file: \\RADICALJAY\c$\124b99e6f03eb11ec06df9\HotFixSqlncli\Files\sqlncli.msi
04/23/2006 23:13:03.031 Creating MSI install log file at: C:\WINDOWS\Hotfix\Redist9\Logs\Redist9_Hotfix_KB913090_sqlncli.msi.log
04/23/2006 23:13:03.046 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
04/23/2006 23:13:03.062 Failed to read registry key: Debug
04/23/2006 23:13:05.468 MSP returned 0: The action completed successfully.
04/23/2006 23:13:05.656 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
04/23/2006 23:13:05.687 Failed to read registry key: Debug
04/23/2006 23:13:05.703 Successfully installed file: \\RADICALJAY\c$\124b99e6f03eb11ec06df9\HotFixSqlncli\Files\sqlncli.msi
04/23/2006 23:13:05.718 Successfully installed target: RADICALJAY
04/23/2006 23:13:05.718 Successfully installed instance: SQL Server Native Client
04/23/2006 23:13:05.734
04/23/2006 23:13:05.750 Product Status Summary:
04/23/2006 23:13:05.750 Product: SQL Server Native Client
04/23/2006 23:13:05.765 SQL Server Native Client (RTM ) - Success
04/23/2006 23:13:05.781
04/23/2006 23:13:05.796 Product: Setup Support Files
04/23/2006 23:13:05.796 Setup Support Files (RTM ) - Not Applied
04/23/2006 23:13:05.812
04/23/2006 23:13:05.828 Product: Database Services
04/23/2006 23:13:05.828 Database Services (RTM 1399 ENU) - Not Applied
04/23/2006 23:13:05.843 Analysis Services (RTM 1399 ENU) - Not Applied
04/23/2006 23:13:05.859 Reporting Services (RTM 1399 ENU) - Not Applied
04/23/2006 23:13:05.875
04/23/2006 23:13:05.875 Product: Database Services
04/23/2006 23:13:05.890 Database Services (SP1 2047 ENU) - NA
04/23/2006 23:13:05.906 Details: Instances of SQL Server Express cannot be updated by using this Service Pack installer. To update instances of SQL Server Express, use the SQL Server Express Service Pack installer.
04/23/2006 23:13:05.906
04/23/2006 23:13:05.921 Product: Notification Services
04/23/2006 23:13:05.937 Notification Services (RTM 1399 ENU) - Not Applied
04/23/2006 23:13:05.953
04/23/2006 23:13:05.953 Product: Integration Services
04/23/2006 23:13:05.968 Integration Services (RTM 1399 ENU) - Not Applied
04/23/2006 23:13:05.984
04/23/2006 23:13:05.984 Product: Client Components
04/23/2006 23:13:06.000 Client Components (RTM 1399 ENU) - Not Applied
04/23/2006 23:13:06.031
04/23/2006 23:13:06.046 Product: MSXML 6.0 Parser
04/23/2006 23:13:06.046 MSXML 6.0 Parser (RTM ) - Not Applied
04/23/2006 23:13:06.062
04/23/2006 23:13:06.078 Product: SQLXML4
04/23/2006 23:13:06.078 SQLXML4 (RTM ) - Not Applied
04/23/2006 23:13:06.093
04/23/2006 23:13:06.109 Product: Backward Compatibility
04/23/2006 23:13:06.109 Backward Compatibility (RTM ) - Not Applied
04/23/2006 23:13:06.125
04/23/2006 23:13:06.140 Product: Microsoft SQL Server VSS Writer
04/23/2006 23:13:06.156 Microsoft SQL Server VSS Writer (RTM ) - Not Applied
04/23/2006 23:13:06.156

I didn't find "return value 3", but this was interesting...

"C:\WINDOWS\Hotfix\Redist9\Logs\Redist9_Hotfix_KB913090_SqlSupport.msp.log"

=== Verbose logging started: 4/23/2006 23:13:06 Build type: SHIP UNICODE 3.01.4000.2435 Calling process: C:\WINDOWS\system32\msiexec.exe ===
MSI (c) (30:E8) [23:13:06:375]: Resetting cached policy values
MSI (c) (30:E8) [23:13:06:375]: Machine policy value 'Debug' is 0
MSI (c) (30:E8) [23:13:06:375]: ******* RunEngine:
******* Product: {53F5C3EE-05ED-4830-994B-50B2F0D50FCE}
******* Action:
******* CommandLine: **********
MSI (c) (30:E8) [23:13:06:375]: Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (30:E8) [23:13:06:375]: Grabbed execution mutex.
MSI (c) (30:E8) [23:13:06:375]: Cloaking enabled.
MSI (c) (30:E8) [23:13:06:375]: Attempting to enable all disabled priveleges before calling Install on Server
MSI (c) (30:E8) [23:13:06:390]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (18:88) [23:13:06:390]: Grabbed execution mutex.
MSI (s) (18:9C) [23:13:06:390]: Resetting cached policy values
MSI (s) (18:9C) [23:13:06:390]: Machine policy value 'Debug' is 0
MSI (s) (18:9C) [23:13:06:390]: ******* RunEngine:
******* Product: {53F5C3EE-05ED-4830-994B-50B2F0D50FCE}
******* Action:
******* CommandLine: **********
MSI (s) (18:9C) [23:13:06:390]: Machine policy value 'DisableUserInstalls' is 0
MSI (s) (18:9C) [23:13:06:390]: End dialog not enabled
MSI (s) (18:9C) [23:13:06:390]: Original package ==> c:\WINDOWS\Installer\2b422ff9.msi
MSI (s) (18:9C) [23:13:06:390]: Package we're running from ==> c:\WINDOWS\Installer\2b422ff9.msi
MSI (s) (18:9C) [23:13:06:390]: APPCOMPAT: looking for appcompat database entry with ProductCode '{53F5C3EE-05ED-4830-994B-50B2F0D50FCE}'.
MSI (s) (18:9C) [23:13:06:390]: APPCOMPAT: no matching ProductCode found in database.
MSI (s) (18:9C) [23:13:06:390]: MSCOREE not loaded loading copy from system32
MSI (s) (18:9C) [23:13:06:500]: File will have security applied from OpCode.
MSI (s) (18:9C) [23:13:06:593]: Original patch ==> \\RADICALJAY\c$\124b99e6f03eb11ec06df9\HotFixSqlSupport\Files\SqlSupport.msp
MSI (s) (18:9C) [23:13:06:593]: Patch we're running from ==> C:\WINDOWS\Installer\7d5500e.msp
MSI (s) (18:9C) [23:13:06:593]: SOFTWARE RESTRICTION POLICY: Verifying patch --> '\\RADICALJAY\c$\124b99e6f03eb11ec06df9\HotFixSqlSupport\Files\SqlSupport.msp' against software restriction policy
MSI (s) (18:9C) [23:13:06:593]: Note: 1: 2262 2: DigitalSignature 3: -2147287038
MSI (s) (18:9C) [23:13:06:593]: SOFTWARE RESTRICTION POLICY: \\RADICALJAY\c$\124b99e6f03eb11ec06df9\HotFixSqlSupport\Files\SqlSupport.msp is not digitally signed
MSI (s) (18:9C) [23:13:06:609]: SOFTWARE RESTRICTION POLICY: \\RADICALJAY\c$\124b99e6f03eb11ec06df9\HotFixSqlSupport\Files\SqlSupport.msp is permitted to run at the 'unrestricted' authorization level.
MSI (s) (18:9C) [23:13:06:625]: SequencePatches starts. Product code: {53F5C3EE-05ED-4830-994B-50B2F0D50FCE}, Product version: 9.00.2047.00, Upgrade code: {3A91FA19-A197-467C-850F-0AFE90899371}, Product language 1033
MSI (s) (18:9C) [23:13:06:625]: PATCH SEQUENCER WARNING: \\RADICALJAY\c$\124b99e6f03eb11ec06df9\HotFixSqlSupport\Files\SqlSupport.msp patch will not be sequenced because it does not contain any transform that may apply to product!
MSI (s) (18:9C) [23:13:06:625]: SequencePatches returns success.
MSI (s) (18:9C) [23:13:06:625]: Final Patch Application Order:
MSI (s) (18:9C) [23:13:06:625]: Other Patches:
MSI (s) (18:9C) [23:13:06:625]: Unknown\Absent: {EE92F683-5F5C-4970-BB0B-9AC591B60268} - \\RADICALJAY\c$\124b99e6f03eb11ec06df9\HotFixSqlSupport\Files\SqlSupport.msp
MSI (s) (18:9C) [23:13:06:625]: Product: Microsoft SQL Server Setup Support Files (English) - Update '{EE92F683-5F5C-4970-BB0B-9AC591B60268}' could not be installed. Error code 1642. Additional information is available in the log file C:\WINDOWS\Hotfix\Redist9\Logs\Redist9_Hotfix_KB913090_SqlSupport.msp.log.

MSI (s) (18:9C) [23:13:06:625]: Note: 1: 1708
MSI (s) (18:9C) [23:13:06:625]: Note: 1: 2729
MSI (s) (18:9C) [23:13:06:671]: Note: 1: 2729
MSI (s) (18:9C) [23:13:06:671]: Product: Microsoft SQL Server Setup Support Files (English) -- Installation failed.

MSI (s) (18:9C) [23:13:06:671]: Attempting to delete file C:\WINDOWS\Installer\7d5500e.msp
MSI (s) (18:9C) [23:13:06:671]: MainEngineThread is returning 1642
The upgrade patch cannot be installed by the Windows Installer service because the program to be upgraded may be missing, or the upgrade patch may update a different version of the program. Verify that the program to be upgraded exists on your computer an
d that you have the correct upgrade patch.
c:\WINDOWS\Installer\2b422ff9.msi
MSI (c) (30:E8) [23:13:06:671]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (30:E8) [23:13:06:671]: MainEngineThread is returning 1642
=== Verbose logging stopped: 4/23/2006 23:13:06 ===

|||i got the same error message.|||

We're getting a KB article ready for this.

SP1 fails with "Unable to install Windows Installer MSP file" for "Setup Support Files"
Workaround:

1/ Save the registry contents of:
KeyName: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\90\Bootstrap\MSIRefCount
Value: Uninstall

2/ Uninstall SqlSupport.msi from Add/Remove control panel
3/ Install SqlSupport.msi version 1399 from the RTM media.
4/ Restore the registry contents that were saved in step 1.

|||That did the trick.|||

Thanks Jeffrey!

This worked for me as well. I posted visual instructions on my blog at VSTeamSystemCentral.com.

:{> Andy

|||

Worked for me too. Thanks,

Jonathan

|||

Works for me, too!

THANK YOU!

Robert.

|||

I downloaded SP2 this week and I'm getting what appears to be the same error...was this not resolved as part of the SP2 release? Do the same steps above apply for SP2?

Thanks

Failure installing SQL Server 2005 SP 1

Windows XP Pro
SQL Server 2005 Express
SQL Server 2005 Standard

Jonathan Allen

Log follows...

This appears to be the log from trying to apply SP1 to your Express instance.

Can you share out the msp log from the second attempt? The logs are in the %windir%\hotfix folder. If you do a search for "return value 3", that may lead you to the failed component log.

Thanks,
Samuel Lester (MSFT)

|||

This is the new log file from the Service Pack GUI...

I didn't find "return value 3", but this was interesting...

"C:\WINDOWS\Hotfix\Redist9\Logs\Redist9_Hotfix_KB913090_SqlSupport.msp.log"

|||i got the same error message.|||

We're getting a KB article ready for this.

SP1 fails with "Unable to install Windows Installer MSP file" for "Setup Support Files"
Workaround:

1/ Save the registry contents of:
KeyName: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\90\Bootstrap\MSIRefCount
Value: Uninstall

2/ Uninstall SqlSupport.msi from Add/Remove control panel
3/ Install SqlSupport.msi version 1399 from the RTM media.
4/ Restore the registry contents that were saved in step 1.

|||That did the trick.|||

Thanks Jeffrey!

This worked for me as well. I posted visual instructions on my blog at VSTeamSystemCentral.com.

:{> Andy

|||

Worked for me too. Thanks,

Jonathan

|||

Works for me, too!

THANK YOU!

Robert.

|||

I downloaded SP2 this week and I'm getting what appears to be the same error...was this not resolved as part of the SP2 release? Do the same steps above apply for SP2?

Thanks

Failure installing SQL Server 2005 SP 1

Windows XP Pro
SQL Server 2005 Express
SQL Server 2005 Standard

Jonathan Allen

Log follows...

This appears to be the log from trying to apply SP1 to your Express instance.

Can you share out the msp log from the second attempt? The logs are in the %windir%\hotfix folder. If you do a search for "return value 3", that may lead you to the failed component log.

Thanks,
Samuel Lester (MSFT)

|||

This is the new log file from the Service Pack GUI...

I didn't find "return value 3", but this was interesting...

"C:\WINDOWS\Hotfix\Redist9\Logs\Redist9_Hotfix_KB913090_SqlSupport.msp.log"

|||i got the same error message.|||

We're getting a KB article ready for this.

SP1 fails with "Unable to install Windows Installer MSP file" for "Setup Support Files"
Workaround:

1/ Save the registry contents of:
KeyName: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\90\Bootstrap\MSIRefCount
Value: Uninstall

2/ Uninstall SqlSupport.msi from Add/Remove control panel
3/ Install SqlSupport.msi version 1399 from the RTM media.
4/ Restore the registry contents that were saved in step 1.

|||That did the trick.|||

Thanks Jeffrey!

This worked for me as well. I posted visual instructions on my blog at VSTeamSystemCentral.com.

:{> Andy

|||

Worked for me too. Thanks,

Jonathan

|||

Works for me, too!

THANK YOU!

Robert.

|||

I downloaded SP2 this week and I'm getting what appears to be the same error...was this not resolved as part of the SP2 release? Do the same steps above apply for SP2?

Thanks

Monday, March 19, 2012

Fatal error exception after SP installation

Fatal error

Fatal error

Fatal error

Friday, February 24, 2012

Failure when installing SQL 2005 SP1 on Windows 2003 Server

Failure when installing SQL 2005 SP1 on Windows 2003 Server

Failure when installing SQL 2005 SP1 on Windows 2003 Server

Failure to Install SQL Server 2005 SP1

failure to install SQL Agent for SQL Express

Failure to install - XOLEHLP.dll not found

Failure to install - XOLEHLP.dll not found

Failure setting security rights on user account SQLServer2005BrowserUser${computerName}

Sunday, February 19, 2012

Failure sending email in subscriptions

Failure installing SQL Server 2005 SP 1

Failure installing SQL Server 2005 SP 1

Failure installing SQL Server 2005 SP 1

Footer rows to skip

Blog Archive

About Me