Problem with sql2005-kb918222-x86-enu.exe (cumulative hotfix, build 2153)

Hello,

I do experiment a problem when trying to install the mentionned patch on my Windows XP SP2 machine (fully patched).

Interestingly, the patch works fine for the named instance, which is a "clean" install of SQL Server 2005 SP1, while it fails on the default instance, which is a SQL 2005 SP1 upgraded in place from SQL Server 2000 SP4. Both instances are Developer editions...

The error is along the following lines:

[snip]

08/10/2006 09:22:06.728 Unable to install MSP file: \\DHDHY0J\c$\1c7c01591e524f9a092159a233\hotfixsql\Files\sqlrun_sql.msp
08/10/2006 09:22:06.818 The following exception occurred: Unable to install Windows Installer MSP file Date: 08/10/2006 09:22:06.818 File: \depot\sqlvault\stable\setupmainl1\setup\sqlse\sqlsedll\copyengine.cpp Line: 856
08/10/2006 09:22:06.948
08/10/2006 09:22:06.998 Product Status Summary:
08/10/2006 09:22:07.048 Product: SQL Server Database Services 2005
08/10/2006 09:22:07.088 MSSQLSERVER - Failure
08/10/2006 09:22:07.138 Details: Unable to install Windows Installer MSP file
08/10/2006 09:22:07.228 SQL2K5 - Not Selected
08/10/2006 09:22:07.338
08/10/2006 09:22:42.409 Hotfix package closed

Any thoughts somebody?

Thanks in advance,

Emmanuel

Emmanuel, can you search your %windir%\hotfix\ folder for the text string "value 3" and include the 10 or so lines on each side. This should be in the sqlrun_sql.msp file and will help us troubleshoot.

Thanks,
Samuel Lester (MSFT)

|||

Hello,

thank you for your input. I could not locate the string "value 3" in the file you mentionned. So I put up my sleeves and decided to dig in this 12Mb+ file... Finally, I found a few interesting entries, and could narrow down my problem to security config: on my machine, the service was running as a normal, non-privileged user (i.e. not member of local admins), and to avoid anti-virus slow-down, I had special security placed on key files allowing access to only this very user. (No, I cannot exclude the files from within the anti-virus because of corporate policies).

I changed back, and the setup ran normally. Sorry for the trouble.

Oh Yes, the named instance is not used usually. Just there for having an installation try, and to be able to compare "clean" vs upgrade install. Therefore no special config on this instance ...

With kind regards,

Emmanuel

sql

PROBLEM WITH SQL2000

hello..i have a really big problem with SQL2000 installation, i cant install it, some sql,odbc dll and other files left after i reinstalled OS without removing SQL,maybe 4 months ago and still have them in my pc, bought new HDD but they still exist in my pc :/ used full format of HDD but those files still left after all new installation of OS,i tryed to delete them but they appear again,deleted them from DOS but then i had to reinstall OS again coz windows dont started up.. what can i do ? plz help me some1 to solve this problem..i whant to install SQL2000 again but cant ((

hi keisa,

here's something to lighten up your day.

some versions of SQL server cannot be run on every OS

for example:

You cannot install a SQL server 2000 enterprise edition on windows Xp

because enterprise edition requires a windows server.

regards,

joey

|||

you never mentioned the OS. and sql server Edition and service pack.

please post back full info

Madhu

|||This sounds like a development or testing machine, if so why don't you simply refresh the complete installation from operating system to SQL Server.

Problem with SQL Service Pack 4

I upgraded from SQL 2000 Service Pack 3 to SQL 2000 Service Pack 4. The
install says it completed but after I rebooted and did a select @.@.version it
still shows SP3. I only have a default instance so I know that it installed
on the right instance. Could anyone help me out with this?You can review the setup log for any errors (file called sqlsp.log in the
windows directory). It is perfectly safe to run SP4 again to try and make it
stick (assuming you have the system database backups just in case you need
to regress)
--
HTH,
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
"Leon Parker" <u23479@.uwe> wrote in message news:625d255c1f101@.uwe...
>I upgraded from SQL 2000 Service Pack 3 to SQL 2000 Service Pack 4. The
> install says it completed but after I rebooted and did a select @.@.version
> it
> still shows SP3. I only have a default instance so I know that it
> installed
> on the right instance. Could anyone help me out with this?|||I tried it several times but got the same result.
I've attached a copy of my sqlsp.log file. I looked at the sqlsp.log file
and it only listed one non-fatal error...I can't see this being the problem
considering it was nonfatal.
Jasper Smith wrote:
>You can review the setup log for any errors (file called sqlsp.log in the
>windows directory). It is perfectly safe to run SP4 again to try and make it
>stick (assuming you have the system database backups just in case you need
>to regress)
>>I upgraded from SQL 2000 Service Pack 3 to SQL 2000 Service Pack 4. The
>> install says it completed but after I rebooted and did a select @.@.version
>> it
>> still shows SP3. I only have a default instance so I know that it
>> installed
>> on the right instance. Could anyone help me out with this?|||What does the following query return?
SELECT SERVERPROPERTY('ProductLevel')
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Leon Parker" <u23479@.uwe> wrote in message news:625d255c1f101@.uwe...
>I upgraded from SQL 2000 Service Pack 3 to SQL 2000 Service Pack 4. The
> install says it completed but after I rebooted and did a select @.@.version
> it
> still shows SP3. I only have a default instance so I know that it
> installed
> on the right instance. Could anyone help me out with this?|||SP3....
Dan Guzman wrote:
>What does the following query return?
> SELECT SERVERPROPERTY('ProductLevel')
>>I upgraded from SQL 2000 Service Pack 3 to SQL 2000 Service Pack 4. The
>> install says it completed but after I rebooted and did a select @.@.version
>> it
>> still shows SP3. I only have a default instance so I know that it
>> installed
>> on the right instance. Could anyone help me out with this?
--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200606/1sql

Problem with sql server eval on Windows server 2003

Hi!
I tried to install the evaluation version of SqlServer2000 freshed download
from MS web site. the os is Windows Server 2003.
And when I try to start the SQLServer,it is impossible.
Could anyone give a help?
Thanks.
Prosper,
France
I don't think the eval version is supposed to work on Win2003.
Robert.
"Prosper" wrote:

> Hi!
> I tried to install the evaluation version of SqlServer2000 freshed download
> from MS web site. the os is Windows Server 2003.
> And when I try to start the SQLServer,it is impossible.
> Could anyone give a help?
> Thanks.
> Prosper,
> France
>
|||Robert,
Yes it does. Prosper, what error message do you get? You should also
post relevant sections from the error log.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
Robert Davis wrote:[vbcol=seagreen]
> I don't think the eval version is supposed to work on Win2003.
> Robert.
> "Prosper" wrote:
>
|||Here are the error messages:
"A connection could not be established to (LOCAL)
Reasons:SQL SERVER does not exist or access denied.
ConnectionOpen(Connect())..
Please verify SQL SERVER is running and check your server registration
properties and try again." when trying to start the server from Enterprise
Manager.
Events logs:
17310 :
SqlDumpExceptionHandler: Process 1708 generated fatal exception c0000005
EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
17311 :
SQL Server is aborting. Fatal exception c0000005 caught.
"Mark Allison" wrote:

> Robert,
> Yes it does. Prosper, what error message do you get? You should also
> post relevant sections from the error log.
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602m.html
>
> Robert Davis wrote:
>
|||Every thing is ok now; I redownload SQL Server for .NET SERVER 2003, and it
works.
Thanks for your help.
Prosper
"Prosper" wrote:
[vbcol=seagreen]
> Here are the error messages:
> "A connection could not be established to (LOCAL)
> Reasons:SQL SERVER does not exist or access denied.
> ConnectionOpen(Connect())..
> Please verify SQL SERVER is running and check your server registration
> properties and try again." when trying to start the server from Enterprise
> Manager.
> Events logs:
> 17310 :
> SqlDumpExceptionHandler: Process 1708 generated fatal exception c0000005
> EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
> 17311 :
> SQL Server is aborting. Fatal exception c0000005 caught.
>
> "Mark Allison" wrote:

Problem with sql server eval on Windows server 2003

Hi!
I tried to install the evaluation version of SqlServer2000 freshed download
from MS web site. the os is Windows Server 2003.
And when I try to start the SQLServer,it is impossible.
Could anyone give a help?
Thanks.
Prosper,
FranceI don't think the eval version is supposed to work on Win2003.
Robert.
"Prosper" wrote:
> Hi!
> I tried to install the evaluation version of SqlServer2000 freshed download
> from MS web site. the os is Windows Server 2003.
> And when I try to start the SQLServer,it is impossible.
> Could anyone give a help?
> Thanks.
> Prosper,
> France
>|||Robert,
Yes it does. Prosper, what error message do you get? You should also
post relevant sections from the error log.
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
Robert Davis wrote:
> I don't think the eval version is supposed to work on Win2003.
> Robert.
> "Prosper" wrote:
>
>>Hi!
>>I tried to install the evaluation version of SqlServer2000 freshed download
>>from MS web site. the os is Windows Server 2003.
>>And when I try to start the SQLServer,it is impossible.
>>Could anyone give a help?
>>Thanks.
>>Prosper,
>>France|||Here are the error messages:
"A connection could not be established to (LOCAL)
Reasons:SQL SERVER does not exist or access denied.
ConnectionOpen(Connect())..
Please verify SQL SERVER is running and check your server registration
properties and try again." when trying to start the server from Enterprise
Manager.
Events logs:
17310 :
SqlDumpExceptionHandler: Process 1708 generated fatal exception c0000005
EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
17311 :
SQL Server is aborting. Fatal exception c0000005 caught.
"Mark Allison" wrote:
> Robert,
> Yes it does. Prosper, what error message do you get? You should also
> post relevant sections from the error log.
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602m.html
>
> Robert Davis wrote:
> > I don't think the eval version is supposed to work on Win2003.
> >
> > Robert.
> >
> > "Prosper" wrote:
> >
> >
> >>Hi!
> >>I tried to install the evaluation version of SqlServer2000 freshed download
> >>from MS web site. the os is Windows Server 2003.
> >>And when I try to start the SQLServer,it is impossible.
> >>
> >>Could anyone give a help?
> >>Thanks.
> >>
> >>Prosper,
> >>France
> >>
>|||Every thing is ok now; I redownload SQL Server for .NET SERVER 2003, and it
works.
Thanks for your help.
Prosper
"Prosper" wrote:
> Here are the error messages:
> "A connection could not be established to (LOCAL)
> Reasons:SQL SERVER does not exist or access denied.
> ConnectionOpen(Connect())..
> Please verify SQL SERVER is running and check your server registration
> properties and try again." when trying to start the server from Enterprise
> Manager.
> Events logs:
> 17310 :
> SqlDumpExceptionHandler: Process 1708 generated fatal exception c0000005
> EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
> 17311 :
> SQL Server is aborting. Fatal exception c0000005 caught.
>
> "Mark Allison" wrote:
> > Robert,
> >
> > Yes it does. Prosper, what error message do you get? You should also
> > post relevant sections from the error log.
> >
> > --
> > Mark Allison, SQL Server MVP
> > http://www.markallison.co.uk
> >
> > Looking for a SQL Server replication book?
> > http://www.nwsu.com/0974973602m.html
> >
> >
> > Robert Davis wrote:
> > > I don't think the eval version is supposed to work on Win2003.
> > >
> > > Robert.
> > >
> > > "Prosper" wrote:
> > >
> > >
> > >>Hi!
> > >>I tried to install the evaluation version of SqlServer2000 freshed download
> > >>from MS web site. the os is Windows Server 2003.
> > >>And when I try to start the SQLServer,it is impossible.
> > >>
> > >>Could anyone give a help?
> > >>Thanks.
> > >>
> > >>Prosper,
> > >>France
> > >>
> >

Problem with sql server eval on Windows server 2003

Hi!
I tried to install the evaluation version of SqlServer2000 freshed download
from MS web site. the os is Windows Server 2003.
And when I try to start the SQLServer,it is impossible.
Could anyone give a help?
Thanks.
Prosper,
FranceI don't think the eval version is supposed to work on Win2003.
Robert.
"Prosper" wrote:

> Hi!
> I tried to install the evaluation version of SqlServer2000 freshed downloa
d
> from MS web site. the os is Windows Server 2003.
> And when I try to start the SQLServer,it is impossible.
> Could anyone give a help?
> Thanks.
> Prosper,
> France
>|||Robert,
Yes it does. Prosper, what error message do you get? You should also
post relevant sections from the error log.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
Robert Davis wrote:[vbcol=seagreen]
> I don't think the eval version is supposed to work on Win2003.
> Robert.
> "Prosper" wrote:
>|||Here are the error messages:
"A connection could not be established to (LOCAL)
Reasons:SQL SERVER does not exist or access denied.
ConnectionOpen(Connect())..
Please verify SQL SERVER is running and check your server registration
properties and try again." when trying to start the server from Enterprise
Manager.
Events logs:
17310 :
SqlDumpExceptionHandler: Process 1708 generated fatal exception c0000005
EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
17311 :
SQL Server is aborting. Fatal exception c0000005 caught.
"Mark Allison" wrote:

> Robert,
> Yes it does. Prosper, what error message do you get? You should also
> post relevant sections from the error log.
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602m.html
>
> Robert Davis wrote:
>|||Every thing is ok now; I redownload SQL Server for .NET SERVER 2003, and it
works.
Thanks for your help.
Prosper
"Prosper" wrote:
[vbcol=seagreen]
> Here are the error messages:
> "A connection could not be established to (LOCAL)
> Reasons:SQL SERVER does not exist or access denied.
> ConnectionOpen(Connect())..
> Please verify SQL SERVER is running and check your server registration
> properties and try again." when trying to start the server from Enterprise
> Manager.
> Events logs:
> 17310 :
> SqlDumpExceptionHandler: Process 1708 generated fatal exception c0000005
> EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
> 17311 :
> SQL Server is aborting. Fatal exception c0000005 caught.
>
> "Mark Allison" wrote:
>

Problem with SQL Server 2005 Standard Edition installation

Hello,

When I try to install SQL Server 2005 Standard Edition, Windows XP SP2, setup fails.

Please help!!!

This is log file:

..............................

Loaded DLL:
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\DbgHelp.dll
Version:
6.5.3.7
MSI (s) (98:E8) [12:19:07:890]: Leaked MSIHANDLE (6010) of type 790531 for thread 2260
MSI (s) (98:E8) [12:19:07:890]: Leaked MSIHANDLE (6009) of type 790540 for thread 2260
MSI (s) (98:E8) [12:19:07:890]: Leaked MSIHANDLE (6008) of type 790541 for thread 2260
MSI (s) (98:E8) [12:19:07:890]: Leaked MSIHANDLE (5973) of type 790541 for thread 2260
MSI (s) (98:E8) [12:19:07:890]: Leaked MSIHANDLE (5970) of type 790531 for thread 2260
MSI (s) (98:E8) [12:19:07:890]: Note: 1: 2769 2: Write_sqlLocalServers.D20239D7_E87C_40C9_9837_E70B8D4882C2 3: 5

Info 2769.The installer has encountered an unexpected error. The error code is 2769. Custom Action Write_sqlLocalServers.D20239D7_E87C_40C9_9837_E70B8D4882C2 did not close 5 MSIHANDLEs.
MSI (s) (98:2C) [12:19:07:890]: Machine policy value 'DisableRollback' is 0
MSI (s) (98:2C) [12:19:07:890]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
Action ended 12:19:07: Write_sqlLocalServers.D20239D7_E87C_40C9_9837_E70B8D4882C2. Return value 3.
MSI (s) (98:2C) [12:19:07:890]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (98:2C) [12:19:07:890]: No System Restore sequence number for this installation.
MSI (s) (98:2C) [12:19:07:890]: Unlocking Server
Action ended 12:19:07: INSTALL. Return value 3.
Property(S): ProductCode = {28B22773-100E-4AF2-A1C9-2F2EA8A35844}
Property(S): ProductLanguage = 1033

You did not say what version of XP you are running because you cannot install SQL Server 2005 Standard in XP Home, if you are running Media edition or Pro copy the content of the CDs/DVD into a folder in your C drive and run setup from your C drive. One more thing if you intend to install Reporting Services make sure IIS is running or the installer will skip it without telling you why. Hope this helps.

|||From the error message in the log, it appears that you have a setting on your machine which is preventing the systemstate backup to be rolled back. Check with your network administrator about disabling this setting.|||

I have Windows XP professional. IIS is running. Installation from C is also failed.

May be, I uninstalled incorrectly beta-version of Visual studio 2005 and/or SQL Server 2005.

I uninstalled all components and then cleaned register, but it didn't help.

Thanks.

Gato.

|||

Please comment what setting "is preventing the systemstate backup to be rolled back" , where and how can I check that?

I work without network administrator .

Thanks,

Gato.

|||

Gato wrote:

I have Windows XP professional. IIS is running. Installation from C is also failed.

May be, I uninstalled incorrectly beta-version of Visual studio 2005 and/or SQL Server 2005.

I uninstalled all components and then cleaned register, but it didn't help.

Thanks.

Gato.

Lets start with some WinXP system restore to the last available restore point and copy the files to the C and install from C drive. And I just noticed you are not running the standard setup, because I know the bootstrap setup runs for a short while and terminates. The 2005 installer is very easy I know because I had installed 2000 on all operating systems including 64bits except Vista and it was a pain but installing 2005 was a breeze. Keep me posted and pay attention to the installer don't answer questions not relevant to you.

Problem with Sql Server 2000 installation

Hi,
I'm not able to install Microsoft SQL Server 2000 on a Pentium 4 2.40 GHz
with Microsoft Windows 2003 Server.
The problem is:
I insert my SQL Server installation CD in the player. Main window opens up.
I click on "SQL Server 2000 Components", which brings me to the next window.
I click on "Install Database Server" and then window closes... and then
nothing! If I restart the installation, the same thing occurs.
Someone has an idea of what the problem might be?
Thanks!
David
How long do you wait after the click on Install? I seem to recall something
like this but if I waited long enough the next dialog window eventually came
up
----
Need SQL Server Examples check out my website at
http://www.geocities.com/sqlserverexamples
"GeckoNewsgroup" <gecko@.myToto.com> wrote in message
news:BCD3E3D3.1406%gecko@.myToto.com...
> Hi,
> I'm not able to install Microsoft SQL Server 2000 on a Pentium 4 2.40 GHz
> with Microsoft Windows 2003 Server.
> The problem is:
> I insert my SQL Server installation CD in the player. Main window opens
up.
> I click on "SQL Server 2000 Components", which brings me to the next
window.
> I click on "Install Database Server" and then window closes... and then
> nothing! If I restart the installation, the same thing occurs.
> Someone has an idea of what the problem might be?
> Thanks!
> David
>
|||David,
Please dont multipost.I answered this in.setup.
Dinesh
"GeckoNewsgroup" <gecko@.myToto.com> wrote in message
news:BCD3E3D3.1406%gecko@.myToto.com...
> Hi,
> I'm not able to install Microsoft SQL Server 2000 on a Pentium 4 2.40 GHz
> with Microsoft Windows 2003 Server.
> The problem is:
> I insert my SQL Server installation CD in the player. Main window opens
up.
> I click on "SQL Server 2000 Components", which brings me to the next
window.
> I click on "Install Database Server" and then window closes... and then
> nothing! If I restart the installation, the same thing occurs.
> Someone has an idea of what the problem might be?
> Thanks!
> David
>

Problem with Sql Server 2000 installation

Hi,
I'm not able to install Microsoft SQL Server 2000 on a Pentium 4 2.40 GHz
with Microsoft Windows 2003 Server.
The problem is:
I insert my SQL Server installation CD in the player. Main window opens up.
I click on "SQL Server 2000 Components", which brings me to the next window.
I click on "Install Database Server" and then window closes... and then
nothing! If I restart the installation, the same thing occurs.
Someone has an idea of what the problem might be?
Thanks!
DavidHow long do you wait after the click on Install? I seem to recall something
like this but if I waited long enough the next dialog window eventually came
up
--
----
----
--
Need SQL Server Examples check out my website at
http://www.geocities.com/sqlserverexamples
"GeckoNewsgroup" <gecko@.myToto.com> wrote in message
news:BCD3E3D3.1406%gecko@.myToto.com...
> Hi,
> I'm not able to install Microsoft SQL Server 2000 on a Pentium 4 2.40 GHz
> with Microsoft Windows 2003 Server.
> The problem is:
> I insert my SQL Server installation CD in the player. Main window opens
up.
> I click on "SQL Server 2000 Components", which brings me to the next
window.
> I click on "Install Database Server" and then window closes... and then
> nothing! If I restart the installation, the same thing occurs.
> Someone has an idea of what the problem might be?
> Thanks!
> David
>|||David,
Please dont multipost.I answered this in.setup.
--
Dinesh
"GeckoNewsgroup" <gecko@.myToto.com> wrote in message
news:BCD3E3D3.1406%gecko@.myToto.com...
> Hi,
> I'm not able to install Microsoft SQL Server 2000 on a Pentium 4 2.40 GHz
> with Microsoft Windows 2003 Server.
> The problem is:
> I insert my SQL Server installation CD in the player. Main window opens
up.
> I click on "SQL Server 2000 Components", which brings me to the next
window.
> I click on "Install Database Server" and then window closes... and then
> nothing! If I restart the installation, the same thing occurs.
> Someone has an idea of what the problem might be?
> Thanks!
> David
>sql

Problem with Sql Server 2000 installation

Hi,
I'm not able to install Microsoft SQL Server 2000 on a Pentium 4 2.40 GHz
with Microsoft Windows 2003 Server.
The problem is:
I insert my SQL Server installation CD in the player. Main window opens up.
I click on "SQL Server 2000 Components", which brings me to the next window.
I click on "Install Database Server" and then window closes... and then
nothing! If I restart the installation, the same thing occurs.
Someone has an idea of what the problem might be?
Thanks!
DavidHow long do you wait after the click on Install? I seem to recall something
like this but if I waited long enough the next dialog window eventually came
up
--
----
----
--
Need SQL Server Examples check out my website at
http://www.geocities.com/sqlserverexamples
"GeckoNewsgroup" <gecko@.myToto.com> wrote in message
news:BCD3E3D3.1406%gecko@.myToto.com...
> Hi,
> I'm not able to install Microsoft SQL Server 2000 on a Pentium 4 2.40 GHz
> with Microsoft Windows 2003 Server.
> The problem is:
> I insert my SQL Server installation CD in the player. Main window opens
up.
> I click on "SQL Server 2000 Components", which brings me to the next
window.
> I click on "Install Database Server" and then window closes... and then
> nothing! If I restart the installation, the same thing occurs.
> Someone has an idea of what the problem might be?
> Thanks!
> David
>|||David,
Please dont multipost.I answered this in.setup.
Dinesh
"GeckoNewsgroup" <gecko@.myToto.com> wrote in message
news:BCD3E3D3.1406%gecko@.myToto.com...
> Hi,
> I'm not able to install Microsoft SQL Server 2000 on a Pentium 4 2.40 GHz
> with Microsoft Windows 2003 Server.
> The problem is:
> I insert my SQL Server installation CD in the player. Main window opens
up.
> I click on "SQL Server 2000 Components", which brings me to the next
window.
> I click on "Install Database Server" and then window closes... and then
> nothing! If I restart the installation, the same thing occurs.
> Someone has an idea of what the problem might be?
> Thanks!
> David
>

Problem with SQL 2005 install. Can Microsoft.SqlServer.MSMQTask.dll be recovered?

Hello!
I am trying to install SQL Server 2005 (Developer Edition -- the version
that came with my Visual Studio 2005 Professional Edition software).
For the most part, the install went pretty smoothly. However, during the
Integration Services portion, I got the following error:
Failed to install and configure assemblies C:\Program Files\Microsoft SQL
Server\90\DTS\Tasks\Microsoft.SqlServer.MSMQTask.d ll in the COM+ catalog.
Error: -2146233087
Error message: Unknown error 0x80131501
Error description: You must have administrative credentials to perform this
task. Contact your system administrator for assistance.
I Googled for some solutions, and came up with a few relevant hits:
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1311934&SiteID=1
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1143461&SiteID=1
http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=61570
I tried the suggestions therein, but none of them seemed to solve the
problem (and now I no longer have *any* Microsoft.SqlServer.MSMQTask entry
in my COM+ list). I couldn't hit "Retry" during the SQL installation and
have it gracefully resume.
I eventually just hit Ignore, and the rest of the install proceeded just
fine.
I'm wondering if there's any way to recover this file and/or COM+ entry?
I'm guessing that it's necessary for Integration Services?
(BTW: I'm on Windows XP Professional, SP2, and I had SQL Server 2005 CTP
installed at one point, too, but uninstalled before installing the current
version.)
Thanks for any help anyone can provide!
John Peterson
Hi
"John Peterson" wrote:

> Hello!
> I am trying to install SQL Server 2005 (Developer Edition -- the version
> that came with my Visual Studio 2005 Professional Edition software).
> For the most part, the install went pretty smoothly. However, during the
> Integration Services portion, I got the following error:
> Failed to install and configure assemblies C:\Program Files\Microsoft SQL
> Server\90\DTS\Tasks\Microsoft.SqlServer.MSMQTask.d ll in the COM+ catalog.
> Error: -2146233087
> Error message: Unknown error 0x80131501
> Error description: You must have administrative credentials to perform this
> task. Contact your system administrator for assistance.
> I Googled for some solutions, and came up with a few relevant hits:
> http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1311934&SiteID=1
> http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1143461&SiteID=1
> http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=61570
> I tried the suggestions therein, but none of them seemed to solve the
> problem (and now I no longer have *any* Microsoft.SqlServer.MSMQTask entry
> in my COM+ list). I couldn't hit "Retry" during the SQL installation and
> have it gracefully resume.
> I eventually just hit Ignore, and the rest of the install proceeded just
> fine.
> I'm wondering if there's any way to recover this file and/or COM+ entry?
> I'm guessing that it's necessary for Integration Services?
> (BTW: I'm on Windows XP Professional, SP2, and I had SQL Server 2005 CTP
> installed at one point, too, but uninstalled before installing the current
> version.)
> Thanks for any help anyone can provide!
> John Peterson
Have you tried a re-install
http://msdn2.microsoft.com/en-us/library/ms144259.aspx#reinstallmode
John
|||John,
Thanks for the reply! I've got two questions:
If I re-install, will it correctly detect the components to re-install, even
if I've already upgraded to SP2 (and the critical update for SP2)?
What exactly is Integration Services in SQL 2005? Is that sort of like the
DTS replacement? If so, is the absence of this COM+ object going to be a
hindrance?
Kind regards,
John Peterson
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:EB989A7F-2DD9-4A7C-BBB4-ECF7AD1568C4@.microsoft.com...
> Hi
> "John Peterson" wrote:
>
> Have you tried a re-install
> http://msdn2.microsoft.com/en-us/library/ms144259.aspx#reinstallmode
> John
|||Oh -- I also meant to ask whether I could expect the previous error to "go
away" if I were to try and re-install, or if it would likely pop up again?
Now that I've done a little more research on Integration Services (also
known as SSIS), it looks like it is a DTS replacement (and more). As such,
I know that I'll need to be using this component -- so if I can resolve this
installation error, I'll be a happy camper. :-)
Thanks for any additional help you (or any others) can provide!
John Peterson
"John Peterson" <j0hnp@.comcast.net> wrote in message
news:%23unJK%234fHHA.1216@.TK2MSFTNGP03.phx.gbl...
> John,
> Thanks for the reply! I've got two questions:
> If I re-install, will it correctly detect the components to re-install,
> even if I've already upgraded to SP2 (and the critical update for SP2)?
> What exactly is Integration Services in SQL 2005? Is that sort of like
> the DTS replacement? If so, is the absence of this COM+ object going to
> be a hindrance?
> Kind regards,
> John Peterson
>
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:EB989A7F-2DD9-4A7C-BBB4-ECF7AD1568C4@.microsoft.com...
>

Problem with SQL 2005 install. Can Microsoft.SqlServer.MSMQTask.dll be recovered?

Hello!
I am trying to install SQL Server 2005 (Developer Edition -- the version
that came with my Visual Studio 2005 Professional Edition software).
For the most part, the install went pretty smoothly. However, during the
Integration Services portion, I got the following error:
Failed to install and configure assemblies C:\Program Files\Microsoft SQL
Server\90\DTS\Tasks\Microsoft.SqlServer.MSMQTask.dll in the COM+ catalog.
Error: -2146233087
Error message: Unknown error 0x80131501
Error description: You must have administrative credentials to perform this
task. Contact your system administrator for assistance.
I Googled for some solutions, and came up with a few relevant hits:
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1311934&SiteID=1
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1143461&SiteID=1
http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=61570
I tried the suggestions therein, but none of them seemed to solve the
problem (and now I no longer have *any* Microsoft.SqlServer.MSMQTask entry
in my COM+ list). I couldn't hit "Retry" during the SQL installation and
have it gracefully resume.
I eventually just hit Ignore, and the rest of the install proceeded just
fine.
I'm wondering if there's any way to recover this file and/or COM+ entry?
I'm guessing that it's necessary for Integration Services?
(BTW: I'm on Windows XP Professional, SP2, and I had SQL Server 2005 CTP
installed at one point, too, but uninstalled before installing the current
version.)
Thanks for any help anyone can provide!
John PetersonHi
"John Peterson" wrote:
> Hello!
> I am trying to install SQL Server 2005 (Developer Edition -- the version
> that came with my Visual Studio 2005 Professional Edition software).
> For the most part, the install went pretty smoothly. However, during the
> Integration Services portion, I got the following error:
> Failed to install and configure assemblies C:\Program Files\Microsoft SQL
> Server\90\DTS\Tasks\Microsoft.SqlServer.MSMQTask.dll in the COM+ catalog.
> Error: -2146233087
> Error message: Unknown error 0x80131501
> Error description: You must have administrative credentials to perform this
> task. Contact your system administrator for assistance.
> I Googled for some solutions, and came up with a few relevant hits:
> http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1311934&SiteID=1
> http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1143461&SiteID=1
> http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=61570
> I tried the suggestions therein, but none of them seemed to solve the
> problem (and now I no longer have *any* Microsoft.SqlServer.MSMQTask entry
> in my COM+ list). I couldn't hit "Retry" during the SQL installation and
> have it gracefully resume.
> I eventually just hit Ignore, and the rest of the install proceeded just
> fine.
> I'm wondering if there's any way to recover this file and/or COM+ entry?
> I'm guessing that it's necessary for Integration Services?
> (BTW: I'm on Windows XP Professional, SP2, and I had SQL Server 2005 CTP
> installed at one point, too, but uninstalled before installing the current
> version.)
> Thanks for any help anyone can provide!
> John Peterson
Have you tried a re-install
http://msdn2.microsoft.com/en-us/library/ms144259.aspx#reinstallmode
John|||John,
Thanks for the reply! I've got two questions:
If I re-install, will it correctly detect the components to re-install, even
if I've already upgraded to SP2 (and the critical update for SP2)?
What exactly is Integration Services in SQL 2005? Is that sort of like the
DTS replacement? If so, is the absence of this COM+ object going to be a
hindrance?
Kind regards,
John Peterson
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:EB989A7F-2DD9-4A7C-BBB4-ECF7AD1568C4@.microsoft.com...
> Hi
> "John Peterson" wrote:
>> Hello!
>> I am trying to install SQL Server 2005 (Developer Edition -- the version
>> that came with my Visual Studio 2005 Professional Edition software).
>> For the most part, the install went pretty smoothly. However, during the
>> Integration Services portion, I got the following error:
>> Failed to install and configure assemblies C:\Program Files\Microsoft SQL
>> Server\90\DTS\Tasks\Microsoft.SqlServer.MSMQTask.dll in the COM+ catalog.
>> Error: -2146233087
>> Error message: Unknown error 0x80131501
>> Error description: You must have administrative credentials to perform
>> this
>> task. Contact your system administrator for assistance.
>> I Googled for some solutions, and came up with a few relevant hits:
>> http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1311934&SiteID=1
>> http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1143461&SiteID=1
>> http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=61570
>> I tried the suggestions therein, but none of them seemed to solve the
>> problem (and now I no longer have *any* Microsoft.SqlServer.MSMQTask
>> entry
>> in my COM+ list). I couldn't hit "Retry" during the SQL installation and
>> have it gracefully resume.
>> I eventually just hit Ignore, and the rest of the install proceeded just
>> fine.
>> I'm wondering if there's any way to recover this file and/or COM+ entry?
>> I'm guessing that it's necessary for Integration Services?
>> (BTW: I'm on Windows XP Professional, SP2, and I had SQL Server 2005 CTP
>> installed at one point, too, but uninstalled before installing the
>> current
>> version.)
>> Thanks for any help anyone can provide!
>> John Peterson
> Have you tried a re-install
> http://msdn2.microsoft.com/en-us/library/ms144259.aspx#reinstallmode
> John|||Oh -- I also meant to ask whether I could expect the previous error to "go
away" if I were to try and re-install, or if it would likely pop up again?
Now that I've done a little more research on Integration Services (also
known as SSIS), it looks like it is a DTS replacement (and more). As such,
I know that I'll need to be using this component -- so if I can resolve this
installation error, I'll be a happy camper. :-)
Thanks for any additional help you (or any others) can provide!
John Peterson
"John Peterson" <j0hnp@.comcast.net> wrote in message
news:%23unJK%234fHHA.1216@.TK2MSFTNGP03.phx.gbl...
> John,
> Thanks for the reply! I've got two questions:
> If I re-install, will it correctly detect the components to re-install,
> even if I've already upgraded to SP2 (and the critical update for SP2)?
> What exactly is Integration Services in SQL 2005? Is that sort of like
> the DTS replacement? If so, is the absence of this COM+ object going to
> be a hindrance?
> Kind regards,
> John Peterson
>
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:EB989A7F-2DD9-4A7C-BBB4-ECF7AD1568C4@.microsoft.com...
>> Hi
>> "John Peterson" wrote:
>> Hello!
>> I am trying to install SQL Server 2005 (Developer Edition -- the version
>> that came with my Visual Studio 2005 Professional Edition software).
>> For the most part, the install went pretty smoothly. However, during
>> the
>> Integration Services portion, I got the following error:
>> Failed to install and configure assemblies C:\Program Files\Microsoft
>> SQL
>> Server\90\DTS\Tasks\Microsoft.SqlServer.MSMQTask.dll in the COM+
>> catalog.
>> Error: -2146233087
>> Error message: Unknown error 0x80131501
>> Error description: You must have administrative credentials to perform
>> this
>> task. Contact your system administrator for assistance.
>> I Googled for some solutions, and came up with a few relevant hits:
>> http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1311934&SiteID=1
>> http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1143461&SiteID=1
>> http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=61570
>> I tried the suggestions therein, but none of them seemed to solve the
>> problem (and now I no longer have *any* Microsoft.SqlServer.MSMQTask
>> entry
>> in my COM+ list). I couldn't hit "Retry" during the SQL installation
>> and
>> have it gracefully resume.
>> I eventually just hit Ignore, and the rest of the install proceeded just
>> fine.
>> I'm wondering if there's any way to recover this file and/or COM+ entry?
>> I'm guessing that it's necessary for Integration Services?
>> (BTW: I'm on Windows XP Professional, SP2, and I had SQL Server 2005
>> CTP
>> installed at one point, too, but uninstalled before installing the
>> current
>> version.)
>> Thanks for any help anyone can provide!
>> John Peterson
>> Have you tried a re-install
>> http://msdn2.microsoft.com/en-us/library/ms144259.aspx#reinstallmode
>> John
>sql

Problem with SP4 installation and REPLSYS.SQL

I have a SQLServer 2000 SP3 running on Windows Server 2000 SP4. My
installation has 5 named instances. I was able to install SQLServer SP4
onto 4 of the named instances with out any problem. When I installed the
SP4 update I was logged on as the local administrator and used Windows
authentication.
When I attempted the install on the last instance, it failed running the
REPLSYS.SQL script. After some digging I found the REPLSYS.OUT file and it
told me that the error was with procedure sp_addextendedproc in the master
db. The script tried to execute the following command:
sp_addextendedproc 'xp_mergexpusage', 'xprepl.dll'
The error says that there is already an object named 'xp_mergexpusage' in
the database.
I have looked at the list of extended stored procedures listed in the Master
DB and I cannot see the xp_mergexpusage stored procedure anywhere. Is it
hidden somehow? I can see the stored procedure in the other instances that
were sucessfully updated but not in the instance that fails.
Has anyone else run into this problem when installing SP4?
Is there a way to attempt a delete of the xp_mergexpusage extended stored
procedure incase it is hidden somehow?
Any help would be greatly appreciated.
Greg Pagan
I found the answer to this issue myself.
Turns out the problem had nothing to do with SP4 at all. It just pointed
out the underlying issue.
I had corruption in the master data base that somehow messed with the
DBI_NextID. The value of that indicator was out of sync with the max(ID)
indicator. The DB_NextID as less than the Max(ID) which was telling the
system that the object already existed. The fix which came from
sqlforums.windowsitpro.com is to generate new DB_NextIDs by creating and
droping simple tables in master until the counter for DB_NextID grows larger
than max(ID). It took me over 700 table creates to get to that point.
After that the SP4 Update ran successfully.
Thanks anyway.
"Greg Pagan" <gpagan@.thehartford.com> wrote in message
news:O%23CHMX3VGHA.5692@.TK2MSFTNGP09.phx.gbl...
>I have a SQLServer 2000 SP3 running on Windows Server 2000 SP4. My
>installation has 5 named instances. I was able to install SQLServer SP4
>onto 4 of the named instances with out any problem. When I installed the
>SP4 update I was logged on as the local administrator and used Windows
>authentication.
> When I attempted the install on the last instance, it failed running the
> REPLSYS.SQL script. After some digging I found the REPLSYS.OUT file and
> it told me that the error was with procedure sp_addextendedproc in the
> master db. The script tried to execute the following command:
> sp_addextendedproc 'xp_mergexpusage', 'xprepl.dll'
> The error says that there is already an object named 'xp_mergexpusage' in
> the database.
> I have looked at the list of extended stored procedures listed in the
> Master DB and I cannot see the xp_mergexpusage stored procedure anywhere.
> Is it hidden somehow? I can see the stored procedure in the other
> instances that were sucessfully updated but not in the instance that
> fails.
> Has anyone else run into this problem when installing SP4?
> Is there a way to attempt a delete of the xp_mergexpusage extended stored
> procedure incase it is hidden somehow?
> Any help would be greatly appreciated.
> Greg Pagan
>
>

Problem with SP4 installation and REPLSYS.SQL

I have a SQLServer 2000 SP3 running on Windows Server 2000 SP4. My
installation has 5 named instances. I was able to install SQLServer SP4
onto 4 of the named instances with out any problem. When I installed the
SP4 update I was logged on as the local administrator and used Windows
authentication.
When I attempted the install on the last instance, it failed running the
REPLSYS.SQL script. After some digging I found the REPLSYS.OUT file and it
told me that the error was with procedure sp_addextendedproc in the master
db. The script tried to execute the following command:
sp_addextendedproc 'xp_mergexpusage', 'xprepl.dll'
The error says that there is already an object named 'xp_mergexpusage' in
the database.
I have looked at the list of extended stored procedures listed in the Master
DB and I cannot see the xp_mergexpusage stored procedure anywhere. Is it
hidden somehow? I can see the stored procedure in the other instances that
were sucessfully updated but not in the instance that fails.
Has anyone else run into this problem when installing SP4?
Is there a way to attempt a delete of the xp_mergexpusage extended stored
procedure incase it is hidden somehow?
Any help would be greatly appreciated.
Greg PaganI found the answer to this issue myself.
Turns out the problem had nothing to do with SP4 at all. It just pointed
out the underlying issue.
I had corruption in the master data base that somehow messed with the
DBI_NextID. The value of that indicator was out of sync with the max(ID)
indicator. The DB_NextID as less than the Max(ID) which was telling the
system that the object already existed. The fix which came from
sqlforums.windowsitpro.com is to generate new DB_NextIDs by creating and
droping simple tables in master until the counter for DB_NextID grows larger
than max(ID). It took me over 700 table creates to get to that point.
After that the SP4 Update ran successfully.
Thanks anyway.
"Greg Pagan" <gpagan@.thehartford.com> wrote in message
news:O%23CHMX3VGHA.5692@.TK2MSFTNGP09.phx.gbl...
>I have a SQLServer 2000 SP3 running on Windows Server 2000 SP4. My
>installation has 5 named instances. I was able to install SQLServer SP4
>onto 4 of the named instances with out any problem. When I installed the
>SP4 update I was logged on as the local administrator and used Windows
>authentication.
> When I attempted the install on the last instance, it failed running the
> REPLSYS.SQL script. After some digging I found the REPLSYS.OUT file and
> it told me that the error was with procedure sp_addextendedproc in the
> master db. The script tried to execute the following command:
> sp_addextendedproc 'xp_mergexpusage', 'xprepl.dll'
> The error says that there is already an object named 'xp_mergexpusage' in
> the database.
> I have looked at the list of extended stored procedures listed in the
> Master DB and I cannot see the xp_mergexpusage stored procedure anywhere.
> Is it hidden somehow? I can see the stored procedure in the other
> instances that were sucessfully updated but not in the instance that
> fails.
> Has anyone else run into this problem when installing SP4?
> Is there a way to attempt a delete of the xp_mergexpusage extended stored
> procedure incase it is hidden somehow?
> Any help would be greatly appreciated.
> Greg Pagan
>
>

Problem with SP4 installation and REPLSYS.SQL

I have a SQLServer 2000 SP3 running on Windows Server 2000 SP4. My
installation has 5 named instances. I was able to install SQLServer SP4
onto 4 of the named instances with out any problem. When I installed the
SP4 update I was logged on as the local administrator and used Windows
authentication.
When I attempted the install on the last instance, it failed running the
REPLSYS.SQL script. After some digging I found the REPLSYS.OUT file and it
told me that the error was with procedure sp_addextendedproc in the master
db. The script tried to execute the following command:
sp_addextendedproc 'xp_mergexpusage', 'xprepl.dll'
The error says that there is already an object named 'xp_mergexpusage' in
the database.
I have looked at the list of extended stored procedures listed in the Master
DB and I cannot see the xp_mergexpusage stored procedure anywhere. Is it
hidden somehow? I can see the stored procedure in the other instances that
were sucessfully updated but not in the instance that fails.
Has anyone else run into this problem when installing SP4?
Is there a way to attempt a delete of the xp_mergexpusage extended stored
procedure incase it is hidden somehow?
Any help would be greatly appreciated.
Greg PaganI found the answer to this issue myself.
Turns out the problem had nothing to do with SP4 at all. It just pointed
out the underlying issue.
I had corruption in the master data base that somehow messed with the
DBI_NextID. The value of that indicator was out of sync with the max(ID)
indicator. The DB_NextID as less than the Max(ID) which was telling the
system that the object already existed. The fix which came from
sqlforums.windowsitpro.com is to generate new DB_NextIDs by creating and
droping simple tables in master until the counter for DB_NextID grows larger
than max(ID). It took me over 700 table creates to get to that point.
After that the SP4 Update ran successfully.
Thanks anyway.
"Greg Pagan" <gpagan@.thehartford.com> wrote in message
news:O%23CHMX3VGHA.5692@.TK2MSFTNGP09.phx.gbl...
>I have a SQLServer 2000 SP3 running on Windows Server 2000 SP4. My
>installation has 5 named instances. I was able to install SQLServer SP4
>onto 4 of the named instances with out any problem. When I installed the
>SP4 update I was logged on as the local administrator and used Windows
>authentication.
> When I attempted the install on the last instance, it failed running the
> REPLSYS.SQL script. After some digging I found the REPLSYS.OUT file and
> it told me that the error was with procedure sp_addextendedproc in the
> master db. The script tried to execute the following command:
> sp_addextendedproc 'xp_mergexpusage', 'xprepl.dll'
> The error says that there is already an object named 'xp_mergexpusage' in
> the database.
> I have looked at the list of extended stored procedures listed in the
> Master DB and I cannot see the xp_mergexpusage stored procedure anywhere.
> Is it hidden somehow? I can see the stored procedure in the other
> instances that were sucessfully updated but not in the instance that
> fails.
> Has anyone else run into this problem when installing SP4?
> Is there a way to attempt a delete of the xp_mergexpusage extended stored
> procedure incase it is hidden somehow?
> Any help would be greatly appreciated.
> Greg Pagan
>
>

Problem with Service Principle Name after new install

Hi all,
I installed a SQL Server 2000 on a Win2003 machine, running the SQL Server
service under a domain user account.
When the SQL Server starts, I find a warning in the event log:
Source: MSSQLServer EventID: 19011
Description: SuperSocket info: (SpnRegister) : Error 8344.
After reading several KB articles I understand that the service account
tries to register the Service Principle Name on startup and fails because it
does not have the rights the register the SPN in Active Directory.
I put the account in the local admin group on the server and created a SPN
with setspn.exe from Win2000 resource kit, which points to at the domain
account. Does not fix the warning message.
I do not want to put the account into domain admin group, which would fix
the problem I think, because domain admins have all permissions to register
the SPN.
Does someone have a hint for me?
Thanks in advance
Regards
Christian
If your server should always work using same tcp port, you may ignore this
message.
If server works under LocalSystem or other account which has such
permissions (by default - only Domain Admins), he registers SPN at startup
and unregisters at shutdown. So in your case if you change tcp/ip settings
for server, you will have to reregister SPN manually. Or you may give such
rights to service account - see this article for permissions info:
http://technet2.microsoft.com/Window...e47441033.mspx
WBR, Evergray
Words mean nothing...
"Christian Guntsche" <christian.guntsche@.docuware.com> wrote in message
news:OxLkQH1RGHA.1688@.TK2MSFTNGP11.phx.gbl...
> Hi all,
> I installed a SQL Server 2000 on a Win2003 machine, running the SQL Server
> service under a domain user account.
> When the SQL Server starts, I find a warning in the event log:
> Source: MSSQLServer EventID: 19011
> Description: SuperSocket info: (SpnRegister) : Error 8344.
> After reading several KB articles I understand that the service account
> tries to register the Service Principle Name on startup and fails because
> it does not have the rights the register the SPN in Active Directory.
> I put the account in the local admin group on the server and created a SPN
> with setspn.exe from Win2000 resource kit, which points to at the domain
> account. Does not fix the warning message.
> I do not want to put the account into domain admin group, which would fix
> the problem I think, because domain admins have all permissions to
> register the SPN.
> Does someone have a hint for me?
> Thanks in advance
> Regards
> Christian
>
|||Thanks for reply,
at least you pointed us in the right direction.
I read the article, but again MS describes not which rights an account needs
in order to register the SPN at startup. All information you get is, that it
works with domain admin rights and with local system.
Nonetheless, the information, that a special function is executed in Active
Directory let us search through the Advanced Active Directory permission
settings and we found that giving the permission to "write public
information" to the SQL Service Account solves the problem.
This prevents us from assigning domain admin rights.
Strange, that Microsoft does not point out which specific permissions have
to be set for a normal user account, but in the other tells you to not use a
admin account.
Anyway this is solved for us.
Regards
Christian
"Oleksandr Chuchko" <forlists@.mail.ru> schrieb im Newsbeitrag
news:%23JIEvO5RGHA.5036@.TK2MSFTNGP12.phx.gbl...
> If your server should always work using same tcp port, you may ignore this
> message.
> If server works under LocalSystem or other account which has such
> permissions (by default - only Domain Admins), he registers SPN at startup
> and unregisters at shutdown. So in your case if you change tcp/ip settings
> for server, you will have to reregister SPN manually. Or you may give such
> rights to service account - see this article for permissions info:
> http://technet2.microsoft.com/Window...e47441033.mspx
> --
> WBR, Evergray
> --
> Words mean nothing...
>
> "Christian Guntsche" <christian.guntsche@.docuware.com> wrote in message
> news:OxLkQH1RGHA.1688@.TK2MSFTNGP11.phx.gbl...
>

Problem with Service Principle Name after new install

Hi all,
I installed a SQL Server 2000 on a Win2003 machine, running the SQL Server
service under a domain user account.
When the SQL Server starts, I find a warning in the event log:
Source: MSSQLServer EventID: 19011
Description: SuperSocket info: (SpnRegister) : Error 8344.
After reading several KB articles I understand that the service account
tries to register the Service Principle Name on startup and fails because it
does not have the rights the register the SPN in Active Directory.
I put the account in the local admin group on the server and created a SPN
with setspn.exe from Win2000 resource kit, which points to at the domain
account. Does not fix the warning message.
I do not want to put the account into domain admin group, which would fix
the problem I think, because domain admins have all permissions to register
the SPN.
Does someone have a hint for me?
Thanks in advance
Regards
ChristianIf your server should always work using same tcp port, you may ignore this
message.
If server works under LocalSystem or other account which has such
permissions (by default - only Domain Admins), he registers SPN at startup
and unregisters at shutdown. So in your case if you change tcp/ip settings
for server, you will have to reregister SPN manually. Or you may give such
rights to service account - see this article for permissions info:
http://technet2.microsoft.com/Windo...de47441033.mspx
WBR, Evergray
--
Words mean nothing...
"Christian Guntsche" <christian.guntsche@.docuware.com> wrote in message
news:OxLkQH1RGHA.1688@.TK2MSFTNGP11.phx.gbl...
> Hi all,
> I installed a SQL Server 2000 on a Win2003 machine, running the SQL Server
> service under a domain user account.
> When the SQL Server starts, I find a warning in the event log:
> Source: MSSQLServer EventID: 19011
> Description: SuperSocket info: (SpnRegister) : Error 8344.
> After reading several KB articles I understand that the service account
> tries to register the Service Principle Name on startup and fails because
> it does not have the rights the register the SPN in Active Directory.
> I put the account in the local admin group on the server and created a SPN
> with setspn.exe from Win2000 resource kit, which points to at the domain
> account. Does not fix the warning message.
> I do not want to put the account into domain admin group, which would fix
> the problem I think, because domain admins have all permissions to
> register the SPN.
> Does someone have a hint for me?
> Thanks in advance
> Regards
> Christian
>|||Thanks for reply,
at least you pointed us in the right direction.
I read the article, but again MS describes not which rights an account needs
in order to register the SPN at startup. All information you get is, that it
works with domain admin rights and with local system.
Nonetheless, the information, that a special function is executed in Active
Directory let us search through the Advanced Active Directory permission
settings and we found that giving the permission to "write public
information" to the SQL Service Account solves the problem.
This prevents us from assigning domain admin rights.
Strange, that Microsoft does not point out which specific permissions have
to be set for a normal user account, but in the other tells you to not use a
admin account.
Anyway this is solved for us.
Regards
Christian
"Oleksandr Chuchko" <forlists@.mail.ru> schrieb im Newsbeitrag
news:%23JIEvO5RGHA.5036@.TK2MSFTNGP12.phx.gbl...
> If your server should always work using same tcp port, you may ignore this
> message.
> If server works under LocalSystem or other account which has such
> permissions (by default - only Domain Admins), he registers SPN at startup
> and unregisters at shutdown. So in your case if you change tcp/ip settings
> for server, you will have to reregister SPN manually. Or you may give such
> rights to service account - see this article for permissions info:
> http://technet2.microsoft.com/Windo...de47441033.mspx
> --
> WBR, Evergray
> --
> Words mean nothing...
>
> "Christian Guntsche" <christian.guntsche@.docuware.com> wrote in message
> news:OxLkQH1RGHA.1688@.TK2MSFTNGP11.phx.gbl...
>sql

Problem with Service Principle Name after new install

Hi all,
I installed a SQL Server 2000 on a Win2003 machine, running the SQL Server
service under a domain user account.
When the SQL Server starts, I find a warning in the event log:
Source: MSSQLServer EventID: 19011
Description: SuperSocket info: (SpnRegister) : Error 8344.
After reading several KB articles I understand that the service account
tries to register the Service Principle Name on startup and fails because it
does not have the rights the register the SPN in Active Directory.
I put the account in the local admin group on the server and created a SPN
with setspn.exe from Win2000 resource kit, which points to at the domain
account. Does not fix the warning message.
I do not want to put the account into domain admin group, which would fix
the problem I think, because domain admins have all permissions to register
the SPN.
Does someone have a hint for me?
Thanks in advance
Regards
ChristianIf your server should always work using same tcp port, you may ignore this
message.
If server works under LocalSystem or other account which has such
permissions (by default - only Domain Admins), he registers SPN at startup
and unregisters at shutdown. So in your case if you change tcp/ip settings
for server, you will have to reregister SPN manually. Or you may give such
rights to service account - see this article for permissions info:
http://technet2.microsoft.com/WindowsServer/en/Library/8127f5ed-4e05-4822-bfa9-402ceede47441033.mspx
--
WBR, Evergray
--
Words mean nothing...
"Christian Guntsche" <christian.guntsche@.docuware.com> wrote in message
news:OxLkQH1RGHA.1688@.TK2MSFTNGP11.phx.gbl...
> Hi all,
> I installed a SQL Server 2000 on a Win2003 machine, running the SQL Server
> service under a domain user account.
> When the SQL Server starts, I find a warning in the event log:
> Source: MSSQLServer EventID: 19011
> Description: SuperSocket info: (SpnRegister) : Error 8344.
> After reading several KB articles I understand that the service account
> tries to register the Service Principle Name on startup and fails because
> it does not have the rights the register the SPN in Active Directory.
> I put the account in the local admin group on the server and created a SPN
> with setspn.exe from Win2000 resource kit, which points to at the domain
> account. Does not fix the warning message.
> I do not want to put the account into domain admin group, which would fix
> the problem I think, because domain admins have all permissions to
> register the SPN.
> Does someone have a hint for me?
> Thanks in advance
> Regards
> Christian
>|||Thanks for reply,
at least you pointed us in the right direction. :)
I read the article, but again MS describes not which rights an account needs
in order to register the SPN at startup. All information you get is, that it
works with domain admin rights and with local system.
Nonetheless, the information, that a special function is executed in Active
Directory let us search through the Advanced Active Directory permission
settings and we found that giving the permission to "write public
information" to the SQL Service Account solves the problem.
This prevents us from assigning domain admin rights.
Strange, that Microsoft does not point out which specific permissions have
to be set for a normal user account, but in the other tells you to not use a
admin account.
Anyway this is solved for us.
Regards
Christian
"Oleksandr Chuchko" <forlists@.mail.ru> schrieb im Newsbeitrag
news:%23JIEvO5RGHA.5036@.TK2MSFTNGP12.phx.gbl...
> If your server should always work using same tcp port, you may ignore this
> message.
> If server works under LocalSystem or other account which has such
> permissions (by default - only Domain Admins), he registers SPN at startup
> and unregisters at shutdown. So in your case if you change tcp/ip settings
> for server, you will have to reregister SPN manually. Or you may give such
> rights to service account - see this article for permissions info:
> http://technet2.microsoft.com/WindowsServer/en/Library/8127f5ed-4e05-4822-bfa9-402ceede47441033.mspx
> --
> WBR, Evergray
> --
> Words mean nothing...
>
> "Christian Guntsche" <christian.guntsche@.docuware.com> wrote in message
> news:OxLkQH1RGHA.1688@.TK2MSFTNGP11.phx.gbl...
>> Hi all,
>> I installed a SQL Server 2000 on a Win2003 machine, running the SQL
>> Server service under a domain user account.
>> When the SQL Server starts, I find a warning in the event log:
>> Source: MSSQLServer EventID: 19011
>> Description: SuperSocket info: (SpnRegister) : Error 8344.
>> After reading several KB articles I understand that the service account
>> tries to register the Service Principle Name on startup and fails because
>> it does not have the rights the register the SPN in Active Directory.
>> I put the account in the local admin group on the server and created a
>> SPN with setspn.exe from Win2000 resource kit, which points to at the
>> domain account. Does not fix the warning message.
>> I do not want to put the account into domain admin group, which would fix
>> the problem I think, because domain admins have all permissions to
>> register the SPN.
>> Does someone have a hint for me?
>> Thanks in advance
>> Regards
>> Christian
>

problem with Server Management Studio Express and diagrames

so I have had a database in Sql Server 2000, in my DB i have made database diagrams.

now I have installed on other PC(where does't install sql 2000) Sql Server Management Studio Express where I have opened my db , bat db diagrams does't work.

what can I do? how can I solve this problem?

enyone can explain me?

thanks.

Management Studio can't open SQL 2000 diagrams, if you click on the diagrams branch of the tree it should ask if you want to install diagram support, once this is done you can create new diagrams.|||ok, bat when I opend diagrams branch of the tree, it doesn't ask if I want or not to install diagram|||

hi,

usually you have to first import the database to the new SQL Server 2005 instance (as you already did)..

then modify the compatibility level to 90 via the SSMSE, database properties (options tab), and finally set the database owner to a valid principal, again SSMSE, database properties (files tab, "owner" peroperty )...

then you should be able to access database diagrams..

regards