Peer to Peer Replication Problem with BLOBs

I've set up a development peer to peer replication between 2 SQL Server 2005 on 2 Windows XP SP2 systems.

The distribution agent is configured to use UseOledbStreaming. When saving smaller BLOBs of approx 10000 KB all works fine. When I try to replicate larger data I get the following error message in the Synchronisation status window and in the history of the distributor to the subscriber tab in the replication monitor:

Der Verteilungs-Agent verwendet die OLE DB-Streamingoptimierung für die Replikation von BLOB-Daten (Binary Large Objects) mit mehr als 16384 Bytes. Der Schwellenwert für die Optimierung kann über die Befehlszeile mithilfe des -OledbStreamThreshold-Parameters festgelegt werden.
(Quelle: MSSQL_REPL, Fehlernummer: MSSQL_REPL21060)
Hilfe abrufen: http://help/MSSQL_REPL21060

I also tried different values of OledbStreamThreshold.

I need to be able to replicate BLOBs in size of up to 1 GB.

I'm writing the BLOB data in chunks to the table DB_BLOBData , that isn't an article for replication and at the end copy it to the destination table MyBLOBTable which is an article. I do this, because I noticed that the transaction log on the subscriber database becomes incredibly huge (>60 GB for maybe 50 1000KB BLOBs written in blocks size of 65536 bytes) when directly updating the row using BLOB.Write(...). I think, that for each write at least the whole BLOB contents is written to the transaction log.

The replication uses Stored procedures, Update using SCALL syntax.

The code of the SP:

...
IF @.action = 1
BEGIN
UPDATE MyBLOBTable
SET DocContent = (SELECT BLOB from DB_BLOBData where GuidId = @.id)
, DocSize = (SELECT DATALENGTH(BLOB) from DB_BLOBData where GuidId = @.id)
WHERE DocId = @.id
DELETE FROM DB_BLOBData WHERE GuidId = @.id
END

IF @.action = 0
BEGIN
IF @.Offset = 0
BEGIN
INSERT DB_BLOBData( GuidId, BLOB )
VALUES ( @.id, @.value )
END
ELSE
BEGIN
UPDATE DB_BLOBData
SET BLOB.Write( @.value , @.Offset , @.Length )
WHERE GuidId = @.id
END
END

SELECT @.ModDttm = modDttm
, @.ModUser = modUser
, @.ModClient = modClient
, @.ModAppl = modAppl
FROM MyBLOBTable
WHERE DocId = @.id

RETURN 0
END

TIA,

Hannoman

Hi Hannoman,

While my ancestors are from Germany, my German is severly lacking, thus my inability to decipher the error message , but you might look at the following in BOL:

ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/rpldata9/html/11061c08-661a-4386-8996-9685cd81de05.htm

Particuarly, the section that talks about LOB's. I don't know if that answers your question, but if it doesn't hopefully it will point you in the right direction.

Scott

|||

Hello Scott

I'm using transactional peer to peer replication.

The error message means something like

The distribution agent uses OLE DB-Streaming optimization for replicating BLOB data with size larger than 16384 bytes. The threshold for the optimizationcan be defined on the command line using the OledbStreamThreshold parameter.

(Source: MSSQL_REPL, Error number: MSSQL_REPL21060)
get help: http://help/MSSQL_REPL21060

The problem is, that this kind of error deadlocks the replication. As I don't know how to handle this, I have to delete the publications and subscriptions and set them up again. In an production environment this wouldn't be a solution.

Hannoman

|||Unfortunately this is a known bug for Peer to Peer in SQL 2005, as a workaround you can try setting -CommitBatchSize to 1.

Peer to Peer Replication Problem with BLOBs

I've set up a development peer to peer replication between 2 SQL Server 2005 on 2 Windows XP SP2 systems.

The distribution agent is configured to use UseOledbStreaming. When saving smaller BLOBs of approx 10000 KB all works fine. When I try to replicate larger data I get the following error message in the Synchronisation status window and in the history of the distributor to the subscriber tab in the replication monitor:

Der Verteilungs-Agent verwendet die OLE DB-Streamingoptimierung für die Replikation von BLOB-Daten (Binary Large Objects) mit mehr als 16384 Bytes. Der Schwellenwert für die Optimierung kann über die Befehlszeile mithilfe des -OledbStreamThreshold-Parameters festgelegt werden.
(Quelle: MSSQL_REPL, Fehlernummer: MSSQL_REPL21060)
Hilfe abrufen: http://help/MSSQL_REPL21060

I also tried different values of OledbStreamThreshold.

I need to be able to replicate BLOBs in size of up to 1 GB.

I'm writing the BLOB data in chunks to the table DB_BLOBData , that isn't an article for replication and at the end copy it to the destination table MyBLOBTable which is an article. I do this, because I noticed that the transaction log on the subscriber database becomes incredibly huge (>60 GB for maybe 50 1000KB BLOBs written in blocks size of 65536 bytes) when directly updating the row using BLOB.Write(...). I think, that for each write at least the whole BLOB contents is written to the transaction log.

The replication uses Stored procedures, Update using SCALL syntax.

The code of the SP:

...
IF @.action = 1
BEGIN
UPDATE MyBLOBTable
SET DocContent = (SELECT BLOB from DB_BLOBData where GuidId = @.id)
, DocSize = (SELECT DATALENGTH(BLOB) from DB_BLOBData where GuidId = @.id)
WHERE DocId = @.id
DELETE FROM DB_BLOBData WHERE GuidId = @.id
END

IF @.action = 0
BEGIN
IF @.Offset = 0
BEGIN
INSERT DB_BLOBData( GuidId, BLOB )
VALUES ( @.id, @.value )
END
ELSE
BEGIN
UPDATE DB_BLOBData
SET BLOB.Write( @.value , @.Offset , @.Length )
WHERE GuidId = @.id
END
END

SELECT @.ModDttm = modDttm
, @.ModUser = modUser
, @.ModClient = modClient
, @.ModAppl = modAppl
FROM MyBLOBTable
WHERE DocId = @.id

RETURN 0
END

TIA,

Hannoman

Hi Hannoman,

While my ancestors are from Germany, my German is severly lacking, thus my inability to decipher the error message , but you might look at the following in BOL:

ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/rpldata9/html/11061c08-661a-4386-8996-9685cd81de05.htm

Particuarly, the section that talks about LOB's. I don't know if that answers your question, but if it doesn't hopefully it will point you in the right direction.

Scott

|||

Hello Scott

I'm using transactional peer to peer replication.

The error message means something like

The distribution agent uses OLE DB-Streaming optimization for replicating BLOB data with size larger than 16384 bytes. The threshold for the optimizationcan be defined on the command line using the OledbStreamThreshold parameter.

(Source: MSSQL_REPL, Error number: MSSQL_REPL21060)
get help: http://help/MSSQL_REPL21060

The problem is, that this kind of error deadlocks the replication. As I don't know how to handle this, I have to delete the publications and subscriptions and set them up again. In an production environment this wouldn't be a solution.

Hannoman

|||Unfortunately this is a known bug for Peer to Peer in SQL 2005, as a workaround you can try setting -CommitBatchSize to 1.

Pauses in SQL 2000

I am running SQL 2000 SP3 on a Windows 2003 server. I am
having problems with pauses in my application software. I
put a protocol analyzer on the switch and I am getting no
data error but I am getting a large amount of SQL
retries. It this normal? Has anyone seen this problem
before?
Thanks,
Jason Mobley
Technology Director
NWFL Daily NewsRetries sound like client connection issues. What I would do is try and
isolate a client machine, and see if you could load SQL client tools. Then
you could run SQL Client Network Utiltiy and compare it to SQL Server
Network Utility on the server. Sometimes the TCP/IP sockets port gets
changed from the default port of 1433, or firewalls block it. In that case,
the clients will switch from TCP/IP sockets to Named Pipes, or conceivably
keep trying to connect. I would investigat that. Even though Named Pipes
seems to be a default, I've seen a lot of clients out there default to
TCP/IP sockets, especially when going to ODBC Data Sources in control panel
and configuring a SQL Server System DSN (client configuration on the login
credential screen shows you what is being used for connections as well).
Read this article for information on Named Pipes and TCP/IP sockets
http://msdn.microsoft.com/library/d.../>
1a_7fcj.asp
****************************************
***************************
Andy S.
MCSE NT/2000, MCDBA SQL 7/2000
andymcdba1@.NOMORESPAM.yahoo.com
Please remove NOMORESPAM before replying.
Always keep your antivirus and Microsoft software
up to date with the latest definitions and product updates.
Be suspicious of every email attachment, I will never send
or post anything other than the text of a http:// link nor
post the link directly to a file for downloading.
This posting is provided "as is" with no warranties
and confers no rights.
****************************************
***************************
"Jmobley" <anonymous@.discussions.microsoft.com> wrote in message
news:6e1801c3e75a$3c080fa0$a301280a@.phx.gbl...

quote:

---

> I am running SQL 2000 SP3 on a Windows 2003 server. I am
> having problems with pauses in my application software. I
> put a protocol analyzer on the switch and I am getting no
> data error but I am getting a large amount of SQL
> retries. It this normal? Has anyone seen this problem
> before?
> Thanks,
> Jason Mobley
> Technology Director
> NWFL Daily News
>

---

Pause Log Shipping for Server Maintenace

Is there a graceful best practice to temporarily pause log shipping so that
unrelated Windows maintenance can be carried out on the servers?
Hi John
To pause Log Shipping, one can simply disable the Log Shipping jobs ie., the
Log Shipping Transaction Log Backup job on the Primary Server and the Log
Shipping Transaction Log Copy and Restore jobs on the Secondary Server.
Once the maintenance activity is completed you can enable the jobs again.
Thanks & Regards
Amer M J
MCP
"John Oberlin" wrote:

> Is there a graceful best practice to temporarily pause log shipping so that
> unrelated Windows maintenance can be carried out on the servers?

Pause Log Shipping for Server Maintenace

Is there a graceful best practice to temporarily pause log shipping so that
unrelated Windows maintenance can be carried out on the servers?Hi John
To pause Log Shipping, one can simply disable the Log Shipping jobs ie., the
Log Shipping Transaction Log Backup job on the Primary Server and the Log
Shipping Transaction Log Copy and Restore jobs on the Secondary Server.
Once the maintenance activity is completed you can enable the jobs again.
Thanks & Regards
Amer M J
MCP
"John Oberlin" wrote:
> Is there a graceful best practice to temporarily pause log shipping so that
> unrelated Windows maintenance can be carried out on the servers?

Pause Log Shipping for Server Maintenace

Is there a graceful best practice to temporarily pause log shipping so that
unrelated Windows maintenance can be carried out on the servers?Hi John
To pause Log Shipping, one can simply disable the Log Shipping jobs ie., the
Log Shipping Transaction Log Backup job on the Primary Server and the Log
Shipping Transaction Log Copy and Restore jobs on the Secondary Server.
Once the maintenance activity is completed you can enable the jobs again.
Thanks & Regards
Amer M J
MCP
"John Oberlin" wrote:

> Is there a graceful best practice to temporarily pause log shipping so tha
t
> unrelated Windows maintenance can be carried out on the servers?

patching a windows server 2003 cluster

Hi,
I have an active-active SQL 2000 Cluster running on Server 2003. Both nodes
have a vanilla 2003 OS on them. I tried upgrading each nodes to a new custom
build (hotfixes, security templates, etc) and it broke both nodes after I
patched the first one. Any suggestions?
Most likely you broke a driver for your shared storage. Check with your
hardware vendor for cluster-certified drivers for the SCSI cards or HBAs.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"jay d" <jayd@.discussions.microsoft.com> wrote in message
news:37204249-71C3-41A3-BF26-EA6463E3D662@.microsoft.com...
> Hi,
> I have an active-active SQL 2000 Cluster running on Server 2003. Both
> nodes
> have a vanilla 2003 OS on them. I tried upgrading each nodes to a new
> custom
> build (hotfixes, security templates, etc) and it broke both nodes after I
> patched the first one. Any suggestions?
|||Thanks. Any idea if there is a best practices guide for fail over cluster
maintenance?
"Geoff N. Hiten" wrote:

> Most likely you broke a driver for your shared storage. Check with your
> hardware vendor for cluster-certified drivers for the SCSI cards or HBAs.
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
> "jay d" <jayd@.discussions.microsoft.com> wrote in message
> news:37204249-71C3-41A3-BF26-EA6463E3D662@.microsoft.com...
>
>
|||Thanks. Any idea if there is a best practices guide for fail over cluster
maintenance?
Jay
"Geoff N. Hiten" wrote:

> Most likely you broke a driver for your shared storage. Check with your
> hardware vendor for cluster-certified drivers for the SCSI cards or HBAs.
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
> "jay d" <jayd@.discussions.microsoft.com> wrote in message
> news:37204249-71C3-41A3-BF26-EA6463E3D662@.microsoft.com...
>
>
|||Try these. Although a good document throughout, there are two sections
worth noting in your case, Maintenance and Troubleshooting.
SQL Server 2000 Failover Clustering
http://www.microsoft.com/technet/pro.../failclus.mspx
Maintaining a SQL Server 2000 Failover Cluster
http://www.microsoft.com/technet/pro...clus.mspx#EIAA
Troubleshooting SQL Server 2000 Failover Clusters
http://www.microsoft.com/technet/pro...clus.mspx#EHAA
Also, for "rolling upgrades," these are worth a look.
Rolling Upgrades
http://www.microsoft.com/technet/pro...ff977ef91.mspx
Restrictions on rolling upgrades
http://www.microsoft.com/technet/pro...f300fcd61.mspx
Good luck.
Sincerely,
Anthony Thomas

"jay d" <jayd@.discussions.microsoft.com> wrote in message
news:C2404898-825C-4841-B2E4-9815FF0A9378@.microsoft.com...
Thanks. Any idea if there is a best practices guide for fail over cluster
maintenance?
"Geoff N. Hiten" wrote:
[vbcol=seagreen]
> Most likely you broke a driver for your shared storage. Check with your
> hardware vendor for cluster-certified drivers for the SCSI cards or HBAs.
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
> "jay d" <jayd@.discussions.microsoft.com> wrote in message
> news:37204249-71C3-41A3-BF26-EA6463E3D662@.microsoft.com...
I
>
>

Patches and updates

Newbie question:
Does SQL Server 2000 have an updates service like that for
Windows that tells you what you have and what you need to
apply? Is there a comprehensive list of updates and
patches? I've looked thru MS website and I didn't locate
it yet.
Thanks for your time.
DionDion,
Iam not aware about any update service but you can certainly subscribe to
the newsletter.This article provides a exhaustive list of patches and
service packs
SQLSecurity Checklist
http://www.sqlsecurity.com/DesktopDefault.aspx?tabindex=3&tabid=4
--
Dinesh.
SQL Server FAQ at
http://www.tkdinesh.com
"Dion" <dreihs@.aol.com> wrote in message
news:114f01c37258$681f5c00$a501280a@.phx.gbl...
> Newbie question:
> Does SQL Server 2000 have an updates service like that for
> Windows that tells you what you have and what you need to
> apply? Is there a comprehensive list of updates and
> patches? I've looked thru MS website and I didn't locate
> it yet.
> Thanks for your time.
> Dion|||Thank you for you quick response.
How do you know where to begin? Can you just start at the
latest greatest cumulative patch (Cumulative Patch for
Microsoft SQL Server (815495)) or is there a progression?
Dion
>--Original Message--
>Dion,
>Iam not aware about any update service but you can
certainly subscribe to
>the newsletter.This article provides a exhaustive list of
patches and
>service packs
>SQLSecurity Checklist
>http://www.sqlsecurity.com/DesktopDefault.aspx?
tabindex=3&tabid=4
>--
>Dinesh.
>SQL Server FAQ at
>http://www.tkdinesh.com
>"Dion" <dreihs@.aol.com> wrote in message
>news:114f01c37258$681f5c00$a501280a@.phx.gbl...
>> Newbie question:
>> Does SQL Server 2000 have an updates service like that
for
>> Windows that tells you what you have and what you need
to
>> apply? Is there a comprehensive list of updates and
>> patches? I've looked thru MS website and I didn't locate
>> it yet.
>> Thanks for your time.
>> Dion
>
>.
>|||Try the following:
http://www.microsoft.com/technet/treeview/default.asp?
url=/technet/security/current.asp?
productid=30&servicepackid=0
Choose your product version and service pack level, then
click GO, and you will see a list of all security-related
hotfixes that apply. For instance, right now, the latest
for SQL2K with SP3 is MS03-031, which is a cumulative fix.
--m
>--Original Message--
>Dion,
>Iam not aware about any update service but you can
certainly subscribe to
>the newsletter.This article provides a exhaustive list of
patches and
>service packs
>SQLSecurity Checklist
>http://www.sqlsecurity.com/DesktopDefault.aspx?
tabindex=3&tabid=4
>--
>Dinesh.
>SQL Server FAQ at
>http://www.tkdinesh.com
>"Dion" <dreihs@.aol.com> wrote in message
>news:114f01c37258$681f5c00$a501280a@.phx.gbl...
>> Newbie question:
>> Does SQL Server 2000 have an updates service like that
for
>> Windows that tells you what you have and what you need
to
>> apply? Is there a comprehensive list of updates and
>> patches? I've looked thru MS website and I didn't locate
>> it yet.
>> Thanks for your time.
>> Dion
>
>.
>|||Dion,
That would be your call.Usually the service packs include all the patches
till then.Any bugs after that, if documented, would be having hotfixes.In
case you experience that, just search in http://support.microsoft.com and
apply the hotfix.If the bug is not documented you can call MS PSS.In any
case, make sure to read the related documentation and test it in a dev
environment before applying them in production.
--
Dinesh.
SQL Server FAQ at
http://www.tkdinesh.com
"Dion" <dreihs@.aol.com> wrote in message
news:127401c3725e$2f332880$a601280a@.phx.gbl...
> Thank you for you quick response.
> How do you know where to begin? Can you just start at the
> latest greatest cumulative patch (Cumulative Patch for
> Microsoft SQL Server (815495)) or is there a progression?
> Dion
> >--Original Message--
> >Dion,
> >
> >Iam not aware about any update service but you can
> certainly subscribe to
> >the newsletter.This article provides a exhaustive list of
> patches and
> >service packs
> >
> >SQLSecurity Checklist
> >http://www.sqlsecurity.com/DesktopDefault.aspx?
> tabindex=3&tabid=4
> >
> >--
> >Dinesh.
> >SQL Server FAQ at
> >http://www.tkdinesh.com
> >
> >"Dion" <dreihs@.aol.com> wrote in message
> >news:114f01c37258$681f5c00$a501280a@.phx.gbl...
> >> Newbie question:
> >>
> >> Does SQL Server 2000 have an updates service like that
> for
> >> Windows that tells you what you have and what you need
> to
> >> apply? Is there a comprehensive list of updates and
> >> patches? I've looked thru MS website and I didn't locate
> >> it yet.
> >>
> >> Thanks for your time.
> >> Dion
> >
> >
> >.
> >

Patch SP4 hanging

SP4 installation hangs. I used windows login to do the patch, a message
saying that it is not a valid user. I selected "retry" then used "sa". It
started hanging when "...MDAC" message disappeared.
I checked c:\winnt\sqlsp.log file. It is different from the files on the
other normal patched servers.
The last 2 lines in the file are:
End: Installpkgs(ID_INSTALLMDAC)
**** Starting open OP in write mode ****
What is the cause? How to fix it?
Hi Julia
You may want to try using the MDAC component checker to see if you have a
consistent installation of MDAC and possibly loading MDAC MDAC 2.8 SP1 if on
Windows 2000 or MDAC 2.8 SP2 if on XP/Windows 2003 before installing the
service pack.
http://www.microsoft.com/downloads/r...splayLang= en
John
"Julia" <Julia@.discussions.microsoft.com> wrote in message
news:686DFD79-5223-4A80-BF1B-99469046BF5D@.microsoft.com...
> SP4 installation hangs. I used windows login to do the patch, a message
> saying that it is not a valid user. I selected "retry" then used "sa".
> It
> started hanging when "...MDAC" message disappeared.
> I checked c:\winnt\sqlsp.log file. It is different from the files on the
> other normal patched servers.
> The last 2 lines in the file are:
> End: Installpkgs(ID_INSTALLMDAC)
> **** Starting open OP in write mode ****
> What is the cause? How to fix it?

Patch SP4 hanging

SP4 installation hangs. I used windows login to do the patch, a message
saying that it is not a valid user. I selected "retry" then used "sa". It
started hanging when "...MDAC" message disappeared.
I checked c:\winnt\sqlsp.log file. It is different from the files on the
other normal patched servers.
The last 2 lines in the file are:
End: Installpkgs(ID_INSTALLMDAC)
**** Starting open OP in write mode ****
What is the cause? How to fix it?Hi Julia
You may want to try using the MDAC component checker to see if you have a
consistent installation of MDAC and possibly loading MDAC MDAC 2.8 SP1 if on
Windows 2000 or MDAC 2.8 SP2 if on XP/Windows 2003 before installing the
service pack.
http://www.microsoft.com/downloads/results.aspx?productID=&freetext=mdac&DisplayLang=en
John
"Julia" <Julia@.discussions.microsoft.com> wrote in message
news:686DFD79-5223-4A80-BF1B-99469046BF5D@.microsoft.com...
> SP4 installation hangs. I used windows login to do the patch, a message
> saying that it is not a valid user. I selected "retry" then used "sa".
> It
> started hanging when "...MDAC" message disappeared.
> I checked c:\winnt\sqlsp.log file. It is different from the files on the
> other normal patched servers.
> The last 2 lines in the file are:
> End: Installpkgs(ID_INSTALLMDAC)
> **** Starting open OP in write mode ****
> What is the cause? How to fix it?

Patch SP4 hanging

SP4 installation hangs. I used windows login to do the patch, a message
saying that it is not a valid user. I selected "retry" then used "sa". It
started hanging when "...MDAC" message disappeared.
I checked c:\winnt\sqlsp.log file. It is different from the files on the
other normal patched servers.
The last 2 lines in the file are:
End: Installpkgs(ID_INSTALLMDAC)
**** Starting open OP in write mode ****
What is the cause? How to fix it?Hi Julia
You may want to try using the MDAC component checker to see if you have a
consistent installation of MDAC and possibly loading MDAC MDAC 2.8 SP1 if on
Windows 2000 or MDAC 2.8 SP2 if on XP/Windows 2003 before installing the
service pack.
http://www.microsoft.com/downloads/...La
ng=en
John
"Julia" <Julia@.discussions.microsoft.com> wrote in message
news:686DFD79-5223-4A80-BF1B-99469046BF5D@.microsoft.com...
> SP4 installation hangs. I used windows login to do the patch, a message
> saying that it is not a valid user. I selected "retry" then used "sa".
> It
> started hanging when "...MDAC" message disappeared.
> I checked c:\winnt\sqlsp.log file. It is different from the files on the
> other normal patched servers.
> The last 2 lines in the file are:
> End: Installpkgs(ID_INSTALLMDAC)
> **** Starting open OP in write mode ****
> What is the cause? How to fix it?

PATCH for Article 817326

I am desperately looking for the patch across the internet
cause i really need this fix basically for WINDOWS
platform listed as follows:
Msbase.jar v 2.2.0030
Mssqlserver.jar v 2.2.0030
Msutil.jar v 2.2.0030
Please advise where can i extract all these patches.
DondonYou need to contact Microsoft product support. As the article states, the
fix is only available directly through them. You won't readily find them on
the Internet because of this.
"Dondon" <dondon@.newspage.com.sg> wrote in message
news:016701c38707$3bd80700$a001280a@.phx.gbl...
> I am desperately looking for the patch across the internet
> cause i really need this fix basically for WINDOWS
> platform listed as follows:
> Msbase.jar v 2.2.0030
> Mssqlserver.jar v 2.2.0030
> Msutil.jar v 2.2.0030
> Please advise where can i extract all these patches.
> Dondon

Patch 3a

Ok filks here is a strange one. Tried installing service pack 3am on my
Windows XP
machine that is at service 2 on the OS Level. Now from what I can gather
when service pack 3a for SQL server is installed it wipes out all the driver
file locations and reinstalls a new MDAC from what I can see. But it never
gets them installed and the SQL Server becomes mute because you can never
connect to it. I've included a copy of the Log file that get's generated from
the install any one care to take a stab at this one. The following is the
SQLSTP.Log File and under that is the Error Log from the SQL Server
Directory. Any help would be great just reply to the group here
-----
10:14:35 Begin Setup
10:14:35 8.00.194
10:14:35 Mode = Normal
10:14:35 ModeType = NORMAL
10:14:38 GetDefinitionEx returned: 0, Extended: 0x0
10:14:38 ValueFTS returned: 1
10:14:38 ValuePID returned: 1
10:14:38 ValueLic returned: 0
10:14:38 System: Windows NT WorkStation
10:14:38 SQL Server ProductType: Developer Edition [0x3]
10:14:38 Begin Action: SetupInitialize
10:14:38 End Action SetupInitialize
10:14:38 Begin Action: SetupInstall
10:14:38 Reading Software\Microsoft\Windows\CurrentVersion\CommonFilesDir ...
10:14:38 CommonFilesDir=C:\Program Files\Common Files
10:14:38 Windows Directory=C:\WINDOWS\
10:14:38 Program Files=C:\Program Files\
10:14:38 TEMPDIR=C:\WINDOWS\TEMP\
10:14:38 Begin Action: SetupInstall
10:14:39 digpid size : 256
10:14:39 digpid size : 164
10:14:39 Begin Action: CheckFixedRequirements
10:14:39 Platform ID: 0xf000000
10:14:39 Version: 5.1.2600
10:14:39 File Version - C:\WINDOWS\System32\shdocvw.dll: 6.0.2800.1584
10:14:39 End Action: CheckFixedRequirements
10:14:40 Begin Action: ShowDialogs
10:14:40 Initial Dialog Mask: 0x83000f7, Disable Back=0x1
10:14:41 Begin Action ShowDialogsHlpr: 0x1
10:14:41 Begin Action: DialogShowSdWelcome
10:14:43 End Action DialogShowSdWelcome
10:14:43 Dialog 0x1 returned: 1
10:14:43 End Action ShowDialogsHlpr
10:14:43 ShowDialogsGetDialog returned: nCurrent=0x2,index=1
10:14:43 Begin Action ShowDialogsHlpr: 0x2
10:14:43 Begin Action: DialogShowSdMachineName
10:14:45 ShowDlgMachine returned: 1
10:14:45 Name = DEV2, Type = 0x1
10:14:45 Begin Action: CheckRequirements
10:14:45 Processor Architecture: x86 (Pentium)
10:14:45 Service Pack: 256
10:14:45 ComputerName: DEV2
10:14:45 User Name: <Login Name>
10:14:45 IsAllAccessAllowed returned: 1
10:14:45 OS Language: 0x409
10:14:45 End Action CheckRequirements
10:14:45 This combination of Package and Operating System allows a full
product install.
10:14:46 CreateSetupTopology(DEV2), Handle : 0x1134a50, returned : 0
10:14:46 CreateSetupTopology returned : 0, Handle : 0x1134a50
10:14:46 Topology Type : 1, Return Value : 0
10:14:46 ST_GetPhysicalNode returned : 0, PNHandle : 0x1134a78
10:14:46 PN_EnumerateEx returned : 0
10:14:46 PN_GetSQLStates returned : 0, SqlStates : 0x0
10:14:46 PN_StartScan [0x1134a78] returned : 0
10:14:46 PN_GetNext [0x1134a78] returned : 18, Handle: [0x0]
10:14:46 No more items in enumeration.
10:14:46 ReleaseSetupTopology
10:14:46 Named instance limit: 100, quota: 0
10:14:46 End Action DialogShowSdMachineName
10:14:46 begin ShowDialogsUpdateMask
10:14:46 nFullMask = 0x83000f7, nCurrent = 0x2, nDirection = 0
10:14:46 Updated Dialog Mask: 0xbf00037, Disable Back = 0x1
10:14:46 Dialog 0x2 returned: 0
10:14:46 End Action ShowDialogsHlpr
10:14:46 ShowDialogsGetDialog returned: nCurrent=0x4,index=2
10:14:46 Begin Action ShowDialogsHlpr: 0x4
10:14:46 Begin Action: DialogShowSdInstallMode
10:14:48 ShowDlgInstallMode returned: 1
10:14:48 InstallMode : 0x1
10:14:48 End Action DialogShowSdInstallMode
10:14:48 begin ShowDialogsUpdateMask
10:14:48 nFullMask = 0xbf00037, nCurrent = 0x4, nDirection = 1
10:14:48 Updated Dialog Mask: 0xbf40037, Disable Back = 0x1
10:14:48 Dialog 0x4 returned: 1
10:14:48 End Action ShowDialogsHlpr
10:14:48 ShowDialogsGetDialog returned: nCurrent=0x10,index=4
10:14:48 Begin Action ShowDialogsHlpr: 0x10
10:14:48 Begin Action: DialogShowSdRegisterUserEx
10:14:57 End Action DialogShowSdRegisterUserEx
10:14:57 Dialog 0x10 returned: 1
10:14:57 End Action ShowDialogsHlpr
10:14:57 ShowDialogsGetDialog returned: nCurrent=0x20,index=5
10:14:57 Begin Action ShowDialogsHlpr: 0x20
10:14:57 Begin Action: DialogShowSdLicense
10:15:00 End Action DialogShowSdLicense
10:15:00 Dialog 0x20 returned: 1
10:15:00 End Action ShowDialogsHlpr
10:15:00 ShowDialogsGetDialog returned: nCurrent=0x40000,index=18
10:15:00 Begin Action ShowDialogsHlpr: 0x40000
10:15:00 Begin Action: DialogShowSdCliSvr
10:15:00 DisplaySystemPreReq
10:15:02 ShowDlgClientServerSelect returned: 1
10:15:02 Type : 0x2
10:15:02 End Action DialogShowSdCliSvr
10:15:02 begin ShowDialogsUpdateMask
10:15:02 nFullMask = 0xbf40037, nCurrent = 0x40000, nDirection = 1
10:15:02 Updated Dialog Mask: 0xbfc0037, Disable Back = 0x1
10:15:02 Dialog 0x40000 returned: 1
10:15:02 End Action ShowDialogsHlpr
10:15:02 ShowDialogsGetDialog returned: nCurrent=0x80000,index=19
10:15:02 Begin Action ShowDialogsHlpr: 0x80000
10:15:02 Begin Action: DialogShowSdInstanceName
10:15:02 Begin Action: ShowDlgInstanceName
10:15:03 End Action: ShowDlgInstanceName
10:15:03 ShowDlgInstanceName returned : 1
10:15:03 InstanceName : MSSQLSERVER
10:15:03 CreateSetupTopology(DEV2), Handle : 0x1134a50, returned : 0
10:15:03 CreateSetupTopology returned : 0, Handle : 0x1134a50
10:15:03 Topology Type : 1, Return Value : 0
10:15:03 ST_GetPhysicalNode returned : 0, PNHandle : 0x1134a78
10:15:03 PN_EnumerateEx returned : 0
10:15:03 PN_GetSQLStates returned : 0, SqlStates : 0x0
10:15:03 PN_StartScan [0x1134a78] returned : 0
10:15:03 PN_GetNext [0x1134a78] returned : 18, Handle: [0x0]
10:15:03 No more items in enumeration.
10:15:03 ReleaseSetupTopology
10:15:03 End Action DialogShowSdInstanceName
10:15:03 begin ShowDialogsUpdateMask
10:15:03 nFullMask = 0xbfc0037, nCurrent = 0x80000, nDirection = 1
10:15:03 Updated Dialog Mask: 0xbfc0037, Disable Back = 0x1
10:15:03 Dialog 0x80000 returned: 1
10:15:03 End Action ShowDialogsHlpr
10:15:04 ShowDialogsGetDialog returned: nCurrent=0x100000,index 10:15:04 Begin Action ShowDialogsHlpr: 0x100000
10:15:04 Begin Action: DialogShowSdSetupType
10:15:04 Begin Action: Setup Type
10:15:22 Setup type set Typical
10:15:34 SQL program folder: C:\Program Files\Microsoft SQL Server
10:15:34 SQL data folder: C:\Program Files\Microsoft SQL Server
10:15:34 Windows system folder: C:\WINDOWS\System32\
10:15:34 Prog req: 38073, Data req: 34432, Sys req: 114225
10:15:34 Prog avail: 9393472, Data avail: 9393472, Sys avail: 9393472
10:15:34 Prog req vs. avail, 186730, 9393472
10:15:34 Data req vs. avail, 34432, 9393472
10:15:34 Sys req vs. avail, 148657, 9393472
10:15:34 DisplaySystemPreReq
10:15:34 [SetupTypeSQL]
10:15:34 szDir = C:\Program Files\Microsoft SQL Server
10:15:34 szDir = %PROGRAMFILES%\Microsoft SQL Server
10:15:34 Result = 301
10:15:34 szDataDir = C:\Program Files\Microsoft SQL Server
10:15:34 szDataDir = %PROGRAMFILES%\Microsoft SQL Server
10:15:34 End Action: Setup Type
10:15:34 Setup Type: Typical (301)
10:15:34 End Action DialogShowSdSetupType
10:15:34 begin ShowDialogsUpdateMask
10:15:34 nFullMask = 0xbfc0037, nCurrent = 0x100000, nDirection = 301
10:15:34 Updated Dialog Mask: 0xbdc0037, Disable Back = 0x1
10:15:34 Dialog 0x100000 returned: 301
10:15:34 End Action ShowDialogsHlpr
10:15:34 ShowDialogsGetDialog returned: nCurrent=0x400000,index=22
10:15:34 Begin Action ShowDialogsHlpr: 0x400000
10:15:34 Begin Action: DlgServices
10:16:15 ShowDlgServices returned: 1
10:16:15 [DlgServices]
10:16:15 Local-Domain = 61680
10:16:15 AutoStart = 15
10:16:15 SQLDomain = KALTEC
10:16:15 SQLDomainAcct = administrator
10:16:15 SQLDomainPwd
10:16:15 AgtDomain = KALTEC
10:16:15 AgtDomainAcct = administrator
10:16:15 AgtDomainPwd
10:16:15 Result = 1
10:16:15 End Action DlgServices
10:16:15 begin ShowDialogsUpdateMask
10:16:15 nFullMask = 0xbdc0037, nCurrent = 0x400000, nDirection = 1
10:16:15 Updated Dialog Mask: 0xbdc0037, Disable Back = 0x1
10:16:15 Dialog 0x400000 returned: 1
10:16:15 End Action ShowDialogsHlpr
10:16:15 ShowDialogsGetDialog returned: nCurrent=0x800000,index=23
10:16:15 Begin Action ShowDialogsHlpr: 0x800000
10:16:15 Begin Action: DlgSQLSecurity
10:16:27 ShowDlgSQLSecurity returned: 1
10:16:27 LoginMode = 2,szPwd
10:16:28 End Action DlgSQLSecurity
10:16:28 begin ShowDialogsUpdateMask
10:16:28 nFullMask = 0xbdc0037, nCurrent = 0x800000, nDirection = 1
10:16:28 Updated Dialog Mask: 0xbdc0037, Disable Back = 0x1
10:16:28 Dialog 0x800000 returned: 1
10:16:28 End Action ShowDialogsHlpr
10:16:28 ShowDialogsGetDialog returned: nCurrent=0x1000000,index=24
10:16:28 Begin Action ShowDialogsHlpr: 0x1000000
10:16:28 Begin Action: DlgCollation
10:16:28 ShowDlgCollation returned: 1
10:16:28 collation_name = SQL_Latin1_General_CP1_CI_AS,locale_name = Latin1_General,lcid = 0x409,SortId = 52,dwCompFlags = 0x30001
10:16:28 End Action DlgCollation
10:16:28 begin ShowDialogsUpdateMask
10:16:28 nFullMask = 0xbdc0037, nCurrent = 0x1000000, nDirection = 1
10:16:28 Updated Dialog Mask: 0xbdc0037, Disable Back = 0x1
10:16:28 Dialog 0x1000000 returned: 1
10:16:28 End Action ShowDialogsHlpr
10:16:28 ShowDialogsGetDialog returned: nCurrent=0x2000000,index=25
10:16:28 Begin Action ShowDialogsHlpr: 0x2000000
10:16:28 Begin Action: DlgNetwork
10:16:28 ShowDlgNetwork returned: 1
10:16:28 [DlgServerNetwork]
10:16:28 NetworkLibs = 255
10:16:28 TCPPort = 1433
10:16:28 TCPPrxy = Default
10:16:28 NMPPipeName = \\.\pipe\sql\query
10:16:28 Result = 1
10:16:28 End Action DlgNetwork
10:16:28 begin ShowDialogsUpdateMask
10:16:28 nFullMask = 0xbdc0037, nCurrent = 0x2000000, nDirection = 1
10:16:28 Updated Dialog Mask: 0xbdc0037, Disable Back = 0x1
10:16:28 Dialog 0x2000000 returned: 1
10:16:28 End Action ShowDialogsHlpr
10:16:28 ShowDialogsGetDialog returned: nCurrent=0x8000000,index=27
10:16:28 Begin Action ShowDialogsHlpr: 0x8000000
10:16:28 Begin Action: DialogShowSdStartCopy
10:16:30 End Action DialogShowSdStartCopy
10:16:30 begin ShowDialogsUpdateMask
10:16:30 nFullMask = 0xbdc0037, nCurrent = 0x8000000, nDirection = 1
10:16:30 Updated Dialog Mask: 0xbdc0037, Disable Back = 0x1
10:16:30 Dialog 0x8000000 returned: 1
10:16:30 End Action ShowDialogsHlpr
10:16:30 ShowDialogsGetDialog returned: nCurrent=0x0,index=0
10:16:30 End Action ShowDialogs
10:16:30 Begin Action ProcessBeforeDataMove:
10:16:31 DeinstallStart returned (C:\Program Files\Microsoft SQL
Server\MSSQL): 0
10:16:31 End Action ProcessBeforeDataMove:
10:16:31 Begin Action SetToolsComponentSelection:
10:16:31 End Action SetToolsComponentSelection:
10:16:31 Begin Action ProcessComponentSelection:
10:16:31 End Action ProcessComponentSelection
10:16:31 Begin Action LogSelectedComponents:
10:16:31 SQLProg
10:16:31 SQLProg\SQLServr
10:16:31 SQLProg\SQLServr\Help
10:16:31 SQLProg\SQLServr\SCMDev
10:16:31 SQLProg\SQLServr\SCMDev\SCMh
10:16:31 SQLProg\SQLServr\SCMDev\SCMX86Lb
10:16:31 SQLProg\SQLServr\SCMDev\SCMALb
10:16:31 SQLProg\SQLServr\Rs1033
10:16:31 SQLProg\SQLServr\RsIntl
10:16:31 SQLProg\SQLServr\ActiveX
10:16:31 SQLProg\SQLServr\System
10:16:31 SQLProg\UpgTools
10:16:31 SQLProg\UpgTools\UpgSys
10:16:31 SQLProg\UpgTools\ActiveX
10:16:31 SQLProg\UpgTools\Res1033
10:16:31 SQLProg\UpgTools\ResOther
10:16:31 SQLProg\UpgTools\Resld
10:16:31 SQLProg\ReplSupp
10:16:31 SQLProg\ReplSupp\ReplDat
10:16:31 SQLProg\ReplSupp\RepComm
10:16:31 SQLProg\ReplSupp\RepNoDk
10:16:31 SQLProg\ReplSupp\ActiveX
10:16:31 SQLProg\Install
10:16:31 SQLProg\System
10:16:31 SQLProg\SvrExt
10:16:31 SQLProg\SvrExt\Help
10:16:31 SQLProg\SvrExt\SvrExtRs
10:16:31 SQLProg\SvrExt\ResIntl
10:16:31 SQLProg\Dat
10:16:31 SQLProg\DatSmpl
10:16:31 SQLProg\BaseSys
10:16:31 SQLProg\BaseBinn
10:16:31 SQLProg\BaseInst
10:16:31 SQLProg\Symbols
10:16:31 SQLProg\Symbols\EXE
10:16:31 SQLProg\Symbols\DLL
10:16:31 SQLProg\Perfmon
10:16:31 SQLProg\Perfmon\System
10:16:31 SQLProg\Root
10:16:31 MgtTool
10:16:31 MgtTool\SEM
10:16:31 MgtTool\SEM\HTML
10:16:31 MgtTool\SEM\MSD98
10:16:31 MgtTool\SEM\MSD98SYS
10:16:31 MgtTool\SEM\MSD98Res
10:16:31 MgtTool\SEM\MSD98Hlp
10:16:31 MgtTool\SEM\Help
10:16:31 MgtTool\SEM\Res1033
10:16:31 MgtTool\SEM\ResIntl
10:16:31 MgtTool\SEM\MSD98RsI
10:16:31 MgtTool\SEM\ActiveX
10:16:31 MgtTool\SEM\ActiveX\Res1033
10:16:31 MgtTool\SEM\ActiveX\ResIntl
10:16:31 MgtTool\SEM\Scripts
10:16:31 MgtTool\SEM\OLEDB
10:16:31 MgtTool\SEM\OLEDB\Res1033
10:16:31 MgtTool\SEM\OLEDB\ResIntl
10:16:31 MgtTool\Profiler
10:16:31 MgtTool\Profiler\Help
10:16:31 MgtTool\Profiler\Res1033
10:16:31 MgtTool\Profiler\ResIntl
10:16:31 MgtTool\Qryanlz
10:16:31 MgtTool\Qryanlz\Help
10:16:31 MgtTool\Qryanlz\Res1033
10:16:31 MgtTool\Qryanlz\ResIntl
10:16:31 MgtTool\DTCCLi
10:16:31 MgtTool\Wzcnflct
10:16:31 MgtTool\Wzcnflct\WzcnHlp
10:16:31 MgtTool\Wzcnflct\Wzcn1033
10:16:31 MgtTool\Wzcnflct\WzcnOthr
10:16:31 MgtTool\Wzcnflct\WzcnCmn
10:16:31 MgtTool\UtilSys
10:16:31 MgtTool\UtilBinn
10:16:31 Connect
10:16:31 Connect\ConnSys
10:16:31 Books
10:16:31 Books\Bookso
10:16:31 Books\Bookso\Utils
10:16:31 DevTools
10:16:31 DevTools\Dbg Int
10:16:31 DevTools\Dbg Int\Dbg Int Common
10:16:31 DevTools\Dbg Int\EXE
10:16:31 CoreRepl
10:16:31 CoreRepl\Res1033
10:16:31 CoreRepl\ResIntl
10:16:31 Core
10:16:31 Core\Res1033
10:16:31 Core\ResOther
10:16:31 Repostry
10:16:31 Repostry\RepstSys
10:16:31 Repostry\Res1033
10:16:31 Repostry\ResIntl
10:16:31 CoreMisc
10:16:31 CoreMisc\ActiveX
10:16:31 CoreMisc\ActiveX\Res1033
10:16:31 CoreMisc\ActiveX\ResIntl
10:16:31 CoreMisc\Res1033
10:16:31 Monarch
10:16:31 Monarch\Monr1033
10:16:31 Monarch\MonrIntl
10:16:31 Jet
10:16:31 CoreInst
10:16:31 CoreCOM
10:16:31 CoreCOM\Res1033
10:16:31 CoreCOM\ResIntl
10:16:31 CoreTool
10:16:31 CoreTool\Res1033
10:16:31 CoreTool\ResOther
10:16:31 DBLibCli
10:16:31 SFExt
10:16:31 SFExt\ActiveX
10:16:31 SFExt\ActiveX\Res1033
10:16:31 SFExt\ActiveX\ResIntl
10:16:31 SFExt\Res1033
10:16:31 SFExt\ResIntl
10:16:31 Trace
10:16:31 Trace\Res1033
10:16:31 Trace\ResOther
10:16:31 MiscCore
10:16:31 MC
10:16:31 MC\MC1033
10:16:31 MC\MCIntl
10:16:31 MC\Help
10:16:31 SQLMgr
10:16:31 SQLMgr\Res1033
10:16:31 SQLMgr\ResIntl
10:16:31 SvrTool
10:16:31 SvrTool\Res1033
10:16:31 SvrTool\ResIntl
10:16:31 DTSUI
10:16:31 DTSUI\Res1033
10:16:31 DTSUI\ResIntl
10:16:31 MSOlap
10:16:32 MSOlap\Res1033
10:16:32 MSOlap\ResIntl
10:16:32 ATL
10:16:32 ATL\winnt
10:16:32 ATL\win9x
10:16:32 MFC42U
10:16:32 VC
10:16:32 VB
10:16:32 OCX1
10:16:32 SQLAdHlp
10:16:32 SQLAdHlp\Res1033
10:16:32 SQLAdHlp\ResOther
10:16:32 {E07FDDBE-5A21-11d2-9DAD-00C04F79D434}
10:16:32 {E07FDDC7-5A21-11d2-9DAD-00C04F79D434}
10:16:32 {E07FDDC0-5A21-11d2-9DAD-00C04F79D434}
10:16:32 {E07FDDBF-5A21-11d2-9DAD-00C04F79D434}
10:16:32 End Action LogSelectedComponents
10:16:32 Begin Action InstallPkgs:
10:16:32 Begin Action: Locked Connectivity Files Check
10:16:40 ConnectivityLocked returned: 0
10:16:40 The operation completed successfully.
10:16:40 End Action: Locked Connectivity Files Check
10:16:40 Setup is installing Microsoft Data Access Components (MDAC) ...
10:16:40 \\DEV1\DVD\ENGLISH\SQL2000\DEV\x86\Other\sqlredis.exe /q:a
/C:"setupre.exe WARN=1 -s -SMS"
10:17:43 ExitCode: 0
10:17:43 Setup is installing Microsoft Distributed Transaction Coordinator
(MSDTC) ...
10:17:43 C:\WINDOWS\TEMP\SqlSetup\Bin\cldtcstp.exe -SupportDir
"C:\WINDOWS\TEMP\SqlSetup\Bin" -DTCPkg
"\\DEV1\DVD\ENGLISH\SQL2000\DEV\x86\Other\dtcsetup.exe" -LogFile
"C:\WINDOWS\sqlstp.log"
10:17:45 Process Exit Code: (0)
10:17:45 /Q:A /T:C:\WINDOWS\TEMP\ixp001.tmp
10:17:45 Setup is installing HTML Help ...
10:17:48 HTML Help installer exit code: 0
10:18:15 End Action InstallPkgs
10:18:15 Begin Action MoveFileData:
10:18:15 Enabled SELFREGISTERBATCH
10:18:15 Enabled CORECOMPONENTHANDLING
10:21:34 Begin Action: MoveFileDataSpecial
10:21:37 End Action: MoveFileDataSpecial
10:21:37 End Action MoveFileData
10:21:37 Begin Action ProcessAfterDataMove:
10:21:37 \\DEV1\DVD\ENGLISH\SQL2000\DEV\x86\Binn\hhcol.exe C:\Program
Files\Microsoft SQL Server\80\Tools\Books
10:21:42 End Action ProcessAfterDataMove
10:21:42 Begin Action BuildServer:
10:21:42 C:\WINDOWS\TEMP\SqlSetup\Bin\scm.exe -Silent 1 -Action 5 -ExePath
"C:\Program Files\Microsoft SQL Server\MSSQL\binn\sqlservr.exe" -Service
"MSSQLSERVER"
10:21:43 Process Exit Code: (0)
10:21:43 Begin Action: CreateRegistrySetSQL
10:21:43 End Action: CreateRegistrySetSQL
10:21:43 Begin Action: RegWriteSetupEntry
10:21:43 End Action: RegWriteSetupEntry
10:21:43 Begin Action: CreateSer
10:21:43 End Action: CreateSer
10:21:43 Begin Action: SkuIt
10:21:44 End Action: SkuIt
10:21:45 SetFileSecuritySQLAndAdmin for C:\Program Files\Microsoft SQL
Server\MSSQL returned: 0, 0
10:21:45 SetRegSecuritySQLAndAdmin for
Software\Microsoft\MSSQLServer\MSSQLServer returned: 0, 0
10:21:45 Begin Action: UpdateSystemPath
10:21:45 Path successfully updated.
10:21:45 C:\oracle\ora92\bin;C:\Program
Files\Oracle\jre\1.3.1\bin;C:\Program
Files\Oracle\jre\1.1.8\bin;C:\Perl\bin\;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;C:\OCM;C:\Program
Files\Microsoft SQL Server\80\Tools\Binn\;C:\Program Files\Common
Files\Autodesk Shared\;C:\Program Files\proe2001\bin;C:\Program Files\Common
Files\Roxio Shared\DLLShared;C:\Program Files\UltraEdit;C:\Program
Files\Rouzer File Printer\;C:\Program Files\Executive Software\Diskeeper\
10:21:45 End Action: UpdateSystemPath
10:21:46 Grant Right for KALTEC\administrator returned : 1, 0
10:21:46 Grant Right for KALTEC\administrator returned : 1, 0
10:21:46 Grant Right for KALTEC\administrator returned : 1, 0
10:21:47 Grant Right for KALTEC\administrator returned : 1, 0
10:21:47 Grant Right for KALTEC\administrator returned : 1, 0
10:21:48 C:\Program Files\Microsoft SQL Server\80\Tools\Binn\cnfgsvr.exe -F
"C:\WINDOWS\sqlstp.log" -I MSSQLSERVER -V 1 -M 0 -Q
"SQL_Latin1_General_CP1_CI_AS" -H 66300 -U sa -P
###############################################################################
Starting Service ...
SQL_Latin1_General_CP1_CI_AS
-m -Q -T4022 -T3659
Connecting to Server ...
driver={sql server};server=DEV2;UID=sa;PWD=;database=master
[Microsoft][ODBC Driver Manager] Data source name not found and no default
driver specified
driver={sql server};server=DEV2;UID=sa;PWD=;database=master
[Microsoft][ODBC Driver Manager] Data source name not found and no default
driver specified
driver={sql server};server=DEV2;UID=sa;PWD=;database=master
[Microsoft][ODBC Driver Manager] Data source name not found and no default
driver specified
SQL Server configuration failed.
###############################################################################
10:22:26 Process Exit Code: (-1)
10:22:35 Setup failed to configure the server. Refer to the server error
logs and C:\WINDOWS\sqlstp.log for more information.
10:22:37 Action CleanUpInstall:
10:22:37 C:\WINDOWS\TEMP\SqlSetup\Bin\scm.exe -Silent 1 -Action 4 -Service
SQLSERVERAGENT
10:22:38 Process Exit Code: (1060) The specified service does not exist as
an installed service.
10:22:38 C:\WINDOWS\TEMP\SqlSetup\Bin\scm.exe -Silent 1 -Action 4 -Service
MSSQLSERVER
10:22:38 Process Exit Code: (0)
10:22:38 StatsGenerate returned: 2
10:22:38 StatsGenerate (0x0,0x1,0xf000000,0x100,1033,303,0x0,0x1,0,0,0
10:22:38 StatsGenerate -1,<Login Name>)
10:22:38 Installation Failed.
-----
2004-10-28 10:21:51.33 server Microsoft SQL Server 2000 - 8.00.194
(Intel X86)
Aug 6 2000 00:57:48
Copyright (c) 1988-2000 Microsoft Corporation
Developer Edition on Windows NT 5.1 (Build 2600: Service Pack 1)
2004-10-28 10:21:51.37 server Copyright (C) 1988-2000 Microsoft
Corporation.
2004-10-28 10:21:51.37 server All rights reserved.
2004-10-28 10:21:51.37 server Server Process ID is 3460.
2004-10-28 10:21:51.37 server Logging SQL Server messages in file
'C:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
2004-10-28 10:21:51.41 server SQL Server is starting at priority class
'normal'(1 CPU detected).
2004-10-28 10:21:51.78 server SQL Server configured for thread mode
processing.
2004-10-28 10:21:51.82 server Using dynamic lock allocation. [2500] Lock
Blocks, [5000] Lock Owner Blocks.
2004-10-28 10:21:51.87 server Attempting to initialize Distributed
Transaction Coordinator.
2004-10-28 10:21:56.01 spid3 Warning ******************
2004-10-28 10:21:56.01 spid3 SQL Server started in single user mode.
Updates allowed to system catalogs.
2004-10-28 10:21:56.04 spid3 Starting up database 'master'.
2004-10-28 10:21:57.41 spid3 Server name is 'DEV2'.
2004-10-28 10:21:57.42 server Using 'SSNETLIB.DLL' version '8.0.311'.
2004-10-28 10:21:57.42 spid5 Starting up database 'model'.
2004-10-28 10:21:57.42 spid7 Starting up database 'msdb'.
2004-10-28 10:21:57.42 spid8 Starting up database 'pubs'.
2004-10-28 10:21:57.42 spid9 Starting up database 'Northwind'.
2004-10-28 10:21:58.95 spid5 Clearing tempdb database.
2004-10-28 10:22:00.94 server SQL server listening on 10.10.1.33: 1433.
2004-10-28 10:22:00.94 server SQL server listening on 127.0.0.1: 1433.
2004-10-28 10:22:02.26 spid5 Starting up database 'tempdb'.
2004-10-28 10:22:02.41 server SQL server listening on TCP, Shared Memory,
Named Pipes.
2004-10-28 10:22:02.41 server SQL Server is ready for client connections
2004-10-28 10:22:02.61 spid3 Recovery complete.
2004-10-28 10:22:02.64 spid3 Warning: override, autoexec procedures
skipped.
2004-10-28 10:22:12.92 spid3 SQL Server is terminating due to 'stop'
request from Service Control Manager.Turn off the Windows Firewall or open up UDP 1434 and TCP 1433 on it.
"Jim B." <Jim B.@.discussions.microsoft.com> wrote in message
news:3AFED5B5-06E9-47A4-8A7E-A68E1EEC24C4@.microsoft.com...
> Ok filks here is a strange one. Tried installing service pack 3am on my
> Windows XP
> machine that is at service 2 on the OS Level. Now from what I can gather
> when service pack 3a for SQL server is installed it wipes out all the
driver
> file locations and reinstalls a new MDAC from what I can see. But it never
> gets them installed and the SQL Server becomes mute because you can never
> connect to it. I've included a copy of the Log file that get's generated
from
> the install any one care to take a stab at this one. The following is the
> SQLSTP.Log File and under that is the Error Log from the SQL Server
> Directory. Any help would be great just reply to the group here.
> ----
--
> 10:14:35 Begin Setup
> 10:14:35 8.00.194
> 10:14:35 Mode = Normal
> 10:14:35 ModeType = NORMAL
> 10:14:38 GetDefinitionEx returned: 0, Extended: 0x0
> 10:14:38 ValueFTS returned: 1
> 10:14:38 ValuePID returned: 1
> 10:14:38 ValueLic returned: 0
> 10:14:38 System: Windows NT WorkStation
> 10:14:38 SQL Server ProductType: Developer Edition [0x3]
> 10:14:38 Begin Action: SetupInitialize
> 10:14:38 End Action SetupInitialize
> 10:14:38 Begin Action: SetupInstall
> 10:14:38 Reading Software\Microsoft\Windows\CurrentVersion\CommonFilesDir
...
> 10:14:38 CommonFilesDir=C:\Program Files\Common Files
> 10:14:38 Windows Directory=C:\WINDOWS\
> 10:14:38 Program Files=C:\Program Files\
> 10:14:38 TEMPDIR=C:\WINDOWS\TEMP\
> 10:14:38 Begin Action: SetupInstall
> 10:14:39 digpid size : 256
> 10:14:39 digpid size : 164
> 10:14:39 Begin Action: CheckFixedRequirements
> 10:14:39 Platform ID: 0xf000000
> 10:14:39 Version: 5.1.2600
> 10:14:39 File Version - C:\WINDOWS\System32\shdocvw.dll: 6.0.2800.1584
> 10:14:39 End Action: CheckFixedRequirements
> 10:14:40 Begin Action: ShowDialogs
> 10:14:40 Initial Dialog Mask: 0x83000f7, Disable Back=0x1
> 10:14:41 Begin Action ShowDialogsHlpr: 0x1
> 10:14:41 Begin Action: DialogShowSdWelcome
> 10:14:43 End Action DialogShowSdWelcome
> 10:14:43 Dialog 0x1 returned: 1
> 10:14:43 End Action ShowDialogsHlpr
> 10:14:43 ShowDialogsGetDialog returned: nCurrent=0x2,index=1
> 10:14:43 Begin Action ShowDialogsHlpr: 0x2
> 10:14:43 Begin Action: DialogShowSdMachineName
> 10:14:45 ShowDlgMachine returned: 1
> 10:14:45 Name = DEV2, Type = 0x1
> 10:14:45 Begin Action: CheckRequirements
> 10:14:45 Processor Architecture: x86 (Pentium)
> 10:14:45 Service Pack: 256
> 10:14:45 ComputerName: DEV2
> 10:14:45 User Name: <Login Name>
> 10:14:45 IsAllAccessAllowed returned: 1
> 10:14:45 OS Language: 0x409
> 10:14:45 End Action CheckRequirements
> 10:14:45 This combination of Package and Operating System allows a full
> product install.
> 10:14:46 CreateSetupTopology(DEV2), Handle : 0x1134a50, returned : 0
> 10:14:46 CreateSetupTopology returned : 0, Handle : 0x1134a50
> 10:14:46 Topology Type : 1, Return Value : 0
> 10:14:46 ST_GetPhysicalNode returned : 0, PNHandle : 0x1134a78
> 10:14:46 PN_EnumerateEx returned : 0
> 10:14:46 PN_GetSQLStates returned : 0, SqlStates : 0x0
> 10:14:46 PN_StartScan [0x1134a78] returned : 0
> 10:14:46 PN_GetNext [0x1134a78] returned : 18, Handle: [0x0]
> 10:14:46 No more items in enumeration.
> 10:14:46 ReleaseSetupTopology
> 10:14:46 Named instance limit: 100, quota: 0
> 10:14:46 End Action DialogShowSdMachineName
> 10:14:46 begin ShowDialogsUpdateMask
> 10:14:46 nFullMask = 0x83000f7, nCurrent = 0x2, nDirection = 0
> 10:14:46 Updated Dialog Mask: 0xbf00037, Disable Back = 0x1
> 10:14:46 Dialog 0x2 returned: 0
> 10:14:46 End Action ShowDialogsHlpr
> 10:14:46 ShowDialogsGetDialog returned: nCurrent=0x4,index=2
> 10:14:46 Begin Action ShowDialogsHlpr: 0x4
> 10:14:46 Begin Action: DialogShowSdInstallMode
> 10:14:48 ShowDlgInstallMode returned: 1
> 10:14:48 InstallMode : 0x1
> 10:14:48 End Action DialogShowSdInstallMode
> 10:14:48 begin ShowDialogsUpdateMask
> 10:14:48 nFullMask = 0xbf00037, nCurrent = 0x4, nDirection = 1
> 10:14:48 Updated Dialog Mask: 0xbf40037, Disable Back = 0x1
> 10:14:48 Dialog 0x4 returned: 1
> 10:14:48 End Action ShowDialogsHlpr
> 10:14:48 ShowDialogsGetDialog returned: nCurrent=0x10,index=4
> 10:14:48 Begin Action ShowDialogsHlpr: 0x10
> 10:14:48 Begin Action: DialogShowSdRegisterUserEx
> 10:14:57 End Action DialogShowSdRegisterUserEx
> 10:14:57 Dialog 0x10 returned: 1
> 10:14:57 End Action ShowDialogsHlpr
> 10:14:57 ShowDialogsGetDialog returned: nCurrent=0x20,index=5
> 10:14:57 Begin Action ShowDialogsHlpr: 0x20
> 10:14:57 Begin Action: DialogShowSdLicense
> 10:15:00 End Action DialogShowSdLicense
> 10:15:00 Dialog 0x20 returned: 1
> 10:15:00 End Action ShowDialogsHlpr
> 10:15:00 ShowDialogsGetDialog returned: nCurrent=0x40000,index=18
> 10:15:00 Begin Action ShowDialogsHlpr: 0x40000
> 10:15:00 Begin Action: DialogShowSdCliSvr
> 10:15:00 DisplaySystemPreReq
> 10:15:02 ShowDlgClientServerSelect returned: 1
> 10:15:02 Type : 0x2
> 10:15:02 End Action DialogShowSdCliSvr
> 10:15:02 begin ShowDialogsUpdateMask
> 10:15:02 nFullMask = 0xbf40037, nCurrent = 0x40000, nDirection = 1
> 10:15:02 Updated Dialog Mask: 0xbfc0037, Disable Back = 0x1
> 10:15:02 Dialog 0x40000 returned: 1
> 10:15:02 End Action ShowDialogsHlpr
> 10:15:02 ShowDialogsGetDialog returned: nCurrent=0x80000,index=19
> 10:15:02 Begin Action ShowDialogsHlpr: 0x80000
> 10:15:02 Begin Action: DialogShowSdInstanceName
> 10:15:02 Begin Action: ShowDlgInstanceName
> 10:15:03 End Action: ShowDlgInstanceName
> 10:15:03 ShowDlgInstanceName returned : 1
> 10:15:03 InstanceName : MSSQLSERVER
> 10:15:03 CreateSetupTopology(DEV2), Handle : 0x1134a50, returned : 0
> 10:15:03 CreateSetupTopology returned : 0, Handle : 0x1134a50
> 10:15:03 Topology Type : 1, Return Value : 0
> 10:15:03 ST_GetPhysicalNode returned : 0, PNHandle : 0x1134a78
> 10:15:03 PN_EnumerateEx returned : 0
> 10:15:03 PN_GetSQLStates returned : 0, SqlStates : 0x0
> 10:15:03 PN_StartScan [0x1134a78] returned : 0
> 10:15:03 PN_GetNext [0x1134a78] returned : 18, Handle: [0x0]
> 10:15:03 No more items in enumeration.
> 10:15:03 ReleaseSetupTopology
> 10:15:03 End Action DialogShowSdInstanceName
> 10:15:03 begin ShowDialogsUpdateMask
> 10:15:03 nFullMask = 0xbfc0037, nCurrent = 0x80000, nDirection = 1
> 10:15:03 Updated Dialog Mask: 0xbfc0037, Disable Back = 0x1
> 10:15:03 Dialog 0x80000 returned: 1
> 10:15:03 End Action ShowDialogsHlpr
> 10:15:04 ShowDialogsGetDialog returned: nCurrent=0x100000,index > 10:15:04 Begin Action ShowDialogsHlpr: 0x100000
> 10:15:04 Begin Action: DialogShowSdSetupType
> 10:15:04 Begin Action: Setup Type
> 10:15:22 Setup type set Typical
> 10:15:34 SQL program folder: C:\Program Files\Microsoft SQL Server
> 10:15:34 SQL data folder: C:\Program Files\Microsoft SQL Server
> 10:15:34 Windows system folder: C:\WINDOWS\System32\
> 10:15:34 Prog req: 38073, Data req: 34432, Sys req: 114225
> 10:15:34 Prog avail: 9393472, Data avail: 9393472, Sys avail: 9393472
> 10:15:34 Prog req vs. avail, 186730, 9393472
> 10:15:34 Data req vs. avail, 34432, 9393472
> 10:15:34 Sys req vs. avail, 148657, 9393472
> 10:15:34 DisplaySystemPreReq
> 10:15:34 [SetupTypeSQL]
> 10:15:34 szDir = C:\Program Files\Microsoft SQL Server
> 10:15:34 szDir = %PROGRAMFILES%\Microsoft SQL Server
> 10:15:34 Result = 301
> 10:15:34 szDataDir = C:\Program Files\Microsoft SQL Server
> 10:15:34 szDataDir = %PROGRAMFILES%\Microsoft SQL Server
> 10:15:34 End Action: Setup Type
> 10:15:34 Setup Type: Typical (301)
> 10:15:34 End Action DialogShowSdSetupType
> 10:15:34 begin ShowDialogsUpdateMask
> 10:15:34 nFullMask = 0xbfc0037, nCurrent = 0x100000, nDirection = 301
> 10:15:34 Updated Dialog Mask: 0xbdc0037, Disable Back = 0x1
> 10:15:34 Dialog 0x100000 returned: 301
> 10:15:34 End Action ShowDialogsHlpr
> 10:15:34 ShowDialogsGetDialog returned: nCurrent=0x400000,index=22
> 10:15:34 Begin Action ShowDialogsHlpr: 0x400000
> 10:15:34 Begin Action: DlgServices
> 10:16:15 ShowDlgServices returned: 1
> 10:16:15 [DlgServices]
> 10:16:15 Local-Domain = 61680
> 10:16:15 AutoStart = 15
> 10:16:15 SQLDomain = KALTEC
> 10:16:15 SQLDomainAcct = administrator
> 10:16:15 SQLDomainPwd
> 10:16:15 AgtDomain = KALTEC
> 10:16:15 AgtDomainAcct = administrator
> 10:16:15 AgtDomainPwd
> 10:16:15 Result = 1
> 10:16:15 End Action DlgServices
> 10:16:15 begin ShowDialogsUpdateMask
> 10:16:15 nFullMask = 0xbdc0037, nCurrent = 0x400000, nDirection = 1
> 10:16:15 Updated Dialog Mask: 0xbdc0037, Disable Back = 0x1
> 10:16:15 Dialog 0x400000 returned: 1
> 10:16:15 End Action ShowDialogsHlpr
> 10:16:15 ShowDialogsGetDialog returned: nCurrent=0x800000,index=23
> 10:16:15 Begin Action ShowDialogsHlpr: 0x800000
> 10:16:15 Begin Action: DlgSQLSecurity
> 10:16:27 ShowDlgSQLSecurity returned: 1
> 10:16:27 LoginMode = 2,szPwd
> 10:16:28 End Action DlgSQLSecurity
> 10:16:28 begin ShowDialogsUpdateMask
> 10:16:28 nFullMask = 0xbdc0037, nCurrent = 0x800000, nDirection = 1
> 10:16:28 Updated Dialog Mask: 0xbdc0037, Disable Back = 0x1
> 10:16:28 Dialog 0x800000 returned: 1
> 10:16:28 End Action ShowDialogsHlpr
> 10:16:28 ShowDialogsGetDialog returned: nCurrent=0x1000000,index=24
> 10:16:28 Begin Action ShowDialogsHlpr: 0x1000000
> 10:16:28 Begin Action: DlgCollation
> 10:16:28 ShowDlgCollation returned: 1
> 10:16:28 collation_name = SQL_Latin1_General_CP1_CI_AS,locale_name => Latin1_General,lcid = 0x409,SortId = 52,dwCompFlags = 0x30001
> 10:16:28 End Action DlgCollation
> 10:16:28 begin ShowDialogsUpdateMask
> 10:16:28 nFullMask = 0xbdc0037, nCurrent = 0x1000000, nDirection = 1
> 10:16:28 Updated Dialog Mask: 0xbdc0037, Disable Back = 0x1
> 10:16:28 Dialog 0x1000000 returned: 1
> 10:16:28 End Action ShowDialogsHlpr
> 10:16:28 ShowDialogsGetDialog returned: nCurrent=0x2000000,index=25
> 10:16:28 Begin Action ShowDialogsHlpr: 0x2000000
> 10:16:28 Begin Action: DlgNetwork
> 10:16:28 ShowDlgNetwork returned: 1
> 10:16:28 [DlgServerNetwork]
> 10:16:28 NetworkLibs = 255
> 10:16:28 TCPPort = 1433
> 10:16:28 TCPPrxy = Default
> 10:16:28 NMPPipeName = \\.\pipe\sql\query
> 10:16:28 Result = 1
> 10:16:28 End Action DlgNetwork
> 10:16:28 begin ShowDialogsUpdateMask
> 10:16:28 nFullMask = 0xbdc0037, nCurrent = 0x2000000, nDirection = 1
> 10:16:28 Updated Dialog Mask: 0xbdc0037, Disable Back = 0x1
> 10:16:28 Dialog 0x2000000 returned: 1
> 10:16:28 End Action ShowDialogsHlpr
> 10:16:28 ShowDialogsGetDialog returned: nCurrent=0x8000000,index=27
> 10:16:28 Begin Action ShowDialogsHlpr: 0x8000000
> 10:16:28 Begin Action: DialogShowSdStartCopy
> 10:16:30 End Action DialogShowSdStartCopy
> 10:16:30 begin ShowDialogsUpdateMask
> 10:16:30 nFullMask = 0xbdc0037, nCurrent = 0x8000000, nDirection = 1
> 10:16:30 Updated Dialog Mask: 0xbdc0037, Disable Back = 0x1
> 10:16:30 Dialog 0x8000000 returned: 1
> 10:16:30 End Action ShowDialogsHlpr
> 10:16:30 ShowDialogsGetDialog returned: nCurrent=0x0,index=0
> 10:16:30 End Action ShowDialogs
> 10:16:30 Begin Action ProcessBeforeDataMove:
> 10:16:31 DeinstallStart returned (C:\Program Files\Microsoft SQL
> Server\MSSQL): 0
> 10:16:31 End Action ProcessBeforeDataMove:
> 10:16:31 Begin Action SetToolsComponentSelection:
> 10:16:31 End Action SetToolsComponentSelection:
> 10:16:31 Begin Action ProcessComponentSelection:
> 10:16:31 End Action ProcessComponentSelection
> 10:16:31 Begin Action LogSelectedComponents:
> 10:16:31 SQLProg
> 10:16:31 SQLProg\SQLServr
> 10:16:31 SQLProg\SQLServr\Help
> 10:16:31 SQLProg\SQLServr\SCMDev
> 10:16:31 SQLProg\SQLServr\SCMDev\SCMh
> 10:16:31 SQLProg\SQLServr\SCMDev\SCMX86Lb
> 10:16:31 SQLProg\SQLServr\SCMDev\SCMALb
> 10:16:31 SQLProg\SQLServr\Rs1033
> 10:16:31 SQLProg\SQLServr\RsIntl
> 10:16:31 SQLProg\SQLServr\ActiveX
> 10:16:31 SQLProg\SQLServr\System
> 10:16:31 SQLProg\UpgTools
> 10:16:31 SQLProg\UpgTools\UpgSys
> 10:16:31 SQLProg\UpgTools\ActiveX
> 10:16:31 SQLProg\UpgTools\Res1033
> 10:16:31 SQLProg\UpgTools\ResOther
> 10:16:31 SQLProg\UpgTools\Resld
> 10:16:31 SQLProg\ReplSupp
> 10:16:31 SQLProg\ReplSupp\ReplDat
> 10:16:31 SQLProg\ReplSupp\RepComm
> 10:16:31 SQLProg\ReplSupp\RepNoDk
> 10:16:31 SQLProg\ReplSupp\ActiveX
> 10:16:31 SQLProg\Install
> 10:16:31 SQLProg\System
> 10:16:31 SQLProg\SvrExt
> 10:16:31 SQLProg\SvrExt\Help
> 10:16:31 SQLProg\SvrExt\SvrExtRs
> 10:16:31 SQLProg\SvrExt\ResIntl
> 10:16:31 SQLProg\Dat
> 10:16:31 SQLProg\DatSmpl
> 10:16:31 SQLProg\BaseSys
> 10:16:31 SQLProg\BaseBinn
> 10:16:31 SQLProg\BaseInst
> 10:16:31 SQLProg\Symbols
> 10:16:31 SQLProg\Symbols\EXE
> 10:16:31 SQLProg\Symbols\DLL
> 10:16:31 SQLProg\Perfmon
> 10:16:31 SQLProg\Perfmon\System
> 10:16:31 SQLProg\Root
> 10:16:31 MgtTool
> 10:16:31 MgtTool\SEM
> 10:16:31 MgtTool\SEM\HTML
> 10:16:31 MgtTool\SEM\MSD98
> 10:16:31 MgtTool\SEM\MSD98SYS
> 10:16:31 MgtTool\SEM\MSD98Res
> 10:16:31 MgtTool\SEM\MSD98Hlp
> 10:16:31 MgtTool\SEM\Help
> 10:16:31 MgtTool\SEM\Res1033
> 10:16:31 MgtTool\SEM\ResIntl
> 10:16:31 MgtTool\SEM\MSD98RsI
> 10:16:31 MgtTool\SEM\ActiveX
> 10:16:31 MgtTool\SEM\ActiveX\Res1033
> 10:16:31 MgtTool\SEM\ActiveX\ResIntl
> 10:16:31 MgtTool\SEM\Scripts
> 10:16:31 MgtTool\SEM\OLEDB
> 10:16:31 MgtTool\SEM\OLEDB\Res1033
> 10:16:31 MgtTool\SEM\OLEDB\ResIntl
> 10:16:31 MgtTool\Profiler
> 10:16:31 MgtTool\Profiler\Help
> 10:16:31 MgtTool\Profiler\Res1033
> 10:16:31 MgtTool\Profiler\ResIntl
> 10:16:31 MgtTool\Qryanlz
> 10:16:31 MgtTool\Qryanlz\Help
> 10:16:31 MgtTool\Qryanlz\Res1033
> 10:16:31 MgtTool\Qryanlz\ResIntl
> 10:16:31 MgtTool\DTCCLi
> 10:16:31 MgtTool\Wzcnflct
> 10:16:31 MgtTool\Wzcnflct\WzcnHlp
> 10:16:31 MgtTool\Wzcnflct\Wzcn1033
> 10:16:31 MgtTool\Wzcnflct\WzcnOthr
> 10:16:31 MgtTool\Wzcnflct\WzcnCmn
> 10:16:31 MgtTool\UtilSys
> 10:16:31 MgtTool\UtilBinn
> 10:16:31 Connect
> 10:16:31 Connect\ConnSys
> 10:16:31 Books
> 10:16:31 Books\Bookso
> 10:16:31 Books\Bookso\Utils
> 10:16:31 DevTools
> 10:16:31 DevTools\Dbg Int
> 10:16:31 DevTools\Dbg Int\Dbg Int Common
> 10:16:31 DevTools\Dbg Int\EXE
> 10:16:31 CoreRepl
> 10:16:31 CoreRepl\Res1033
> 10:16:31 CoreRepl\ResIntl
> 10:16:31 Core
> 10:16:31 Core\Res1033
> 10:16:31 Core\ResOther
> 10:16:31 Repostry
> 10:16:31 Repostry\RepstSys
> 10:16:31 Repostry\Res1033
> 10:16:31 Repostry\ResIntl
> 10:16:31 CoreMisc
> 10:16:31 CoreMisc\ActiveX
> 10:16:31 CoreMisc\ActiveX\Res1033
> 10:16:31 CoreMisc\ActiveX\ResIntl
> 10:16:31 CoreMisc\Res1033
> 10:16:31 Monarch
> 10:16:31 Monarch\Monr1033
> 10:16:31 Monarch\MonrIntl
> 10:16:31 Jet
> 10:16:31 CoreInst
> 10:16:31 CoreCOM
> 10:16:31 CoreCOM\Res1033
> 10:16:31 CoreCOM\ResIntl
> 10:16:31 CoreTool
> 10:16:31 CoreTool\Res1033
> 10:16:31 CoreTool\ResOther
> 10:16:31 DBLibCli
> 10:16:31 SFExt
> 10:16:31 SFExt\ActiveX
> 10:16:31 SFExt\ActiveX\Res1033
> 10:16:31 SFExt\ActiveX\ResIntl
> 10:16:31 SFExt\Res1033
> 10:16:31 SFExt\ResIntl
> 10:16:31 Trace
> 10:16:31 Trace\Res1033
> 10:16:31 Trace\ResOther
> 10:16:31 MiscCore
> 10:16:31 MC
> 10:16:31 MC\MC1033
> 10:16:31 MC\MCIntl
> 10:16:31 MC\Help
> 10:16:31 SQLMgr
> 10:16:31 SQLMgr\Res1033
> 10:16:31 SQLMgr\ResIntl
> 10:16:31 SvrTool
> 10:16:31 SvrTool\Res1033
> 10:16:31 SvrTool\ResIntl
> 10:16:31 DTSUI
> 10:16:31 DTSUI\Res1033
> 10:16:31 DTSUI\ResIntl
> 10:16:31 MSOlap
> 10:16:32 MSOlap\Res1033
> 10:16:32 MSOlap\ResIntl
> 10:16:32 ATL
> 10:16:32 ATL\winnt
> 10:16:32 ATL\win9x
> 10:16:32 MFC42U
> 10:16:32 VC
> 10:16:32 VB
> 10:16:32 OCX1
> 10:16:32 SQLAdHlp
> 10:16:32 SQLAdHlp\Res1033
> 10:16:32 SQLAdHlp\ResOther
> 10:16:32 {E07FDDBE-5A21-11d2-9DAD-00C04F79D434}
> 10:16:32 {E07FDDC7-5A21-11d2-9DAD-00C04F79D434}
> 10:16:32 {E07FDDC0-5A21-11d2-9DAD-00C04F79D434}
> 10:16:32 {E07FDDBF-5A21-11d2-9DAD-00C04F79D434}
> 10:16:32 End Action LogSelectedComponents
> 10:16:32 Begin Action InstallPkgs:
> 10:16:32 Begin Action: Locked Connectivity Files Check
> 10:16:40 ConnectivityLocked returned: 0
> 10:16:40 The operation completed successfully.
> 10:16:40 End Action: Locked Connectivity Files Check
> 10:16:40 Setup is installing Microsoft Data Access Components (MDAC) ...
> 10:16:40 \\DEV1\DVD\ENGLISH\SQL2000\DEV\x86\Other\sqlredis.exe /q:a
> /C:"setupre.exe WARN=1 -s -SMS"
> 10:17:43 ExitCode: 0
> 10:17:43 Setup is installing Microsoft Distributed Transaction Coordinator
> (MSDTC) ...
> 10:17:43 C:\WINDOWS\TEMP\SqlSetup\Bin\cldtcstp.exe -SupportDir
> "C:\WINDOWS\TEMP\SqlSetup\Bin" -DTCPkg
> "\\DEV1\DVD\ENGLISH\SQL2000\DEV\x86\Other\dtcsetup.exe" -LogFile
> "C:\WINDOWS\sqlstp.log"
> 10:17:45 Process Exit Code: (0)
> 10:17:45 /Q:A /T:C:\WINDOWS\TEMP\ixp001.tmp
> 10:17:45 Setup is installing HTML Help ...
> 10:17:48 HTML Help installer exit code: 0
> 10:18:15 End Action InstallPkgs
> 10:18:15 Begin Action MoveFileData:
> 10:18:15 Enabled SELFREGISTERBATCH
> 10:18:15 Enabled CORECOMPONENTHANDLING
> 10:21:34 Begin Action: MoveFileDataSpecial
> 10:21:37 End Action: MoveFileDataSpecial
> 10:21:37 End Action MoveFileData
> 10:21:37 Begin Action ProcessAfterDataMove:
> 10:21:37 \\DEV1\DVD\ENGLISH\SQL2000\DEV\x86\Binn\hhcol.exe C:\Program
> Files\Microsoft SQL Server\80\Tools\Books
> 10:21:42 End Action ProcessAfterDataMove
> 10:21:42 Begin Action BuildServer:
> 10:21:42 C:\WINDOWS\TEMP\SqlSetup\Bin\scm.exe -Silent 1 -Action
5 -ExePath
> "C:\Program Files\Microsoft SQL Server\MSSQL\binn\sqlservr.exe" -Service
> "MSSQLSERVER"
> 10:21:43 Process Exit Code: (0)
> 10:21:43 Begin Action: CreateRegistrySetSQL
> 10:21:43 End Action: CreateRegistrySetSQL
> 10:21:43 Begin Action: RegWriteSetupEntry
> 10:21:43 End Action: RegWriteSetupEntry
> 10:21:43 Begin Action: CreateSer
> 10:21:43 End Action: CreateSer
> 10:21:43 Begin Action: SkuIt
> 10:21:44 End Action: SkuIt
> 10:21:45 SetFileSecuritySQLAndAdmin for C:\Program Files\Microsoft SQL
> Server\MSSQL returned: 0, 0
> 10:21:45 SetRegSecuritySQLAndAdmin for
> Software\Microsoft\MSSQLServer\MSSQLServer returned: 0, 0
> 10:21:45 Begin Action: UpdateSystemPath
> 10:21:45 Path successfully updated.
> 10:21:45 C:\oracle\ora92\bin;C:\Program
> Files\Oracle\jre\1.3.1\bin;C:\Program
>
Files\Oracle\jre\1.1.8\bin;C:\Perl\bin\;%SystemRoot%\system32;%SystemRoot%;%
SystemRoot%\System32\Wbem;C:\OCM;C:\Program
> Files\Microsoft SQL Server\80\Tools\Binn\;C:\Program Files\Common
> Files\Autodesk Shared\;C:\Program Files\proe2001\bin;C:\Program
Files\Common
> Files\Roxio Shared\DLLShared;C:\Program Files\UltraEdit;C:\Program
> Files\Rouzer File Printer\;C:\Program Files\Executive Software\Diskeeper\
> 10:21:45 End Action: UpdateSystemPath
> 10:21:46 Grant Right for KALTEC\administrator returned : 1, 0
> 10:21:46 Grant Right for KALTEC\administrator returned : 1, 0
> 10:21:46 Grant Right for KALTEC\administrator returned : 1, 0
> 10:21:47 Grant Right for KALTEC\administrator returned : 1, 0
> 10:21:47 Grant Right for KALTEC\administrator returned : 1, 0
> 10:21:48 C:\Program Files\Microsoft SQL
erver\80\Tools\Binn\cnfgsvr.exe -F
> "C:\WINDOWS\sqlstp.log" -I MSSQLSERVER -V 1 -M 0 -Q
> "SQL_Latin1_General_CP1_CI_AS" -H 66300 -U sa -P
>
############################################################################
###
>
> Starting Service ...
> SQL_Latin1_General_CP1_CI_AS
> -m -Q -T4022 -T3659
> Connecting to Server ...
> driver={sql server};server=DEV2;UID=sa;PWD=;database=master
> [Microsoft][ODBC Driver Manager] Data source name not found and no default
> driver specified
> driver={sql server};server=DEV2;UID=sa;PWD=;database=master
> [Microsoft][ODBC Driver Manager] Data source name not found and no default
> driver specified
> driver={sql server};server=DEV2;UID=sa;PWD=;database=master
> [Microsoft][ODBC Driver Manager] Data source name not found and no default
> driver specified
> SQL Server configuration failed.
>
############################################################################
###
> 10:22:26 Process Exit Code: (-1)
> 10:22:35 Setup failed to configure the server. Refer to the server error
> logs and C:\WINDOWS\sqlstp.log for more information.
> 10:22:37 Action CleanUpInstall:
> 10:22:37 C:\WINDOWS\TEMP\SqlSetup\Bin\scm.exe -Silent 1 -Action
4 -Service
> SQLSERVERAGENT
> 10:22:38 Process Exit Code: (1060) The specified service does not exist as
> an installed service.
> 10:22:38 C:\WINDOWS\TEMP\SqlSetup\Bin\scm.exe -Silent 1 -Action
4 -Service
> MSSQLSERVER
> 10:22:38 Process Exit Code: (0)
> 10:22:38 StatsGenerate returned: 2
> 10:22:38 StatsGenerate (0x0,0x1,0xf000000,0x100,1033,303,0x0,0x1,0,0,0
> 10:22:38 StatsGenerate -1,<Login Name>)
> 10:22:38 Installation Failed.
> ----
--
> 2004-10-28 10:21:51.33 server Microsoft SQL Server 2000 - 8.00.194
> (Intel X86)
> Aug 6 2000 00:57:48
> Copyright (c) 1988-2000 Microsoft Corporation
> Developer Edition on Windows NT 5.1 (Build 2600: Service Pack 1)
> 2004-10-28 10:21:51.37 server Copyright (C) 1988-2000 Microsoft
> Corporation.
> 2004-10-28 10:21:51.37 server All rights reserved.
> 2004-10-28 10:21:51.37 server Server Process ID is 3460.
> 2004-10-28 10:21:51.37 server Logging SQL Server messages in file
> 'C:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
> 2004-10-28 10:21:51.41 server SQL Server is starting at priority class
> 'normal'(1 CPU detected).
> 2004-10-28 10:21:51.78 server SQL Server configured for thread mode
> processing.
> 2004-10-28 10:21:51.82 server Using dynamic lock allocation. [2500]
Lock
> Blocks, [5000] Lock Owner Blocks.
> 2004-10-28 10:21:51.87 server Attempting to initialize Distributed
> Transaction Coordinator.
> 2004-10-28 10:21:56.01 spid3 Warning ******************
> 2004-10-28 10:21:56.01 spid3 SQL Server started in single user mode.
> Updates allowed to system catalogs.
> 2004-10-28 10:21:56.04 spid3 Starting up database 'master'.
> 2004-10-28 10:21:57.41 spid3 Server name is 'DEV2'.
> 2004-10-28 10:21:57.42 server Using 'SSNETLIB.DLL' version '8.0.311'.
> 2004-10-28 10:21:57.42 spid5 Starting up database 'model'.
> 2004-10-28 10:21:57.42 spid7 Starting up database 'msdb'.
> 2004-10-28 10:21:57.42 spid8 Starting up database 'pubs'.
> 2004-10-28 10:21:57.42 spid9 Starting up database 'Northwind'.
> 2004-10-28 10:21:58.95 spid5 Clearing tempdb database.
> 2004-10-28 10:22:00.94 server SQL server listening on 10.10.1.33: 1433.
> 2004-10-28 10:22:00.94 server SQL server listening on 127.0.0.1: 1433.
> 2004-10-28 10:22:02.26 spid5 Starting up database 'tempdb'.
> 2004-10-28 10:22:02.41 server SQL server listening on TCP, Shared
Memory,
> Named Pipes.
> 2004-10-28 10:22:02.41 server SQL Server is ready for client
connections
> 2004-10-28 10:22:02.61 spid3 Recovery complete.
> 2004-10-28 10:22:02.64 spid3 Warning: override, autoexec procedures
> skipped.
> 2004-10-28 10:22:12.92 spid3 SQL Server is terminating due to 'stop'
> request from Service Control Manager.
>

Passwords in the SSIS configuration file

Thanks to some earlier help from this forum, I have my package running using configuration files and Windows Authentication. However, when I try to execute the package using Sql authentication, login fails for the user i am specifying. When I check out the configuration file, the connection string does not contain the password. I added the password to the connection string, but it does not cone back. I followed the instructions found on the following site:

http://www.nigelrivett.net/DTS/SSISConfigurationFile.html

After trying what was suggested there, I was still unsuccessful with my login attempt.

Anyone know how to set up a package to run using Sql authentication?

Thanks!

Craig

At the time of development, set the protection level of package to EncryptSensitiveWithUserKey, after this sertting the package will store the sensitive information like password in itself.

Atul

Password security

Have SQL 7.0 running on a Windows 2000 server. Users
access the database on a front end client that utilizes
SQL authentication. I see no password restriction
properties anywhere. I need to set some restrictions,
such as password expiration in 90 days, unique password
requirements, and minimum password lengths. Where do I
set up these restrictions? I can't find anything.Those options are not availble for SQL logins in SQL 7 or 2000. Odds are
we'll have it for the next major release.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.

Password not Added after Installation

Hi,
I recently installed MSDE 2000, by giving the following to
setup parameters in the Command Prompt:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\> D:\MSDE2000\Setup.Exe SAPWD="apple" SECURITYMODE=SQL
DISABLENETWORKPROTOCOLS=0 /L*v C:\MSDELog.txt
C:\>
In log file, it did mentioned that the installation is
successfull at it's end of the file. However the SA
password is blank eventhough I gave the password
as "apple". Why did this happen. Is there anything wrong
in my setup parameter mentioned in the Command Prompt?
Help required on this matter, cos there are several
computers left to install MSDE 2000 and hoping to use the
above setup parameters.
Thanx in advance,
shahzard.
hi shahzard,
"Shahzard" <anonymous@.discussions.microsoft.com> ha scritto nel messaggio
news:574901c47465$e8574990$a301280a@.phx.gbl...
> Hi,
> I recently installed MSDE 2000, by giving the following to
> setup parameters in the Command Prompt:
> Microsoft Windows XP [Version 5.1.2600]
> (C) Copyright 1985-2001 Microsoft Corp.
>
> C:\> D:\MSDE2000\Setup.Exe SAPWD="apple" SECURITYMODE=SQL
> DISABLENETWORKPROTOCOLS=0 /L*v C:\MSDELog.txt
> C:\>
> In log file, it did mentioned that the installation is
> successfull at it's end of the file. However the SA
> password is blank eventhough I gave the password
> as "apple". Why did this happen. Is there anything wrong
> in my setup parameter mentioned in the Command Prompt?
> Help required on this matter, cos there are several
> computers left to install MSDE 2000 and hoping to use the
> above setup parameters.
the command line is ok, and i reproduced the problem on a Win2k box, where
SECURITYMODE=SQL has not been honored...
will investigate a little further... for workaround, run Regedit, locate
HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\InstanceName\MSSQLServer
and set LoginMode key = 2
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

password expiry with HTTPS merge replication

Hi
We are using anonymous HTTPS merge replication.

The windows password used for the client subscriber expired on the publisher.

I reset it on the publisher - but SQL still seems to think that it is not expired - I get the following message in the event log of the publisher running SQL Server 2005

Login failed for user 'XYZ'. Reason: The password of the account has expired. [CLIENT: <local machine>]

Any ideas ?

thanks
Bruce

Two things to try:

1. Reset IIS and attempt to sync again

2. Since you are saying you use anon auth, I believe merge agent is not passing any credentials, just ensure that there is no other auth enabled on IIS.

Also I would suggest against anon authentication and instead use Basic authentication. And maybe you are using your domain\account in the anon auth instead of machine account? That would be more insecure. Strongly suggest you use basic authentication.

Password does not meet Windows policy requirements 2005

I have been given the task to see if our software will work against SQL
Server 2005:-
XP Pro installed on a Virtual PC
SQL Server 2005 Standard Edition Installed
Mixed mode Security
Check policy set to off
Installation of 2005 was successful and no error reported in the logs.
Now the fun started hen attempting to install our software, using the SA
account (we have also created additional SQL logins too but still have the
same problem) it gets as far as creating the various databases but when
attempting to create tables it receives the following error:-
Create Table failed
SQL-DMO error: 15118 [Microsoft][ODBC SQL Server Driver][SQL Server]
Password validation failed.The password does not meet Windows policy
requirements because it is not complex enough
The password we are using meets the criteria for creating passwords and I
have also checked Windows Security Settings and the Passord Policy 'Password
must meet complexity requirements' is disabled
If you need any additional information please let me know.
Many thanks
PaulHi Paul,
make sure that there is o domain policy activated which forces secure
passwords.
HTH, jens Suessmeyer.|||Jens,
Thank you for your reply the domain policy is not currently active
Paul
"Jens" wrote:
> Hi Paul,
> make sure that there is o domain policy activated which forces secure
> passwords.
> HTH, jens Suessmeyer.
>

Password complexity in SQL

We have a SQL 2000 server and a client app that accesses it. We utilize SQL
authentication for the users who have already logged into the Windows domain
with a separate userid and password.
We are currently going through a certification and accredidation test and
one of the things we are getting dinged on is that we do not require complex
passwords with the SQL password. I see nowhere in SQL server to setup
mandatory password complexities, ie: minimum 8 characters, at least 1
number, 1 capital letter, etc.
Is there somewhere in SQL 2000 that a password policy for the SQL password
can be setup?Not for SQL Server 2000 not I'm aware of, unless you build and enfore this
functionality yourself. In SQL Server 2005, SQL passwords will abide by the
Windows OS machine/domain password policy with Windows Server 2003 and
above. In either version, its preferred to use only Windows logins which
have had password complexity policies for some time. Do you really need to
support SQL logins?
Cheers,
Bob Beauchemin
http://www.SQLskills.com/blogs/bobb
"Rockitman" <Rockitman@.discussions.microsoft.com> wrote in message
news:8F93457A-538A-4FD5-8551-79A9404AB777@.microsoft.com...
> We have a SQL 2000 server and a client app that accesses it. We utilize
> SQL
> authentication for the users who have already logged into the Windows
> domain
> with a separate userid and password.
> We are currently going through a certification and accredidation test and
> one of the things we are getting dinged on is that we do not require
> complex
> passwords with the SQL password. I see nowhere in SQL server to setup
> mandatory password complexities, ie: minimum 8 characters, at least 1
> number, 1 capital letter, etc.
> Is there somewhere in SQL 2000 that a password policy for the SQL password
> can be setup?|||Well that's what I'm trying to tell these guys. We already meet the
password requirements as a user cannot even get access to the client app
without first logging into the domain with a required complex password. If
I
change all the users to Windows authentication, when they access the client
app, will it just automatically open or will they have to reenter their
Domain id and password?
"Bob Beauchemin" wrote:

> Not for SQL Server 2000 not I'm aware of, unless you build and enfore this
> functionality yourself. In SQL Server 2005, SQL passwords will abide by th
e
> Windows OS machine/domain password policy with Windows Server 2003 and
> above. In either version, its preferred to use only Windows logins which
> have had password complexity policies for some time. Do you really need to
> support SQL logins?
> Cheers,
> Bob Beauchemin
> http://www.SQLskills.com/blogs/bobb|||If you use Windows authentication, their existing credentials are used, they
don't need to reenter. You'd need to change the connection strings in the
client apps to make this happen. There are some issues with delegation of
credentials (NTLM credentials are good for 1 inter-machine "hop", Kerberos
credentials can do multi-machine only if you have delegation enabled on a
server level) so you'd want to ensure that your application architecture can
accomdate this, especially if you have an intranet application. There's a
section in the SQL Server Books Online with details.
Cheers,
Bob Beauchemin
http://www.SQLskills.com/blogs/bobb
"Rockitman" <Rockitman@.discussions.microsoft.com> wrote in message
news:3A6FD24F-14C1-4C15-B559-CD1489849867@.microsoft.com...
> Well that's what I'm trying to tell these guys. We already meet the
> password requirements as a user cannot even get access to the client app
> without first logging into the domain with a required complex password.
> If I
> change all the users to Windows authentication, when they access the
> client
> app, will it just automatically open or will they have to reenter their
> Domain id and password?
> "Bob Beauchemin" wrote:
>
>

Passing the User ID and AD group as Parameter

Hi...
I have a requirement where I need to pass the Users Windows userID and the AD group through which he is associated to the database so that I can get appropiate data.

Is there a way I can pass the Windows user ID and the AD group(through which he is authenticated in Reporting Serivces) through the Reporting Serivces as a parameter so that it can be used in the Reporting Query.

Thanks,
siaj

The UserID parameter in the report holds the username information including the logged on domainor machine. getting the AD Group in which the user is authenticated to view the report is a bit different as the user can be in multiple groups, though it can′t be identified which group the user has granted the effective permissions to the report. (if you are hit by a machine gun you probably won′t know which bullet killed you at the end :-) )

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de
|||

As Jens says, UserID is just available using the internal object. For the AD group you should consider writing a custom assembly that performs the operation according to your business rules to decide which is THE group among the ones the user may pertain. I've not checked how difficult it will be to write such code in .Net but sounds not much complicated.

Best regards,
Jordi Rambla
MVP SQL Server
SolidQualityLearning|||Hi Siaj,

Were you able to figure this out? I am in need of the same functionality. I undertand .Net has a 'IsInGroup()' function that can check if a user is in a group but I am not sure how it goes...

Thanks,
Ben|||test|||Have you figured this out? I am in the same situation...

Thanks,
Ben