Footer rows to skip: installed

Showing posts with label installed. Show all posts

Thursday, March 29, 2012

field not found!

Hello
We have made a database installed it on MS SQL server version 8.0.0.760 (SP3) running on Win NT 4.0 (SP6a) danish. The database is accessed from a program made with delphi 6, and it uses BDE.
The problem is when we start the program, it says :
Field 'V=E6rdi' not found.
This field is accessed by a view called Xsystem:
which contain: select * from Xtable.
This problem is not found on another PC runnig Windows 2000 (sp3). On this PC it work fine.
Any Help pleaseHi,
TRY FOR TEST
CREATE VIEW TESTVIEW AS
SELECT "Værdi" AS Vaerdi from Xtable
>We have made a database installed it on MS SQL server
>version 8.0.0.760 (SP3) running on Win NT 4.0 (SP6a)
>danish. The database is accessed from a program made with
>delphi 6, and it uses BDE.
Check version of Middlewares
MDAC
BDE
--
SHINICHI YONEDA MXL04371@.nifty.ne.jp
Microsoft Most Valuable Professional
MVP for SQL Server 2002-2003|||Thank you Mr. SHINICHI YONEDA for your reply.
I will try this.
>--Original Message--
>Hi,
> TRY FOR TEST
>CREATE VIEW TESTVIEW AS
>SELECT "V=E6rdi" AS Vaerdi from Xtable
>>We have made a database installed it on MS SQL server
>>version 8.0.0.760 (SP3) running on Win NT 4.0 (SP6a)
>>danish. The database is accessed from a program made with
>>delphi 6, and it uses BDE.
> Check version of Middlewares
>MDAC
>BDE
>--
>SHINICHI YONEDA MXL04371@.nifty.ne.jp
>Microsoft Most Valuable Professional
>MVP for SQL Server 2002-2003
>.
>

Friday, March 23, 2012

Feedback after one week of using

Hi all,
Just installed the software on Monday and I already have 2 reports in the
production. This software is so amazing, I did a little demo today at work
and everyone was shocked to see that it took me only 15 minutes to author
one simple report with no line of code! It's very easy to use, I think
coming up with the query is hard. I still think it needs some improvements,
i.e. calendar control (this is a must in any report, I don't believe they
didn't think of it when they released the software!)
I still have some questions though:
1. Since we have SQL and Web servers in the DMZ (they belong to DMZ domain),
we don't want to have users (on separate domain) log on (using DMZ domain
account - no trust allowed) to view and subscribe reports. Is there a way to
set anonymous access to default reports, except for few reports and certain
features that we want to lock out from anonymous users? This helps us a lot
with maintenance and support.
2. Can I connect to 2 or more datasources in the same report?
Thanks in advance for the help.
SQL Server Reporting Services ROCKS!Thanks for using our product.
1. Allowing both anonymous and authenticated access would require to
configure IIS to accept both anonymous and windows integrated
authentication. We found this configuration to be very confusing and asking
customers to avoid it. If you allow both, internet explorer will not know
which one to use. This will cause unstable behavior, sometimes it will try
to go as anonymous and sometimes will ask for user name and password.
One way to solve this problem is to install another report server and point
it to the same database. Then allow only anonymous access on one RS and only
integrated authentication on another. After that you can give rights to
account under which IIS runs anonymous user for some reports. Note that if
you use different boxes for this, you'll have to make this used a domain
user known to both boxes and SQL.
2. Yes, this is possible.
--
Dmitry Vasilevsky, SQL Server Reporting Services Developer
This posting is provided "AS IS" with no warranties, and confers no rights.
--
---
"VNN" <VNN@.hotmail.com> wrote in message
news:enXXJ7lCFHA.1268@.TK2MSFTNGP10.phx.gbl...
> Hi all,
> Just installed the software on Monday and I already have 2 reports in the
> production. This software is so amazing, I did a little demo today at work
> and everyone was shocked to see that it took me only 15 minutes to author
> one simple report with no line of code! It's very easy to use, I think
> coming up with the query is hard. I still think it needs some
improvements,
> i.e. calendar control (this is a must in any report, I don't believe they
> didn't think of it when they released the software!)
> I still have some questions though:
> 1. Since we have SQL and Web servers in the DMZ (they belong to DMZ
domain),
> we don't want to have users (on separate domain) log on (using DMZ domain
> account - no trust allowed) to view and subscribe reports. Is there a way
to
> set anonymous access to default reports, except for few reports and
certain
> features that we want to lock out from anonymous users? This helps us a
lot
> with maintenance and support.
> 2. Can I connect to 2 or more datasources in the same report?
> Thanks in advance for the help.
> SQL Server Reporting Services ROCKS!
>|||Hello Dmitry,
I can echo the comments of VNN. I am into my second week using RS,
apart from initial hiccups of installation, development has been rapid.
I am eagerly awaiting SP2 to see if they can add some features which i
feel can make my life easier.
As you mentioned multiple installations of RS pointing to same DB, I
would like to know more about this.
I am trying to deploy my reports on a remote server. But i am not sure
to use the existing RS DB on a machine in my domain or
Create a new RS db on the server.
Would like to know how to go about
1. Using the existing DB
2. Creating a new DB on the server.
In case of creating a new DB is there a way I can export all the
reports I created on my local machine to the new report server ?
What are the security/account types/auth/IIS issues I need to take care
of.
I am gonna do the installation tommorow and trying to get as much info
as possible.
Thx
Bofo|||When multiple servers are sharing the same SQL DB that is called a web farm
configuration. It is more complicated to setup and it is more expensive (you
have to have an enterprise server license). For what you are doing you
definitely do not need to do this and I would recommend against it (even if
you are already using enterprise). In your case it is best to have
development and production separate. It is very easy to deploy all reports
again. RS has multiple configurations you can deploy to (I have three). You
can deploy all your reports or you can deploy just the ones you need (select
the ones to deploy, right mouse click deploy).
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"RemoteDeploy" <bofobofo@.yahoo.com> wrote in message
news:1107497967.753916.202930@.l41g2000cwc.googlegroups.com...
> Hello Dmitry,
> I can echo the comments of VNN. I am into my second week using RS,
> apart from initial hiccups of installation, development has been rapid.
> I am eagerly awaiting SP2 to see if they can add some features which i
> feel can make my life easier.
> As you mentioned multiple installations of RS pointing to same DB, I
> would like to know more about this.
> I am trying to deploy my reports on a remote server. But i am not sure
> to use the existing RS DB on a machine in my domain or
> Create a new RS db on the server.
> Would like to know how to go about
> 1. Using the existing DB
> 2. Creating a new DB on the server.
> In case of creating a new DB is there a way I can export all the
> reports I created on my local machine to the new report server ?
> What are the security/account types/auth/IIS issues I need to take care
> of.
> I am gonna do the installation tommorow and trying to get as much info
> as possible.
>
> Thx
> Bofo
>

Feature Pack for SP2

I installed SP2 of SQL2005 onto my development machine for testing before using it on the live server.

I saw that MSXML 6 was part of the package and was updated, but what about the OLEDB for MS OLAP 9 driver? Will we see a Feature Pack SP2 soon? Or is it even available and I am just blind?

Or did the OLE DB for OLAP thing not change at all? What version is the latest for this component, and maybe even more important: Where does the dll hide? System32 I suppose, but...

Thanks for pointing out!

Feature pack is part of SP2 package. Here is the link to the new feature pack http://www.microsoft.com/downloads/details.aspx?familyid=50b97994-8453-4998-8226-fa42ec403d17&displaylang=en

You can also find the link on the main page of the SP2 http://www.microsoft.com/sql/sp2.mspx.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

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 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 / Window
s
> 2003 64 bit. The actual version 9.0.2047. Starting from that day the servi
ce
> restart periodically (one time a day) because a fatal exception. The
> application works well until unexpected shutdown. I tried to look at SQL l
og
> 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 direct
ly
> 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'. Logi
n
> 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 n
ot
> 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 que
ry
> 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.RefD
o
>
>
> 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 lo
g
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 0
0
* 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 chan
ge
> 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 0
0
> * 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 0
0
> * 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 0
0
> * & & 00 00 00 00 26 01 01 01 00 02 1f 00 00 26 04 00 00 0
2
> * & §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 2
0
> * APP.16 & ? & 41 50 50 2e 31 36 00 00 26 04 04 3f 01 00 00 00 00 2
6
>
>
> "John Bell" wrote:
>
>|||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 o
f
complexity...
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> If installing the hotfix does not cure this I would call PSS.
> John
> "Catalin NASTAC" wrote:
>

FAT32->NTFS (after SQL Server 2005 Express installation)

I have FAT32 system on my machine and SQL Server 2005 Express installed on it.

Is there will be any problem in SQL Server 2005 Express (in terms of server machine and client machine) if I change my FAT system from FAT32 to NTFS ?

Thanks

Typically you have to format your drive to switch file systems. You'd have to re-install all your software after this, including SQL Express. If you have user databases, you'll need to save copies of them somewhere before formating your disk. Once you've got the system switched over to NTSF, SQL Express will work fine.

If you're using a third party tool to switch file systems without formating, I can't make any claims as to what will happen with SQL Express as we don't test that.

Mike

|||

Thanks Mike.

For unexpacted I should go through Format HDD (or partiation) as NTFS system -way.

Sunday, February 26, 2012

Farsi Collation

I've installed SQL Server 2000 with Arabic collation during the
installation. Yet, I'm not able to search for Farsi strings. What
should I do?topolou (topolou2000@.yahoo.com) writes:
> I've installed SQL Server 2000 with Arabic collation during the
> installation. Yet, I'm not able to search for Farsi strings. What
> should I do?

Unfortunately there is no Farsi collation for SQL Server, but the Arabic
collations are as close as you can come. I have learnt that these
collations does not sort Farsi correctly.

Why you cannot find Farsi data I don't know, but note that you need
to delelimit Unicode literals with N'', for instance N'nisse'.

--
Erland Sommarskog, SQL Server MVP, sommar@.algonet.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp

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 Login

I have installed a brand new msde2000, in order to get SQL
Service Manager. The SQL Service Mgr is installed, and it
shows up in my tray with the little green arrow. I
installed the msde following the instructions in the MS
Knowledge base article 319930, How to Connect to MSDE. I
installed it with the SECURITYMODE=SQL parameter. I used
the osql command to give it a new password. So far so
good. Now, following 319930, I tried a connectivity
test. I get the following error message: Test Connection
failed because of an error in initializing provider.
Login failed for user 'user'.
I am running Windows98SE on a home network.
Any thoughts/help, please!!!!
Hi,
By default, the MSDE was install with OS Authentication . But windows 98
will not support OS authentication.
To use MSDE on Win 98, use have to use SQL Server authentification . To use
the SQL authetification on MSDE, see readme.txt
with the MSDE.
How to change the model after installation: (Need to modify registry)
Default instance:
HKLM\Software\Microsoft\MSSqlserver\MSSqlServer\Lo ginMode
Named instance:
HKLM\Software\Microsoft\Microsoft SQL Server\Instance
Name\MSSQLServer\LoginMode
Change the value to 0 or 2 for mixed-mode or 1 for integrated. (Integrated
is the default setup for the SQL Server 2000 Data Engine.)
Note The 0 and 2 values have the same functionality. They both set the
security to mixed-mode.
To set this key to mixed-mode (SQL Authentication and OS Authentication) ,
follow these steps:
1.. Stop SQL Server and all related services, such as SQLAgent, from the
Services control panel.
2.. Click Start, click Run, type regedt32, and then click OK.
3.. Find the HKEY_LOCAL_MACHINE window on the local computer.
4.. Navigate to the following registry key for the default instance:
HKEY_LOCAL_MACHINE\Software\Microsoft\MSSqlserver\ MSSqlServer
5.. Navigate to the following registry key for a named instance:
HKLM\Software\Microsoft\Microsoft SQL Server\Instance
Name\MSSQLServer\LoginMode
6.. On the right-hand pane, find the value LoginMode and double-click it.
7.. In the DWORD Editor window, set the value to 0 or 2. Also, make sure
that the Hex radio button is selected.
8.. Click OK.
Restart SQL Server and SQL Server Agent services for this change to take
effect.
After these try conecting using the below command from command prompt.
OSQL -Usa -Sserver_name
Thanks
Hari
MCDBA
"fgbrooks" <anonymous@.discussions.microsoft.com> wrote in message
news:7c3801c43173$af8c8b00$a601280a@.phx.gbl...
> I have installed a brand new msde2000, in order to get SQL
> Service Manager. The SQL Service Mgr is installed, and it
> shows up in my tray with the little green arrow. I
> installed the msde following the instructions in the MS
> Knowledge base article 319930, How to Connect to MSDE. I
> installed it with the SECURITYMODE=SQL parameter. I used
> the osql command to give it a new password. So far so
> good. Now, following 319930, I tried a connectivity
> test. I get the following error message: Test Connection
> failed because of an error in initializing provider.
> Login failed for user 'user'.
> I am running Windows98SE on a home network.
> Any thoughts/help, please!!!!
|||Thanks for the reply. I had already checked the Registry
following the instructions of the readme and 319930, and
had previously set it at 2. At a command prompt, if I
type 'osql -U sa', I am prompted for a password (which I
had previously set up), enter it, and it appears that I am
logged in. However, when I try to test this using
a 'test.udl' file as described in 319930, it fails, even
though I enter the same password.
My server name is FRED'S COMPUTER (with a space between
the S and the C). When I try to enter your suggested
command, it reads as follows: osql -U sa -S FRED'S
COMPUTER. This command fails as improper syntax.
Evidently, it doesn't like my server name. Any other
thoughts?
>--Original Message--
>Hi,
>By default, the MSDE was install with OS Authentication .
But windows 98
>will not support OS authentication.
>To use MSDE on Win 98, use have to use SQL Server
authentification . To use
>the SQL authetification on MSDE, see readme.txt
>with the MSDE.
>How to change the model after installation: (Need to
modify registry)
>Default instance:
>HKLM\Software\Microsoft\MSSqlserver\MSSqlServer\L oginMode
>Named instance:
>HKLM\Software\Microsoft\Microsoft SQL Server\Instance
>Name\MSSQLServer\LoginMode
>Change the value to 0 or 2 for mixed-mode or 1 for
integrated. (Integrated
>is the default setup for the SQL Server 2000 Data Engine.)
>Note The 0 and 2 values have the same functionality. They
both set the
>security to mixed-mode.
>To set this key to mixed-mode (SQL Authentication and OS
Authentication) ,
>follow these steps:
> 1.. Stop SQL Server and all related services, such as
SQLAgent, from the
>Services control panel.
> 2.. Click Start, click Run, type regedt32, and then
click OK.
> 3.. Find the HKEY_LOCAL_MACHINE window on the local
computer.
> 4.. Navigate to the following registry key for the
default instance:
>
HKEY_LOCAL_MACHINE\Software\Microsoft\MSSqlserver\ MSSqlServ
er
> 5.. Navigate to the following registry key for a named
instance:
> HKLM\Software\Microsoft\Microsoft SQL Server\Instance
>Name\MSSQLServer\LoginMode
> 6.. On the right-hand pane, find the value LoginMode
and double-click it.
> 7.. In the DWORD Editor window, set the value to 0 or
2. Also, make sure
>that the Hex radio button is selected.
> 8.. Click OK.
>Restart SQL Server and SQL Server Agent services for this
change to take
>effect.
>After these try conecting using the below command from
command prompt.
>OSQL -Usa -Sserver_name
>Thanks
>Hari
>MCDBA
>
>"fgbrooks" <anonymous@.discussions.microsoft.com> wrote in
message[vbcol=seagreen]
>news:7c3801c43173$af8c8b00$a601280a@.phx.gbl...
SQL[vbcol=seagreen]
it[vbcol=seagreen]
I[vbcol=seagreen]
used[vbcol=seagreen]
Connection
>
>.
>

Failure to install SQL 2005 SP2 standard on cluster

Hi,

While I installed on the active node I got the following error: A recently applied update, KB921896, failed to install

After that installation finished , but query the server version I get:

SELECT SERVERPROPERTY('productversion'), SERVERPROPERTY ('productlevel'), SERVERPROPERTY ('edition')

9.00.1399.06 RTM Standard Edition

On the Visual Studion Manager Help About I get 9.00.3042

Error logs are below. Can you please tell me how can I overcome this?

TIA.

I paste here the summary and the hotfix logs of the primary node.

There is also the Redist9_Hotfix_KB921896_SqlSupport.msi.log but it is too long to paste here.

summary.txt:

Time: 07/29/2007 02:46:28.253

KB Number: KB921896

Machine: DB1

OS Version: Microsoft Windows Server 2003 family, Enterprise Edition Service Pack 1 (Build 3790)

Package Language: 1033 (ENU)

Package Platform: x86

Package SP Level: 2

Package Version: 3042

Command-line parameters specified:

Cluster Installation: Yes

Log Location on Passive Nodes:

(DB1) C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix

(DB2) C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix

**********************************************************************************

Prerequisites Check & Status

SQLSupport: Passed

**********************************************************************************

Products Detected Language Level Patch Level Platform Edition

Setup Support Files ENU 9.1.2047 x86

Database Services (MSSQLSERVER) ENU RTM 2005.090.1399.00 x86 STANDARD

Integration Services ENU SP1 9.00.2047.00 x86 STANDARD

SQL Server Native Client ENU 9.00.2047.00 x86

Client Components ENU SP1 9.1.2047 x86 STANDARD

MSXML 6.0 Parser ENU 6.00.3883.8 x86

SQLXML4 ENU 9.00.2047.00 x86

Backward Compatibility ENU 8.05.1704 x86

Microsoft SQL Server VSS Writer ENU 9.00.2047.00 x86

**********************************************************************************

Products Disqualified & Reason

Product Reason

**********************************************************************************

Processes Locking Files

Process Name Feature Type User Name PID

**********************************************************************************

Product Installation Status

Product : Setup Support Files

Product Version (Previous): 2047

Product Version (Final) : 3042

Status : Success

Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\Redist9_Hotfix_KB921896_SqlSupport.msi.log

Error Number : 0

Error Description :

Product : Database Services (MSSQLSERVER)

Product Version (Previous): 1399

Product Version (Final) :

Status : Failure

Log File :

Error Number : 11009

Error Description : No passive nodes were successfully patched

Product : Integration Services

Product Version (Previous): 2047

Product Version (Final) : 3042

Status : Success

Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\DTS9_Hotfix_KB921896_sqlrun_dts.msp.log

Error Number : 0

Error Description :

Product : SQL Server Native Client

Product Version (Previous): 2047

Product Version (Final) : 3042

Status : Reboot Required

Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\Redist9_Hotfix_KB921896_sqlncli.msi.log

Error Number : 3010

Error Description :

Product : Client Components

Product Version (Previous): 2047

Product Version (Final) : 3042

Status : Success

Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQLTools9_Hotfix_KB921896_sqlrun_tools.msp.log

Error Number : 0

Error Description :

Product : MSXML 6.0 Parser

Product Version (Previous): 3883

Product Version (Final) : 6.10.1129.0

Status : Success

Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\Redist9_Hotfix_KB921896_msxml6.msi.log

Error Number : 0

Error Description :

Product : SQLXML4

Product Version (Previous): 2047

Product Version (Final) : 3042

Status : Success

Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\Redist9_Hotfix_KB921896_sqlxml4.msi.log

Error Number : 0

Error Description :

Product : Backward Compatibility

Product Version (Previous): 1704

Product Version (Final) : 2004

Status : Success

Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\Redist9_Hotfix_KB921896_SQLServer2005_BC.msi.log

Error Number : 0

Error Description :

Product : Microsoft SQL Server VSS Writer

Product Version (Previous): 2047

Product Version (Final) : 3042

Status : Success

Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\Redist9_Hotfix_KB921896_SqlWriter.msi.log

Error Number : 0

Error Description :

**********************************************************************************

Summary

No passive nodes were successfully patched

Exit Code Returned: 11009

hotfix log:

I paste here only part of the file were I think I see errors (because the post fails on complete logs)

07/29/2007 02:24:37.934 ================================================================================
07/29/2007 02:24:37.949 Hotfix package launched
07/29/2007 02:24:37.965 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
07/29/2007 02:24:37.965 Registry: Read registry key value "CommonFilesDir", string value = C:\Program Files\Common Files
07/29/2007 02:24:37.965 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
07/29/2007 02:24:37.965 Registry: Read registry key value "ProgramFilesDir", string value = C:\Program Files
07/29/2007 02:24:37.980 Local Computer:
07/29/2007 02:24:37.980 Target Details: DB1
07/29/2007 02:24:37.980 commonfilesdir = C:\Program Files\Common Files
07/29/2007 02:24:37.980 lcidsupportdir = f:\33a341363e4f5937131539f1\1033
07/29/2007 02:24:37.980 programfilesdir = C:\Program Files
07/29/2007 02:24:37.980 programfilesdir_wow = C:\Program Files
07/29/2007 02:24:37.980 supportdir = f:\33a341363e4f5937131539f1
07/29/2007 02:24:37.996 supportdirlocal = f:\33a341363e4f5937131539f1
07/29/2007 02:24:37.996 windir = C:\WINDOWS
07/29/2007 02:24:37.996 winsysdir = C:\WINDOWS\system32
07/29/2007 02:24:37.996 winsysdir_wow = C:\WINDOWS\SysWOW64
07/29/2007 02:24:37.996
07/29/2007 02:24:38.012 Enumerating applicable products for this patch
07/29/2007 02:24:38.027 Found Redist 2005 product definition
07/29/2007 02:24:38.121 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
07/29/2007 02:24:38.121 Registry: Read registry key value "CommonFilesDir", string value = C:\Program Files\Common Files
07/29/2007 02:24:38.121 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
07/29/2007 02:24:38.121 Registry: Read registry key value "ProgramFilesDir", string value = C:\Program Files
07/29/2007 02:24:40.105 Found Redist 2005 product definition
07/29/2007 02:24:40.137 Found Redist 2005 product definition
07/29/2007 02:24:40.152 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
07/29/2007 02:24:40.152 Registry: Read registry key value "CommonFilesDir", string value = C:\Program Files\Common Files
07/29/2007 02:24:40.152 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
07/29/2007 02:24:40.152 Registry: Read registry key value "ProgramFilesDir", string value = C:\Program Files
07/29/2007 02:24:56.168 Found SQL 2005 product definition
07/29/2007 02:25:00.293 Enumeration: Determining QFE level for product instance MSSQLSERVER
07/29/2007 02:25:00.309 Enumeration: Associated hotfix build information not found for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\SQLServr.exe
07/29/2007 02:25:00.309 Enumeration: Found following QFE level for product instance MSSQLSERVER: 1399
...

07/29/2007 02:30:06.090 Locked file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\binn\sqlagent90.exe (SQLSERVERAGENT [SQLAGENT90.EXE] - 3284)
07/29/2007 02:30:06.387 Locked file: C:\Program Files\microsoft sql server\90\shared\sqlbrowser.exe (SQLBrowser [sqlbrowser.exe] - 1480)
07/29/2007 02:30:58.137 Attempting to pause the 32 bit ngen queue
07/29/2007 02:30:58.902 Installing product: Redist9
07/29/2007 02:30:58.918 Installing instance: Setup Support Files
07/29/2007 02:30:58.934 Installing target: DB1
07/29/2007 02:30:58.934 Installing file: SqlSupport.msi
07/29/2007 02:30:59.027 Copy Engine: Creating MSI install log file at: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\Redist9_Hotfix_KB921896_SqlSupport.msi.log
07/29/2007 02:30:59.027 Registry: Opened registry key "Software\Policies\Microsoft\Windows\Installer"
07/29/2007 02:30:59.027 Registry: Cannot read registry key value "Debug"
07/29/2007 02:31:29.730 Registry: Opened registry key "Software\Policies\Microsoft\Windows\Installer"
07/29/2007 02:31:29.746 Registry: Cannot read registry key value "Debug"
07/29/2007 02:31:29.762 Copy Engine: Installed file: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\Cache\SQLSupport\x86\1033\SqlSupport.msi
07/29/2007 02:31:29.762 Installed target: DB1
07/29/2007 02:31:30.027 Installed instance: Setup Support Files
07/29/2007 02:31:30.043 Installed product: Redist9
07/29/2007 02:31:30.043 Installing product: SQL9
07/29/2007 02:31:30.043 Installing instance: MSSQLSERVER
07/29/2007 02:31:30.059 Enumerating passive cluster nodes
07/29/2007 02:31:30.574 Patching available passive node: DB2
07/29/2007 02:31:30.574 Patching passive node: DB2
07/29/2007 02:31:30.590 Waiting for first completed passive node
07/29/2007 02:31:30.934 Task Scheduler: Created remote folder for product instance target \\DB2
07/29/2007 02:31:49.387 Task Scheduler: Transferred payload to remote product instance target \\DB2
07/29/2007 02:31:49.402 Task Scheduler: Transferred payload to remote product instance target \\DB2
07/29/2007 02:31:49.574 Task Scheduler: Error, cannot create scheduled task for product instance target \\DB2
07/29/2007 02:31:50.449 Task Scheduler: Removed remote folder for product instance target \\DB2
07/29/2007 02:31:50.449 Error, remote process failed for product instance target
07/29/2007 02:31:50.449 Exit code for passive node: DB2 = 1603
07/29/2007 02:31:50.590 The following exception occurred: No passive nodes were successfully patched Date: 07/29/2007 02:31:50.590 File: \depot\sqlvault\stable\setupmainl1\setup\sqlse\sqlsedll\instance.cpp Line: 3422
07/29/2007 02:31:51.449 Watson: Param1 = Unknown
07/29/2007 02:31:51.465 Watson: Param2 = 0x2b01
07/29/2007 02:31:51.465 Watson: Param3 = Unknown
07/29/2007 02:31:51.465 Watson: Param4 = 0x0
07/29/2007 02:31:51.465 Watson: Param5 = instance.cpp@.3422
07/29/2007 02:31:51.465 Watson: Param6 = Unknown
07/29/2007 02:31:51.480 Watson: Param7 = SQL9
07/29/2007 02:31:51.480 Watson: Param8 = Hotfix@.
07/29/2007 02:31:51.480 Watson: Param9 = x86
07/29/2007 02:31:51.480 Watson: Param10 = 3042
07/29/2007 02:31:51.480 Installed product: SQL9
07/29/2007 02:31:51.480 Installing product: DTS9
07/29/2007 02:31:51.496 Installing instance: Integration Services
07/29/2007 02:31:51.496 Installing target: DB1
07/29/2007 02:31:51.512 Installing file: sqlrun_dts.msp
07/29/2007 02:31:51.512 Copy Engine: Creating MSP install log file at: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\DTS9_Hotfix_KB921896_sqlrun_dts.msp.log

...

Hey, did you resolve this? I'm running into the same issue.

Thanks,

Failure to install SQL 2005 SP2 standard on cluster

Hi,

While I installed on the active node I got the following error: A recently applied update, KB921896, failed to install

After that installation finished , but query the server version I get:

SELECT SERVERPROPERTY('productversion'), SERVERPROPERTY ('productlevel'), SERVERPROPERTY ('edition')

9.00.1399.06 RTM Standard Edition

On the Visual Studion Manager Help About I get 9.00.3042

Error logs are below. Can you please tell me how can I overcome this?

TIA.

I paste here the summary and the hotfix logs of the primary node.

There is also the Redist9_Hotfix_KB921896_SqlSupport.msi.log but it is too long to paste here.

summary.txt:

Time: 07/29/2007 02:46:28.253

KB Number: KB921896

Machine: DB1

OS Version: Microsoft Windows Server 2003 family, Enterprise Edition Service Pack 1 (Build 3790)

Package Language: 1033 (ENU)

Package Platform: x86

Package SP Level: 2

Package Version: 3042

Command-line parameters specified:

Cluster Installation: Yes

Log Location on Passive Nodes:

(DB1) C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix

(DB2) C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix

**********************************************************************************

Prerequisites Check & Status

SQLSupport: Passed

**********************************************************************************

Products Detected Language Level Patch Level Platform Edition

Setup Support Files ENU 9.1.2047 x86

Database Services (MSSQLSERVER) ENU RTM 2005.090.1399.00 x86 STANDARD

Integration Services ENU SP1 9.00.2047.00 x86 STANDARD

SQL Server Native Client ENU 9.00.2047.00 x86

Client Components ENU SP1 9.1.2047 x86 STANDARD

MSXML 6.0 Parser ENU 6.00.3883.8 x86

SQLXML4 ENU 9.00.2047.00 x86

Backward Compatibility ENU 8.05.1704 x86

Microsoft SQL Server VSS Writer ENU 9.00.2047.00 x86

**********************************************************************************

Products Disqualified & Reason

Product Reason

**********************************************************************************

Processes Locking Files

Process Name Feature Type User Name PID

**********************************************************************************

Product Installation Status

Product : Setup Support Files

Product Version (Previous): 2047

Product Version (Final) : 3042

Status : Success

Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\Redist9_Hotfix_KB921896_SqlSupport.msi.log

Error Number : 0

Error Description :

Product : Database Services (MSSQLSERVER)

Product Version (Previous): 1399

Product Version (Final) :

Status : Failure

Log File :

Error Number : 11009

Error Description : No passive nodes were successfully patched

Product : Integration Services

Product Version (Previous): 2047

Product Version (Final) : 3042

Status : Success

Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\DTS9_Hotfix_KB921896_sqlrun_dts.msp.log

Error Number : 0

Error Description :

Product : SQL Server Native Client

Product Version (Previous): 2047

Product Version (Final) : 3042

Status : Reboot Required

Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\Redist9_Hotfix_KB921896_sqlncli.msi.log

Error Number : 3010

Error Description :

Product : Client Components

Product Version (Previous): 2047

Product Version (Final) : 3042

Status : Success

Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQLTools9_Hotfix_KB921896_sqlrun_tools.msp.log

Error Number : 0

Error Description :

Product : MSXML 6.0 Parser

Product Version (Previous): 3883

Product Version (Final) : 6.10.1129.0

Status : Success

Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\Redist9_Hotfix_KB921896_msxml6.msi.log

Error Number : 0

Error Description :

Product : SQLXML4

Product Version (Previous): 2047

Product Version (Final) : 3042

Status : Success

Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\Redist9_Hotfix_KB921896_sqlxml4.msi.log

Error Number : 0

Error Description :

Product : Backward Compatibility

Product Version (Previous): 1704

Product Version (Final) : 2004

Status : Success

Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\Redist9_Hotfix_KB921896_SQLServer2005_BC.msi.log

Error Number : 0

Error Description :

Product : Microsoft SQL Server VSS Writer

Product Version (Previous): 2047

Product Version (Final) : 3042

Status : Success

Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\Redist9_Hotfix_KB921896_SqlWriter.msi.log

Error Number : 0

Error Description :

**********************************************************************************

Summary

No passive nodes were successfully patched

Exit Code Returned: 11009

hotfix log:

I paste here only part of the file were I think I see errors (because the post fails on complete logs)

...

Hey, did you resolve this? I'm running into the same issue.

Thanks,

Failure to create a Report Project within Visual Studio 2003

I'm having a problem creating a Report Project within Visual Studio. I have
VS.NET 2003 installed and I had then installed Sql Reporting Services with
the latest service pack. If I try and then create a reporting project within
a pre-existing solution, it gives me the following error.
Class already exists.
I looked at the knowledge base and it seems that this behaviour is caused by
a mis-behaving add-in. Subsequently, I disabled all of my add-ins within the
add-in manager and tested again. The problem still exists.
Any other ideas on what I should try?
Thanks,
Darren.On Thu, 7 Apr 2005 07:55:02 -0700, "dmpenner"
<dmpenner@.discussions.microsoft.com> wrote:
>I'm having a problem creating a Report Project within Visual Studio. I have
>VS.NET 2003 installed and I had then installed Sql Reporting Services with
>the latest service pack. If I try and then create a reporting project within
>a pre-existing solution, it gives me the following error.
>Class already exists.
>I looked at the knowledge base and it seems that this behaviour is caused by
>a mis-behaving add-in. Subsequently, I disabled all of my add-ins within the
>add-in manager and tested again. The problem still exists.
>Any other ideas on what I should try?
>Thanks,
>Darren.
Darren,
If you try to create a new project from the File menu (choose the
Wizard option for speed) does that create a working report or not?
Andrew Watt
MVP - InfoPath|||Andrew,
Just tried creating a new report project from the file menu and I still get
the same "Class already exists" message. If I look in my local directory
where I'm trying to create the new project, a folder is created there with a
virtually empty .rptproj file with the following contents.
<?xml version="1.0"?>
<Project xmlns:xsi="http://www.w3.org/2000/10/XMLSchema-instance"
xmlns:xsd="">http://www.w3.org/2000/10/XMLSchema">
<DataSources />
<Reports />
</Project>
I can't however, see the project in the solution explorer and it doesn't
seem to be added to the solution file. Any other suggestions?
Thanks,
Darren.
"Andrew Watt [MVP - InfoPath]" wrote:
> On Thu, 7 Apr 2005 07:55:02 -0700, "dmpenner"
> <dmpenner@.discussions.microsoft.com> wrote:
> >I'm having a problem creating a Report Project within Visual Studio. I have
> >VS.NET 2003 installed and I had then installed Sql Reporting Services with
> >the latest service pack. If I try and then create a reporting project within
> >a pre-existing solution, it gives me the following error.
> >
> >Class already exists.
> >
> >I looked at the knowledge base and it seems that this behaviour is caused by
> >a mis-behaving add-in. Subsequently, I disabled all of my add-ins within the
> >add-in manager and tested again. The problem still exists.
> >
> >Any other ideas on what I should try?
> >
> >Thanks,
> >Darren.
> Darren,
> If you try to create a new project from the File menu (choose the
> Wizard option for speed) does that create a working report or not?
> Andrew Watt
> MVP - InfoPath
>|||Darren,
This isn't something I have seen before so the following questions are
simply trying to identify more clearly your specific
setup/circumstances.
Can you describe your setup in more detail? Which add-ins do you have?
When did you disable them?
Have you ever (I assume not, but want to be clear) created an RS
report successfully on that machine?
Apart from RS is Visual Studio working normally?
Andrew Watt
MVP - InfoPath
On Thu, 7 Apr 2005 08:55:03 -0700, "dmpenner"
<dmpenner@.discussions.microsoft.com> wrote:
>Andrew,
>Just tried creating a new report project from the file menu and I still get
>the same "Class already exists" message. If I look in my local directory
>where I'm trying to create the new project, a folder is created there with a
>virtually empty .rptproj file with the following contents.
><?xml version="1.0"?>
><Project xmlns:xsi="http://www.w3.org/2000/10/XMLSchema-instance"
>xmlns:xsd="">http://www.w3.org/2000/10/XMLSchema">
> <DataSources />
> <Reports />
></Project>
>I can't however, see the project in the solution explorer and it doesn't
>seem to be added to the solution file. Any other suggestions?
>Thanks,
>Darren.
>"Andrew Watt [MVP - InfoPath]" wrote:
>> On Thu, 7 Apr 2005 07:55:02 -0700, "dmpenner"
>> <dmpenner@.discussions.microsoft.com> wrote:
>> >I'm having a problem creating a Report Project within Visual Studio. I have
>> >VS.NET 2003 installed and I had then installed Sql Reporting Services with
>> >the latest service pack. If I try and then create a reporting project within
>> >a pre-existing solution, it gives me the following error.
>> >
>> >Class already exists.
>> >
>> >I looked at the knowledge base and it seems that this behaviour is caused by
>> >a mis-behaving add-in. Subsequently, I disabled all of my add-ins within the
>> >add-in manager and tested again. The problem still exists.
>> >
>> >Any other ideas on what I should try?
>> >
>> >Thanks,
>> >Darren.
>> Darren,
>> If you try to create a new project from the File menu (choose the
>> Wizard option for speed) does that create a working report or not?
>> Andrew Watt
>> MVP - InfoPath

Failure to authendicate domain/users

I have several access databases in mind to migrate to SQL server. I installed MS SQL 2005 Express on my machine. I will have procedures to run with authorizations beyond that of a common user, such as database administrative work where server agent is not available, I may rely on users' log-on prompt to do some maintenance work. However, I cannot get the EXEC AS 'Domain\User' to work. The procedures can be created OK. But whenever they are called, the following message shows up:

Msg 15404, Level 16, State 19, Procedure XXX, Line 0
Could not obtain information about Windows NT group/user 'Domain\User', error code 0xea.

I tried to tweak with the account under which the server service is running. There are three options under built-in account: Local system, Local service, and Network Service. My understanding is that Network Service will use the log-on of the current user of the computer. I have admin right of the computer. None of the three options work. Additionally, when I specify an account (my own account), it's the same thing.

The procedure xp_logininfo always fails when I query a specific domain\user.

The ADHelper is configured to run manually.

I could not think of other ways to get a possible solution. Any help is much appreciated.

hi,

try having a look at http://support.microsoft.com/kb/834124/en-us

regards

|||

Hi, there,

I did several times. The problem is that the article does not contain an explanation of state 19. It has explanations for state 21 and above. Do you have any idea what state 19 relates to?

Thanks,

Sunday, February 19, 2012

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

Thursday, March 29, 2012

field not found!

Friday, March 23, 2012

Feedback after one week of using

Feature Pack for SP2

Monday, March 19, 2012

Fatal error exception after SP installation

Fatal error exception after SP installation

FAT32->NTFS (after SQL Server 2005 Express installation)

Sunday, February 26, 2012

Farsi Collation

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 Login

Failure to install SQL 2005 SP2 standard on cluster

Failure to install SQL 2005 SP2 standard on cluster

Failure to create a Report Project within Visual Studio 2003

Failure to authendicate domain/users

Sunday, February 19, 2012

Failure installing SQL Server 2005 SP 1

Footer rows to skip

Blog Archive

About Me