Can not install MSDE 2000A

I am attempting to install the MS SQL Server Desktop Engine. I have the
MSDE2000A.exe file and it unpacks successfully. I then run the setup and get
an install fail with the following:
Install message:
Setup failed to configure the server. See the server error logs and setup
error logs.
The only server error log I can find sez the following:
2005-02-11 14:09:52.11 server Microsoft SQL Server 2000 - 8.00.760
(Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 2)
server Copyright (C) 1988-2002 Microsoft Corporation.
server All rights reserved.
server Server Process ID is 2716.
server Logging SQL Server messages in file 'C:\Program Files\Microsoft
SQL Server\MSSQL\LOG\ERRORLOG'.
server SQL Server is starting at priority class 'normal'(1 CPU detected).
server SQL Server configured for thread mode processing.
server Using dynamic lock allocation. [500] Lock Blocks, [1000] Lock
Owner Blocks.
spid3 Warning ******************
spid3 SQL Server started in single user mode. Updates allowed to system
catalogs.
spid3 Starting up database 'master'.
server Using 'SSNETLIB.DLL' version '8.0.766'.
spid5 Starting up database 'model'.
spid3 Server name is 'BART9550'.
spid3 Skipping startup of clean database id 5
spid3 Skipping startup of clean database id 6
spid3 Starting up database 'msdb'.
spid5 Clearing tempdb database.
server SQL server listening on Shared Memory.
server SQL Server is ready for client connections
spid5 Starting up database 'tempdb'.
spid3 Recovery complete.
spid3 SQL global counter collection task is created.
spid3 Warning: override, autoexec procedures skipped.
spid3 SQL Server is terminating due to 'stop' request from Service
Control Manager.
The application event log sez:
Event Type:Warning
Event Source:MSSQLServer
Event Category:(8)
Event ID:19011
Date:2/11/2005
Time:3:22:01 PM
User:N/A
Computer:BART9550
Description:
The description for Event ID ( 19011 ) in Source ( MSSQLServer ) cannot be
found. The local computer may not have the necessary registry information or
message DLL files to display messages from a remote computer. You may be able
to use the /AUXSOURCE= flag to retrieve this description; see Help and
Support for details. The following information is part of the event:
(SpnRegister) : Error 1355.
Also another entry sez:
Event Type:Information
Event Source:MSSQLSERVER
Event Category:(2)
Event ID:17055
Date:2/11/2005
Time:3:22:00 PM
User:N/A
Computer:BART9550
Description:
The description for Event ID ( 17055 ) in Source ( MSSQLSERVER ) cannot be
found. The local computer may not have the necessary registry information or
message DLL files to display messages from a remote computer. You may be able
to use the /AUXSOURCE= flag to retrieve this description; see Help and
Support for details. The following information is part of the event: 17834,
Using 'SSNETLIB.DLL' version '8.0.766'.
How do I get this install to work as I have an application that requires SQL
desktop.
Thanks...
Read the readme files that come with MSDE. You can't just run the setup.exe
with no parameters an expect to install SQL Server exactly like you would
like it configured. MSDE a developer's tool so act like a developer and do
some investigative work before trying to install it.
Jim
"BartC" <BartC@.discussions.microsoft.com> wrote in message
news:555AF044-A697-401C-8D08-0121BCFAFDD4@.microsoft.com...
>I am attempting to install the MS SQL Server Desktop Engine. I have the
> MSDE2000A.exe file and it unpacks successfully. I then run the setup and
> get
> an install fail with the following:
> Install message:
> Setup failed to configure the server. See the server error logs and setup
> error logs.
> The only server error log I can find sez the following:
> 2005-02-11 14:09:52.11 server Microsoft SQL Server 2000 - 8.00.760
> (Intel X86)
> Dec 17 2002 14:22:05
> Copyright (c) 1988-2003 Microsoft Corporation
> Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 2)
> server Copyright (C) 1988-2002 Microsoft Corporation.
> server All rights reserved.
> server Server Process ID is 2716.
> server Logging SQL Server messages in file 'C:\Program Files\Microsoft
> SQL Server\MSSQL\LOG\ERRORLOG'.
> server SQL Server is starting at priority class 'normal'(1 CPU
> detected).
> server SQL Server configured for thread mode processing.
> server Using dynamic lock allocation. [500] Lock Blocks, [1000] Lock
> Owner Blocks.
> spid3 Warning ******************
> spid3 SQL Server started in single user mode. Updates allowed to
> system
> catalogs.
> spid3 Starting up database 'master'.
> server Using 'SSNETLIB.DLL' version '8.0.766'.
> spid5 Starting up database 'model'.
> spid3 Server name is 'BART9550'.
> spid3 Skipping startup of clean database id 5
> spid3 Skipping startup of clean database id 6
> spid3 Starting up database 'msdb'.
> spid5 Clearing tempdb database.
> server SQL server listening on Shared Memory.
> server SQL Server is ready for client connections
> spid5 Starting up database 'tempdb'.
> spid3 Recovery complete.
> spid3 SQL global counter collection task is created.
> spid3 Warning: override, autoexec procedures skipped.
> spid3 SQL Server is terminating due to 'stop' request from Service
> Control Manager.
> The application event log sez:
> Event Type: Warning
> Event Source: MSSQLServer
> Event Category: (8)
> Event ID: 19011
> Date: 2/11/2005
> Time: 3:22:01 PM
> User: N/A
> Computer: BART9550
> Description:
> The description for Event ID ( 19011 ) in Source ( MSSQLServer ) cannot be
> found. The local computer may not have the necessary registry information
> or
> message DLL files to display messages from a remote computer. You may be
> able
> to use the /AUXSOURCE= flag to retrieve this description; see Help and
> Support for details. The following information is part of the event:
> (SpnRegister) : Error 1355.
>
> Also another entry sez:
> Event Type: Information
> Event Source: MSSQLSERVER
> Event Category: (2)
> Event ID: 17055
> Date: 2/11/2005
> Time: 3:22:00 PM
> User: N/A
> Computer: BART9550
> Description:
> The description for Event ID ( 17055 ) in Source ( MSSQLSERVER ) cannot be
> found. The local computer may not have the necessary registry information
> or
> message DLL files to display messages from a remote computer. You may be
> able
> to use the /AUXSOURCE= flag to retrieve this description; see Help and
> Support for details. The following information is part of the event:
> 17834,
> Using 'SSNETLIB.DLL' version '8.0.766'.
> How do I get this install to work as I have an application that requires
> SQL
> desktop.
> Thanks...
|||Hi Jim,
Thanks for the put down. Most appreciated.
I am not a developer. I am simply a computer user trying to use a program
that requires MSDE. And, I did not think that MSDE was a developer tool,
but simply a db engine that apps could plug into. But clearly you know more
than I.
And, with a little research by this end user I switched on no back out so I
could read the install log, and I supplied the setup.ini file with the
following:
BLANKSAPWD=1
SQLSecurityMode=SQL
By stopping the back out I now have SQL server running. but can not install
ODB connectivity drivers. ODBC 2.8 install was attempted in safemode.
Thanks Jim,...
Looking forward to your next put down.
BTW, I was directed to this forum by MS support as the place to receive help.
"Jim Young" wrote:

> Read the readme files that come with MSDE. You can't just run the setup.exe
> with no parameters an expect to install SQL Server exactly like you would
> like it configured. MSDE a developer's tool so act like a developer and do
> some investigative work before trying to install it.
> Jim
|||I'm sorry, my comment was most inappropriate. I'll try to help you with your
problem any way that I can.
If MSDE is running then MDAC (and the ODBC drivers) must already be
installed - SQL Server can't run without it.
I find it surprising and disappointing that the application you are trying
to install, that requires MSDE, does not make the installation of MSDE
seamless to you. What is the name of the program you are trying to install?
Jim
"BartC" <BartC@.discussions.microsoft.com> wrote in message
news:931E2080-068B-4120-BCC8-5F548C5C5B79@.microsoft.com...
> Hi Jim,
> Thanks for the put down. Most appreciated.
> I am not a developer. I am simply a computer user trying to use a program
> that requires MSDE. And, I did not think that MSDE was a developer tool,
> but simply a db engine that apps could plug into. But clearly you know
> more
> than I.
> And, with a little research by this end user I switched on no back out so
> I
> could read the install log, and I supplied the setup.ini file with the
> following:
> BLANKSAPWD=1
> SQLSecurityMode=SQL
> By stopping the back out I now have SQL server running. but can not
> install
> ODB connectivity drivers. ODBC 2.8 install was attempted in safemode.
> Thanks Jim,...
> Looking forward to your next put down.
> BTW, I was directed to this forum by MS support as the place to receive
> help.
> "Jim Young" wrote:
>
|||"Jim Young" wrote:
> I'm sorry, my comment was most inappropriate. I'll try to help you with your
> problem any way that I can.
> If MSDE is running then MDAC (and the ODBC drivers) must already be
> installed - SQL Server can't run without it.
> I find it surprising and disappointing that the application you are trying
> to install, that requires MSDE, does not make the installation of MSDE
> seamless to you. What is the name of the program you are trying to install?
Hi Jim,
Thank you. We’ll start fresh. Here’s the deal.
OS= WinXPpro.
App=ACT! 2005 (version7)
And yes, I have gone around and around with BEST software (makers of ACT!)
about the need to support the install of SQL MSDE. They claim that it is a
MS problem. However, I have used this install of XP for 2 or 3 yrs with
hardly a BSOD or any other problem. 70 or 80 programs run just fine. (Of
course not all at once). FYI ACT! Is a contact manager. I have been using
v6 with a great deal of success. However, v7 is a total rewrite and uses
SQL. It is essentially version one. I don’t know that I want to trust my
data to a program that is such a problem to install, and relies on some
else’s db engine.
On to the problem:
I could only get MSDE up and running when I switched on don’t back out on
failure:
setup.exe DISABLEROLLBACK=1
I did this based on a clue that the last line in the SQL error log was:
SQL Server is terminating due to a ‘stop’ request from Service Control
Manager.
My thought was that if it can be stopped it must be running. Lo and behold
on reboot the little computer icon is in the system tray. And Task list
shows SQL server running, and sqlmangr running.
However, the drivers tab in ODBC do NOT show SQL Server. And, when I
attempt to install MDAC v2.8 it bombs out.
Part of my problem is that I don’t under stand the functional relationships
between all these elements. My thought is that SQL MSDE is the db engine,
and that MDAC drivers in the ODBC are essentally middle ware allowing the
application to access the db.
Before SQL was running, when I last attempted to install ACT! v7 the error
out was 1603 can not configure server. I have not tried to reinstall yet
wanting to get as many ducks in a row as possible.
Looking forward to your post.
Thanks
BartC
|||You're correct MSDE is the database engine, MDAC is the communication layer
between the application and the database.
The DISABLEROLLBACK option is an option for the Windows installer to not
rollback any changes to your system if the installation fails. The original
error your received, 1603, is basically a general error reporting back that
the MSDE installation failed.
It seem to me that although MSDE is apparently running, the installation is
in an inconsistent state. What I would recommend is completely unistalling
MSDE. The following link is to a KB article for manually removing MSDE from
your system.
http://support.microsoft.com/default...b;en-us;320873
On your system go to Control Panel | Add Remove Program and see if there is
an entry for removing MSDE (it may be referenced as SQL Server). If you find
it then uninstall it. If that is successful then continue with the Remove
Files and Folders part of the KB article and finish the rest of the steps on
the article, removing registry entries.
If this is all successful then you have a system that is cleaned of MSDE.
Next I would try installing MDAC 2.8 and see if you get through that
successfully. If you don't then I would not attempt to install MSDE, since I
doubt it will succeed.
Next reinstall MSDE by running setup.exe with the following command line
parameters. You could use an .ini file for the SECURITYMODE or BLANKSAPWD
options if you want. Personally, I find using the command line easier.
/Lv c:\MSDEsetup.log SECURITYMODE="SQL" BLANKSAPWD=1
This will install a default instance of MSDE to the default directories
(c:\program files\Microsoft SQL Server) with a blank sa password.
If the install fails then you should have a verbose log on the root of drive
C. Post to this group the tail end of the log where the installation start
to break down; you'll see where there is first a failure and then rollbacks
of registry entries and files.
A lot embedded database application are moving their data storage over to
MSDE. It's a very powerful and reliable environment (once you get it
installed!). The problem is that SQL Server is much more complex of an
application to install than a simple flat file database or an Access based
solution. When the installation of MSDE goes sideways, recovering from it
can be quite a lot of trouble, as you've experienced.
Good luck - I hope you are able to get MSDE finally installed.
Jim
"BartC" <BartC@.discussions.microsoft.com> wrote in message
news:1D534BF8-4C6F-49D9-A7F8-CB426F7A8EE8@.microsoft.com...
> "Jim Young" wrote:
> Hi Jim,
> Thank you. We'll start fresh. Here's the deal.
> OS= WinXPpro.
> App=ACT! 2005 (version7)
> And yes, I have gone around and around with BEST software (makers of ACT!)
> about the need to support the install of SQL MSDE. They claim that it is
> a
> MS problem. However, I have used this install of XP for 2 or 3 yrs with
> hardly a BSOD or any other problem. 70 or 80 programs run just fine. (Of
> course not all at once). FYI ACT! Is a contact manager. I have been
> using
> v6 with a great deal of success. However, v7 is a total rewrite and uses
> SQL. It is essentially version one. I don't know that I want to trust my
> data to a program that is such a problem to install, and relies on some
> else's db engine.
> On to the problem:
> I could only get MSDE up and running when I switched on don't back out on
> failure:
> setup.exe DISABLEROLLBACK=1
> I did this based on a clue that the last line in the SQL error log was:
> SQL Server is terminating due to a 'stop' request from Service Control
> Manager.
> My thought was that if it can be stopped it must be running. Lo and
> behold
> on reboot the little computer icon is in the system tray. And Task list
> shows SQL server running, and sqlmangr running.
> However, the drivers tab in ODBC do NOT show SQL Server. And, when I
> attempt to install MDAC v2.8 it bombs out.
> Part of my problem is that I don't under stand the functional
> relationships
> between all these elements. My thought is that SQL MSDE is the db engine,
> and that MDAC drivers in the ODBC are essentally middle ware allowing the
> application to access the db.
> Before SQL was running, when I last attempted to install ACT! v7 the error
> out was 1603 can not configure server. I have not tried to reinstall yet
> wanting to get as many ducks in a row as possible.
> Looking forward to your post.
> Thanks
> BartC
|||Hi Jim,
Well I see one error of my ways. I was installing MSDE first and then
attempting an install of MDAC 2.8.
If I understand you correctly after I remove everything I should start with
MDAC and then go on to installing MSDE.
I will try this, but it will have to wait for a day or two. The pressure of
work interfers with all the fun stuff ;-)
Thanks... I'll post results in a few days.
BartC
"Jim Young" wrote:
> snip...
> It seem to me that although MSDE is apparently running, the installation is
> in an inconsistent state. What I would recommend is completely unistalling
> MSDE. The following link is to a KB article for manually removing MSDE from
> your system.
|||It wasn't an error to install MDAC after MSDE; I just thought it would be a
good test to make sure that your system is in good order first. All windows
versions since Windows 2000 come with MDAC preinstalled, but it is best to
upgrade to 2.8 before you start the MSDE installation.
Jim
"BartC" <BartC@.discussions.microsoft.com> wrote in message
news:075F0748-C889-4FA2-8E80-EE7482B059EE@.microsoft.com...
> Hi Jim,
> Well I see one error of my ways. I was installing MSDE first and then
> attempting an install of MDAC 2.8.
> If I understand you correctly after I remove everything I should start
> with
> MDAC and then go on to installing MSDE.
> I will try this, but it will have to wait for a day or two. The pressure
> of
> work interfers with all the fun stuff ;-)
> Thanks... I'll post results in a few days.
> BartC
>
>
>
> "Jim Young" wrote:
>
|||Jim,
OK, here is the latest:
re: KB 320873 - the Msizap.exe failed to find the SQL server to uninstall.
There was no SQL server in Add/Remove.
This in spite of the fact the icon was in the system tray, and I could call
up the control panel to start and stop the SQL server.
Soooooo... I stepped through the manual removal. And took out lots of SQL
keys that were in the registry, plus all the stuff that the KB article
suggested. Removed the temp files and the entire branch of SQL server in the
directory structure.
I also ran Registry First Aid and did a general clean up of the registry.
I then ran the MDACsetup and received the following:
MDAC 2.8 RTM is incompatible with this version of Windows. All of its
features are currently part of Windows.
There is a Details button that brought up nothing.
OK, so which is it... Incompatible with WinXP pro or already installed?
Hard to know from that error mess.
Forging ahead I ran the SQL setup with your (Jim’s) command line switches.
(See previous message.) That resulted in the same error as before... to wit:
Setup failed to configure the server. Refer to the error logs.
With the verbose log switched turned on the resultant log is 3.6 MB. I am
not going to post that (don’t think I could anyway.) There is a lot of note
1: 2360- stuff near the top, and then tons of opening and adding RegValues.
But here is the middle part. This is near the end of the install and a bit
into the rollback. It seems to vomit at (24!1C) at the config server
execution.
I am at a total loss as how to proceed.
Starting custom action CallSQLAdHlp
c:\Program Files\Microsoft SQL Server\80\Tools\Binn\sqladhlp.exe : 0
MSI (s) (24:B8) [06:36:45:799]: Executing op:
ActionStart(Name=RollbackAgentSecurity.2D02443E_70 02_4C0B_ABC9_EAB2C064397B,,)
MSI (s) (24:B8) [06:36:45:799]: Executing op:
CustomActionSchedule(Action=RollbackAgentSecurity. 2D02443E_7002_4C0B_ABC9_EAB2C064397B,ActionType=12 81,Source=BinaryData,Target=UnInstSQLAgentSecurity ,)
MSI (s) (24:B8) [06:36:45:809]: Executing op:
ActionStart(Name=InstallAgentSecurity.2D02443E_700 2_4C0B_ABC9_EAB2C064397B,,)
MSI (s) (24:B8) [06:36:45:809]: Executing op:
CustomActionSchedule(Action=InstallAgentSecurity.2 D02443E_7002_4C0B_ABC9_EAB2C064397B,ActionType=102 5,Source=BinaryData,Target=InstallSQLAgentSecurity ,)
MSI (s) (24:E8) [06:36:45:819]: Invoking remote custom action. DLL:
C:\WINDOWS\Installer\MSI45.tmp, Entrypoint: InstallSQLAgentSecurity
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
TempFolder is
C:\DOCUME~1\Bart\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\
Loading extended custom action library
C:\DOCUME~1\Bart\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sqlcax.dll
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
Starting custom action InstallSQLAgentSecurity
InstallSQLAgentSecurity succeeded
MSI (s) (24:B8) [06:36:46:070]: Executing op:
ActionStart(Name=SkuIt.2D02443E_7002_4C0B_ABC9_EAB 2C064397B,,)
MSI (s) (24:B8) [06:36:46:070]: Executing op:
CustomActionSchedule(Action=SkuIt.2D02443E_7002_4C 0B_ABC9_EAB2C064397B,ActionType=1025,Source=Binary Data,Target=SkuIt,)
MSI (s) (24:1C) [06:36:46:070]: Invoking remote custom action. DLL:
C:\WINDOWS\Installer\MSI46.tmp, Entrypoint: SkuIt
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
TempFolder is
C:\DOCUME~1\Bart\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\
Loading extended custom action library
C:\DOCUME~1\Bart\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sqlcax.dll
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
Starting custom action SkuIt
MSI (s) (24:B8) [06:36:46:320]: Executing op:
ActionStart(Name=ConfigServer.2D02443E_7002_4C0B_A BC9_EAB2C064397B...
MSI (s) (24:B8) [06:36:46:330]: Executing op:
CustomActionSchedule(Action=ConfigServer.2D02443E_ 7002_4C0B_ABC9_EAB2C064397B...
MSI (s) (24:84) [06:36:46:330]: Invoking remote custom action. DLL:
C:\WINDOWS\Installer\MSI47.tmp, Entrypoint: ConfigServer
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
TempFolder is
C:\DOCUME~1\Bart\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\
Loading extended custom action library
C:\DOCUME~1\Bart\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sqlcax.dll
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
Starting custom action ConfigServer
Executing "c:\Program Files\Microsoft SQL Server\80\Tools\Binn\cnfgsvr.exe
-V 1 -M 1 -U sa -I "MSSQLSERVER" -Q "SQL_Latin1_General_CP1_CI_AS""
MSI (c) (20:88) [06:37:12:798]: Font created. Charset: Req=0, Ret=0, Font:
Req=MS Shell Dlg, Ret=MS Shell Dlg
MSI (s) (24!1C) [06:37:50:753]: Product: Microsoft SQL Server Desktop Engine
-- Setup failed to configure the server. Refer to the server error logs and
setup error logs for more information.
Action ended 6:37:50: InstallFinalize. Return value 3.
MSI (s) (24:B8) [06:37:50:783]: User policy value 'DisableRollback' is 0
MSI (s) (24:B8) [06:37:50:783]: Machine policy value 'DisableRollback' is 0
MSI (s) (24:B8) [06:37:50:823]: Executing op:
Header(Signature=1397708873,Version=300,Timestamp= 844313717,LangId=1033,Platform=0,ScriptType=2,Scri ptMajorVersion=21,ScriptMinorVersion=4,ScriptAttri butes=1)
MSI (s) (24:B8) [06:37:50:823]: Executing op: DialogInfo(Type=0,Argument=1033)
MSI (s) (24:B8) [06:37:50:823]: Executing op:
DialogInfo(Type=1,Argument=Microsoft SQL Server Desktop Engine)
MSI (s) (24:B8) [06:37:50:823]: Executing op:
RollbackInfo(,RollbackAction=Rollback,RollbackDesc ription=Rolling back
action:,RollbackTemplate=[1],CleanupAction=RollbackCleanup,CleanupDescription= Removing backup files,CleanupTemplate=File: [1])
MSI (s) (24:B8) [06:37:50:823]: Executing op:
RegisterBackupFile(File=c:\Config.Msi\3cca84.rbf)
MSI (s) (24:B8) [06:37:50:823]: Executing op:
ActionStart(Name=ConfigServer.2D02443E_7002_4C0B_A BC9_EAB2C064397B...
MSI (s) (24:B8) [06:37:50:823]: Executing op:
ProductInfo(ProductKey={E09B48B5-E141-427A-AB0C-D3605127224A},ProductName=Microsoft
SQL Server Desktop
Engine,PackageName=SqlRun01.msi,Language=1033,Vers ion=134218489,Assignment=1,ObsoleteArg=0,,,Package Code={D29DCF7A-8199-4373-BA0D-2F3635EC940C},,,InstanceType=0,LUASetting=0)
MSI (s) (24:B8) [06:37:50:833]: Executing op:
ActionStart(Name=SkuIt.2D02443E_7002_4C0B_ABC9_EAB 2C064397B,,)
MSI (s) (24:B8) [06:37:50:833]: Executing op:
ActionStart(Name=InstallAgentSecurity.2D02443E_700 2_4C0B_ABC9_EAB2C064397B,,)
MSI (s) (24:B8) [06:37:50:833]: Executing op:
ActionStart(Name=RollbackAgentSecurity.2D02443E_70 02_4C0B_ABC9_EAB2C064397B,,)
MSI (s) (24:B8) [06:37:50:833]: Executing op:
CustomActionRollback(Action=RollbackAgentSecurity. 2D02443E_7002_4C0B_ABC9_EAB2C064397B,ActionType=12 81,Source=BinaryData,Target=UnInstSQLAgentSecurity ,)
MSI (s) (24:F8) [06:37:50:833]: Invoking remote custom action. DLL:
C:\WINDOWS\Installer\MSI48.tmp, Entrypoint: UnInstSQLAgentSecurity
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
TempFolder is
C:\DOCUME~1\Bart\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\
Loading extended custom action library
C:\DOCUME~1\Bart\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sqlcax.dll
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
Starting custom action UnInstSQLAgentSecurity
Starting custom action UnInstSQLAgentSecurity
MSI (s) (24:B8) [06:37:51:003]: Executing op:
ActionStart(Name=InstallSQLAdHlp.2D02443E_7002_4C0 B_ABC9_EAB2C064397B,,)
MSI (s) (24:B8) [06:37:51:003]: Executing op:
ActionStart(Name=InstallPerfMon.2D02443E_7002_4C0B _ABC9_EAB2C064397B,,)
MSI (s) (24:B8) [06:37:51:003]: Executing op:
ActionStart(Name=InstallServices,Description=Insta lling new
services,Template=Service: [2])
MSI (s) (24:B8) [06:37:51:003]: Executing op:
ServiceControl(,Name=MSSQLSERVER,Action=8,,)
MSI (s) (24:B8) [06:37:51:003]: Executing op:
ServiceControl(,Name=SQLSERVERAGENT,Action=8,,)
MSI (s) (24:B8) [06:37:51:193]: Executing op:
ActionStart(Name=RegisterTypeLibraries,Description =Registering type
libraries,Template=LibID: [1])
MSI (s) (24:B8) [06:37:51:193]: Executing op:
TypeLibraryUnregister(,,FilePath=c:\WINDOWS\system 32\atl.dll,LibID={44EC0535-400F-11D0-9DCD-00A0C90391D3},Version=-2147483648,,Language=0,,BinaryType=0)
MSI (s) (24:B8) [06:37:51:193]: CMsiServices::ProcessTypeLibrary runs in
local context, not impersonated.
MSI (s) (24:B8) [06:37:51:203]: ProcessTypeLibraryCore returns: 0. (0 means
OK)
MSI (s) (24:B8) [06:37:51:213]: Executing op:
TypeLibraryUnregister(,,FilePath=c:\Program Files\Microsoft SQL
Server\80\Tools\Binn\dtspump.DLL,LibID={10010200-740B-11D0-AE7B-00AA004A34D5},Version=-2147483648,,Language=0,,BinaryType=0)
MSI (s) (24:B8) [06:37:51:213]: CMsiServices::ProcessTypeLibrary runs in
local context, not impersonated.
MSI (s) (24:B8) [06:37:51:223]: ProcessTypeLibraryCore returns: 0. (0 means
OK)
MSI (s) (24:B8) [06:37:51:233]: Executing op:
TypeLibraryUnregister(,,FilePath=c:\Program Files\Microsoft SQL
Server\80\Tools\Binn\dtspkg.DLL,LibID={10010001-EB1C-11CF-AE6E-00AA004A34D5},Version=-2147483648,,Language=0,,BinaryType=0)
MSI (s) (24:B8) [06:37:51:233]: CMsiServices::ProcessTypeLibrary runs in
local context, not impersonated.
MSI (s) (24:B8) [06:37:51:304]: ProcessTypeLibraryCore returns: 0. (0 means
OK)
|||This may be a long shot, but is the Server service running on your machine?
Go to Control Panel | Adminstrative Tools | Services. If it is not running
then bring up the properties for the service, set the startup to automatic
and start the service. Then try re-installing MSDE.
Jim
"BartC" <BartC@.discussions.microsoft.com> wrote in message
news:B7EE12E7-D84E-4D83-96E6-70229C1F445C@.microsoft.com...
> Jim,
> OK, here is the latest:
> re: KB 320873 - the Msizap.exe failed to find the SQL server to uninstall.
> There was no SQL server in Add/Remove.
> This in spite of the fact the icon was in the system tray, and I could
> call
> up the control panel to start and stop the SQL server.
> Soooooo... I stepped through the manual removal. And took out lots of
> SQL
> keys that were in the registry, plus all the stuff that the KB article
> suggested. Removed the temp files and the entire branch of SQL server in
> the
> directory structure.
> I also ran Registry First Aid and did a general clean up of the registry.
> I then ran the MDACsetup and received the following:
> MDAC 2.8 RTM is incompatible with this version of Windows. All of its
> features are currently part of Windows.
> There is a Details button that brought up nothing.
> OK, so which is it... Incompatible with WinXP pro or already installed?
> Hard to know from that error mess.
> Forging ahead I ran the SQL setup with your (Jim's) command line switches.
> (See previous message.) That resulted in the same error as before... to
> wit:
> Setup failed to configure the server. Refer to the error logs.
> With the verbose log switched turned on the resultant log is 3.6 MB. I am
> not going to post that (don't think I could anyway.) There is a lot of
> note
> 1: 2360- stuff near the top, and then tons of opening and adding
> RegValues.
> But here is the middle part. This is near the end of the install and a
> bit
> into the rollback. It seems to vomit at (24!1C) at the config server
> execution.
> I am at a total loss as how to proceed.
> Starting custom action CallSQLAdHlp
> c:\Program Files\Microsoft SQL Server\80\Tools\Binn\sqladhlp.exe : 0
> MSI (s) (24:B8) [06:36:45:799]: Executing op:
> ActionStart(Name=RollbackAgentSecurity.2D02443E_70 02_4C0B_ABC9_EAB2C064397B,,)
> MSI (s) (24:B8) [06:36:45:799]: Executing op:
> CustomActionSchedule(Action=RollbackAgentSecurity. 2D02443E_7002_4C0B_ABC9_EAB2C064397B,ActionType=12 81,Source=BinaryData,Target=UnInstSQLAgentSecurity ,)
> MSI (s) (24:B8) [06:36:45:809]: Executing op:
> ActionStart(Name=InstallAgentSecurity.2D02443E_700 2_4C0B_ABC9_EAB2C064397B,,)
> MSI (s) (24:B8) [06:36:45:809]: Executing op:
> CustomActionSchedule(Action=InstallAgentSecurity.2 D02443E_7002_4C0B_ABC9_EAB2C064397B,ActionType=102 5,Source=BinaryData,Target=InstallSQLAgentSecurity ,)
> MSI (s) (24:E8) [06:36:45:819]: Invoking remote custom action. DLL:
> C:\WINDOWS\Installer\MSI45.tmp, Entrypoint: InstallSQLAgentSecurity
> SOFTWARE\Microsoft\Microsoft SQL Server
> Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
> TempFolder is
> C:\DOCUME~1\Bart\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\
> Loading extended custom action library
> C:\DOCUME~1\Bart\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sqlcax.dll
> SOFTWARE\Microsoft\Microsoft SQL Server
> Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
> Starting custom action InstallSQLAgentSecurity
> InstallSQLAgentSecurity succeeded
> MSI (s) (24:B8) [06:36:46:070]: Executing op:
> ActionStart(Name=SkuIt.2D02443E_7002_4C0B_ABC9_EAB 2C064397B,,)
> MSI (s) (24:B8) [06:36:46:070]: Executing op:
> CustomActionSchedule(Action=SkuIt.2D02443E_7002_4C 0B_ABC9_EAB2C064397B,ActionType=1025,Source=Binary Data,Target=SkuIt,)
> MSI (s) (24:1C) [06:36:46:070]: Invoking remote custom action. DLL:
> C:\WINDOWS\Installer\MSI46.tmp, Entrypoint: SkuIt
> SOFTWARE\Microsoft\Microsoft SQL Server
> Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
> TempFolder is
> C:\DOCUME~1\Bart\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\
> Loading extended custom action library
> C:\DOCUME~1\Bart\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sqlcax.dll
> SOFTWARE\Microsoft\Microsoft SQL Server
> Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
> Starting custom action SkuIt
> MSI (s) (24:B8) [06:36:46:320]: Executing op:
> ActionStart(Name=ConfigServer.2D02443E_7002_4C0B_A BC9_EAB2C064397B...
> MSI (s) (24:B8) [06:36:46:330]: Executing op:
> CustomActionSchedule(Action=ConfigServer.2D02443E_ 7002_4C0B_ABC9_EAB2C064397B...
> MSI (s) (24:84) [06:36:46:330]: Invoking remote custom action. DLL:
> C:\WINDOWS\Installer\MSI47.tmp, Entrypoint: ConfigServer
> SOFTWARE\Microsoft\Microsoft SQL Server
> Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
> TempFolder is
> C:\DOCUME~1\Bart\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\
> Loading extended custom action library
> C:\DOCUME~1\Bart\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sqlcax.dll
> SOFTWARE\Microsoft\Microsoft SQL Server
> Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
> Starting custom action ConfigServer
> Executing "c:\Program Files\Microsoft SQL Server\80\Tools\Binn\cnfgsvr.exe
> -V 1 -M 1 -U sa -I "MSSQLSERVER" -Q "SQL_Latin1_General_CP1_CI_AS""
> MSI (c) (20:88) [06:37:12:798]: Font created. Charset: Req=0, Ret=0,
> Font:
> Req=MS Shell Dlg, Ret=MS Shell Dlg
> MSI (s) (24!1C) [06:37:50:753]: Product: Microsoft SQL Server Desktop
> Engine
> -- Setup failed to configure the server. Refer to the server error logs
> and
> setup error logs for more information.
> Action ended 6:37:50: InstallFinalize. Return value 3.
> MSI (s) (24:B8) [06:37:50:783]: User policy value 'DisableRollback' is 0
> MSI (s) (24:B8) [06:37:50:783]: Machine policy value 'DisableRollback' is
> 0
> MSI (s) (24:B8) [06:37:50:823]: Executing op:
> Header(Signature=1397708873,Version=300,Timestamp= 844313717,LangId=1033,Platform=0,ScriptType=2,Scri ptMajorVersion=21,ScriptMinorVersion=4,ScriptAttri butes=1)
> MSI (s) (24:B8) [06:37:50:823]: Executing op:
> DialogInfo(Type=0,Argument=1033)
> MSI (s) (24:B8) [06:37:50:823]: Executing op:
> DialogInfo(Type=1,Argument=Microsoft SQL Server Desktop Engine)
> MSI (s) (24:B8) [06:37:50:823]: Executing op:
> RollbackInfo(,RollbackAction=Rollback,RollbackDesc ription=Rolling back
> action:,RollbackTemplate=[1],CleanupAction=RollbackCleanup,CleanupDescription= Removing
> backup files,CleanupTemplate=File: [1])
> MSI (s) (24:B8) [06:37:50:823]: Executing op:
> RegisterBackupFile(File=c:\Config.Msi\3cca84.rbf)
> MSI (s) (24:B8) [06:37:50:823]: Executing op:
> ActionStart(Name=ConfigServer.2D02443E_7002_4C0B_A BC9_EAB2C064397B...
> MSI (s) (24:B8) [06:37:50:823]: Executing op:
> ProductInfo(ProductKey={E09B48B5-E141-427A-AB0C-D3605127224A},ProductName=Microsoft
> SQL Server Desktop
> Engine,PackageName=SqlRun01.msi,Language=1033,Vers ion=134218489,Assignment=1,ObsoleteArg=0,,,Package Code={D29DCF7A-8199-4373-BA0D-2F3635EC940C},,,InstanceType=0,LUASetting=0)
> MSI (s) (24:B8) [06:37:50:833]: Executing op:
> ActionStart(Name=SkuIt.2D02443E_7002_4C0B_ABC9_EAB 2C064397B,,)
> MSI (s) (24:B8) [06:37:50:833]: Executing op:
> ActionStart(Name=InstallAgentSecurity.2D02443E_700 2_4C0B_ABC9_EAB2C064397B,,)
> MSI (s) (24:B8) [06:37:50:833]: Executing op:
> ActionStart(Name=RollbackAgentSecurity.2D02443E_70 02_4C0B_ABC9_EAB2C064397B,,)
> MSI (s) (24:B8) [06:37:50:833]: Executing op:
> CustomActionRollback(Action=RollbackAgentSecurity. 2D02443E_7002_4C0B_ABC9_EAB2C064397B,ActionType=12 81,Source=BinaryData,Target=UnInstSQLAgentSecurity ,)
> MSI (s) (24:F8) [06:37:50:833]: Invoking remote custom action. DLL:
> C:\WINDOWS\Installer\MSI48.tmp, Entrypoint: UnInstSQLAgentSecurity
> SOFTWARE\Microsoft\Microsoft SQL Server
> Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
> TempFolder is
> C:\DOCUME~1\Bart\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\
> Loading extended custom action library
> C:\DOCUME~1\Bart\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sqlcax.dll
> SOFTWARE\Microsoft\Microsoft SQL Server
> Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
> Starting custom action UnInstSQLAgentSecurity
> Starting custom action UnInstSQLAgentSecurity
> MSI (s) (24:B8) [06:37:51:003]: Executing op:
> ActionStart(Name=InstallSQLAdHlp.2D02443E_7002_4C0 B_ABC9_EAB2C064397B,,)
> MSI (s) (24:B8) [06:37:51:003]: Executing op:
> ActionStart(Name=InstallPerfMon.2D02443E_7002_4C0B _ABC9_EAB2C064397B,,)
> MSI (s) (24:B8) [06:37:51:003]: Executing op:
> ActionStart(Name=InstallServices,Description=Insta lling new
> services,Template=Service: [2])
> MSI (s) (24:B8) [06:37:51:003]: Executing op:
> ServiceControl(,Name=MSSQLSERVER,Action=8,,)
> MSI (s) (24:B8) [06:37:51:003]: Executing op:
> ServiceControl(,Name=SQLSERVERAGENT,Action=8,,)
> MSI (s) (24:B8) [06:37:51:193]: Executing op:
> ActionStart(Name=RegisterTypeLibraries,Description =Registering type
> libraries,Template=LibID: [1])
> MSI (s) (24:B8) [06:37:51:193]: Executing op:
> TypeLibraryUnregister(,,FilePath=c:\WINDOWS\system 32\atl.dll,LibID={44EC0535-400F-11D0-9DCD-00A0C90391D3},Version=-2147483648,,Language=0,,BinaryType=0)
> MSI (s) (24:B8) [06:37:51:193]: CMsiServices::ProcessTypeLibrary runs in
> local context, not impersonated.
> MSI (s) (24:B8) [06:37:51:203]: ProcessTypeLibraryCore returns: 0. (0
> means
> OK)
> MSI (s) (24:B8) [06:37:51:213]: Executing op:
> TypeLibraryUnregister(,,FilePath=c:\Program Files\Microsoft SQL
> Server\80\Tools\Binn\dtspump.DLL,LibID={10010200-740B-11D0-AE7B-00AA004A34D5},Version=-2147483648,,Language=0,,BinaryType=0)
> MSI (s) (24:B8) [06:37:51:213]: CMsiServices::ProcessTypeLibrary runs in
> local context, not impersonated.
> MSI (s) (24:B8) [06:37:51:223]: ProcessTypeLibraryCore returns: 0. (0
> means
> OK)
> MSI (s) (24:B8) [06:37:51:233]: Executing op:
> TypeLibraryUnregister(,,FilePath=c:\Program Files\Microsoft SQL
> Server\80\Tools\Binn\dtspkg.DLL,LibID={10010001-EB1C-11CF-AE6E-00AA004A34D5},Version=-2147483648,,Language=0,,BinaryType=0)
> MSI (s) (24:B8) [06:37:51:233]: CMsiServices::ProcessTypeLibrary runs in
> local context, not impersonated.
> MSI (s) (24:B8) [06:37:51:304]: ProcessTypeLibraryCore returns: 0. (0
> means
> OK)
>

Can not bring MSDTC online in W2K3EE-SP1 cluster (2 nodes)

I've installed Windows Server 2003 EE SP1 Cluster successfully with two nodes
and now I'm trying to install MS SQL server 2000 Cluster on it..
as part of the preparation is to add new resource for MSDTC before install
SQL server 2000 then upgrade to sql server 2000 sp3a..
I've used two methods to add MSDTC resource to the cluster ... one by using
the Cluster resources Quorum disk and ip address... and the second time using
special ip and disk for MSDTC different than the quorum and add in separate
group.. but in both methods the same error msdtc resource failed..
errors in event log:
=================================
application log: eventid 4383
MS DTC was unable to determine the state of the cluster service on this
machine. MS DTC cannot continue to startup. Please contact Microsoft Product
Support. Error Specifics:
d:\srvrtm\com\complus\dtc\shared\mtxclu\mtxclusetu phelper.cpp:498, Pid: 2636,
CmdLine: C:\WINOS\system32\msdtc.exe
===========================================
in the security log: eventid 560
Object Open:
Object Server: SC Manager
Object Type: SERVICE OBJECT
Object Name: ClusSvc
Handle ID: -
Operation ID: {0,27022083}
Process ID: 632
Image File Name: C:\WINOS\system32\services.exe
Primary User Name: Q4A-DEV$
Primary Domain: IAEA
Primary Logon ID: (0x0,0x3E7)
Client User Name: NETWORK SERVICE
Client Domain: NT AUTHORITY
Client Logon ID: (0x0,0x3E4)
Accesses: READ_CONTROL
Query service configuration information
Query status of service
Enumerate dependencies of service
Query information from service
Privileges: -
Restricted Sid Count: 0
Access Mask: 0x2008D
========================================
in the system log
eventid 7034
The Distributed Transaction Coordinator service terminated unexpectedly. It
has done this 1 time(s).
======================================
Please let me know how to resolve it..
I've used as well the method in http://support.microsoft.com/kb/301600/en-us
but the same result..
I was reading the news and found that many have troubles during the
installation because the sql server 2000 EE doesn't contain sp3a and in many
cases it failed to continue with the installation on W2K3EESP1 in the process
before the upgrade to sp3a...
how to fix the msdtc problem in the cluster !!!?
Thanks
best regards,
Samo
Sounds like a permissions issue based on the info you posted. Check the
startup account for the MSDTC service on each node. Make sure it is a
domain-level account that has admin priviledges on the box. I generally use
the cluster service account for the MSDTC account to avoid any permissions
issues.
Geoff N. Hiten
Microsoft SQL Server MVP
"Samo" <Samo@.discussions.microsoft.com> wrote in message
news:1EF209B9-9074-4D0E-899E-25C46865BF52@.microsoft.com...
> I've installed Windows Server 2003 EE SP1 Cluster successfully with two
> nodes
> and now I'm trying to install MS SQL server 2000 Cluster on it..
> as part of the preparation is to add new resource for MSDTC before install
> SQL server 2000 then upgrade to sql server 2000 sp3a..
> I've used two methods to add MSDTC resource to the cluster ... one by
> using
> the Cluster resources Quorum disk and ip address... and the second time
> using
> special ip and disk for MSDTC different than the quorum and add in
> separate
> group.. but in both methods the same error msdtc resource failed..
> errors in event log:
> =================================
> application log: eventid 4383
> MS DTC was unable to determine the state of the cluster service on this
> machine. MS DTC cannot continue to startup. Please contact Microsoft
> Product
> Support. Error Specifics:
> d:\srvrtm\com\complus\dtc\shared\mtxclu\mtxclusetu phelper.cpp:498, Pid:
> 2636,
> CmdLine: C:\WINOS\system32\msdtc.exe
> ===========================================
> in the security log: eventid 560
> Object Open:
> Object Server: SC Manager
> Object Type: SERVICE OBJECT
> Object Name: ClusSvc
> Handle ID: -
> Operation ID: {0,27022083}
> Process ID: 632
> Image File Name: C:\WINOS\system32\services.exe
> Primary User Name: Q4A-DEV$
> Primary Domain: IAEA
> Primary Logon ID: (0x0,0x3E7)
> Client User Name: NETWORK SERVICE
> Client Domain: NT AUTHORITY
> Client Logon ID: (0x0,0x3E4)
> Accesses: READ_CONTROL
> Query service configuration information
> Query status of service
> Enumerate dependencies of service
> Query information from service
> Privileges: -
> Restricted Sid Count: 0
> Access Mask: 0x2008D
> ========================================
> in the system log
> eventid 7034
> The Distributed Transaction Coordinator service terminated unexpectedly.
> It
> has done this 1 time(s).
> ======================================
> Please let me know how to resolve it..
> I've used as well the method in
> http://support.microsoft.com/kb/301600/en-us
> but the same result..
> I was reading the news and found that many have troubles during the
> installation because the sql server 2000 EE doesn't contain sp3a and in
> many
> cases it failed to continue with the installation on W2K3EESP1 in the
> process
> before the upgrade to sp3a...
> how to fix the msdtc problem in the cluster !!!?
> Thanks
> --
> best regards,
> Samo
|||I've just spent two days trying to get SQL2K on a W2kEE (no sp1)
cluster.
My first problem was getting the MSDTC to come online. I could
configure it but not get it online.
I tried all the MS suggestions and more besides including
uninstall/reinstall MSDTC. In a vain attempt to get it working I ended
up breaking the cluster service, it refused to start.
My solution was to rebuild the server, setup my cluster group for
network/quorom, then before setting up DTC group, make registry change
for the Clusterinstallstate, enable network DTC and it worked first
time.
Sorry I couldn't give you a quick fix. I've still got to fix my
installation failure - unable to install SQL on a 2nd node.
Steve
"Geoff N. Hiten" <SRDBA@.Careerbuilder.com> wrote in message news:<eDd30kSTFHA.3392@.TK2MSFTNGP12.phx.gbl>...[vbcol=seagreen]
> Sounds like a permissions issue based on the info you posted. Check the
> startup account for the MSDTC service on each node. Make sure it is a
> domain-level account that has admin priviledges on the box. I generally use
> the cluster service account for the MSDTC account to avoid any permissions
> issues.
> Geoff N. Hiten
> Microsoft SQL Server MVP
>
> "Samo" <Samo@.discussions.microsoft.com> wrote in message
> news:1EF209B9-9074-4D0E-899E-25C46865BF52@.microsoft.com...
|||I've used the Cluster service account which has local admin rights, log on as
service, etc on both nodes but the same application eventid 4383 error
persist and msdtc failed to start ...
best regards,
Samo
"Geoff N. Hiten" wrote:

> Sounds like a permissions issue based on the info you posted. Check the
> startup account for the MSDTC service on each node. Make sure it is a
> domain-level account that has admin priviledges on the box. I generally use
> the cluster service account for the MSDTC account to avoid any permissions
> issues.
> Geoff N. Hiten
> Microsoft SQL Server MVP
>
> "Samo" <Samo@.discussions.microsoft.com> wrote in message
> news:1EF209B9-9074-4D0E-899E-25C46865BF52@.microsoft.com...
>
>
|||Just to let you know , the MSDTC resource started without problem after
using the cluster service account and "restarting the cluster service" which
is strange...
a good start.. now I'll start with the active/active installation of sql
server 2000 EE cluster and let you know if I face any issue...
P.S.: I'm installing it on W2K3EE SP1 cluster...
Thanks,
best regards,
Samo
"Samo" wrote:
[vbcol=seagreen]
> I've used the Cluster service account which has local admin rights, log on as
> service, etc on both nodes but the same application eventid 4383 error
> persist and msdtc failed to start ...
> --
> best regards,
> Samo
>
> "Geoff N. Hiten" wrote:
|||Hi,
I'm interested by what you say about using the cluster service account.
Did you use this account to start the DTC service?
Steve
"Samo" wrote:
[vbcol=seagreen]
> Just to let you know , the MSDTC resource started without problem after
> using the cluster service account and "restarting the cluster service" which
> is strange...
> a good start.. now I'll start with the active/active installation of sql
> server 2000 EE cluster and let you know if I face any issue...
> P.S.: I'm installing it on W2K3EE SP1 cluster...
> Thanks,
> --
> best regards,
> Samo
>
> "Samo" wrote:

Can no longer open my SSIS packages

I am in the process of migrating DTS 2000 packages via DTS Migration Wizard.

I ran all of the packages through the wizard. Then, I successfully completed changing the remaining issues in two of my packages to SSIS. Everything was fine. The second package I completed is called from a SQL Agent Job. I managed to get the job step converted to use SSIS package. It ran successfully.

Now, I am trying to open other packages to work on them and I get "Microsoft Visual Studio is unable to load this document: Value does not fall within the expected range." and a message window that says "Object reference not set to an instance of an object." This actually happens with the two that I migrated, also. I can no longer access them.

What happened?!?!?!? Does anyone have any experience with this?

Well, the solution I had the files in must have been corrupted. I can open individual files using BIDS. I just can't do anything with them from the project. Seems as though a collection might have gone willy.

Can I move some column position by using SQL command ?

I created SQL table follow by XSD file

And when any users added new column to XSD in ordinal position = 3

But after my program successfully created new column, its position is the last position

What can I do ??

I suspect why I can't set it (I've looked for solution on MSDN already)

even though

We can see ordinal position by

this query

SELECT *
FROM INFORMATION_SCHEMA.Columns

What can I do for solving ?? Help me please

You're adding columns dynamically? They will go to the end and I'd be surprised if there was any way to change the position.

But more importantly, why are you adding columns dynamically and why do you care what position the columns are in? It makes no difference what the physical col position is in a table