HELP!... SQL Log Gone. How do I recover Database

As the subject says...
I will admit to some stupidity. I inadvertently deleted
the log file.
On top of that, it appears my backups have failed, so no
back up.
Data file still exists.
Please tell me there is a way to recover.
Thanks in advance.
SvenI would give MS PSS a call if it's important to get it back.
http://support.microsoft.com/default.aspx?scid=fh;EN-US;sql SQL Support
http://www.mssqlserver.com/faq/general-pss.asp MS PSS
But if all else fails here is something you can try:
http://www.sqlservercentral.com/scripts/scriptdetails.asp?scriptid=599
Restoring a .mdf
Andrew J. Kelly
SQL Server MVP
"Sven Hansen" <svenhansen@.shaw.ca> wrote in message
news:079001c3af02$a07d2fa0$a101280a@.phx.gbl...
> As the subject says...
> I will admit to some stupidity. I inadvertently deleted
> the log file.
> On top of that, it appears my backups have failed, so no
> back up.
> Data file still exists.
> Please tell me there is a way to recover.
> Thanks in advance.
> Sven|||If you have the data file, then you can bring back your
database by using "sp_attach_db" coomand.
Look in BOL, for syntax and more info. Its very easy.
Good Luck!
-SQLVarad (MCDBA-1999,MCSE-1999)
>--Original Message--
>As the subject says...
>I will admit to some stupidity. I inadvertently deleted
>the log file.
>On top of that, it appears my backups have failed, so no
>back up.
>Data file still exists.
>Please tell me there is a way to recover.
>Thanks in advance.
>Sven
>.
>|||Since you have only data file, use this syntax
Example:
EXEC sp_attach_db @.dbname = 'pubs',
'c:\Program Files\Microsoft SQL Server\MSSQL\Data\pubs.mdf'
SQL Server will automatically attach a new log file.
Good Luck!
SQLVarad (MCDBA-1999,MCSE-1999)
>--Original Message--
>As the subject says...
>I will admit to some stupidity. I inadvertently deleted
>the log file.
>On top of that, it appears my backups have failed, so no
>back up.
>Data file still exists.
>Please tell me there is a way to recover.
>Thanks in advance.
>Sven
>.
>|||You saved my life... and likely my job... :)
Thank you.
The script worked perfectly.
Take care and thanks again.
Sven
>--Original Message--
>I would give MS PSS a call if it's important to get it
back.
>http://support.microsoft.com/default.aspx?scid=fh;EN-
US;sql SQL Support
>http://www.mssqlserver.com/faq/general-pss.asp MS PSS
>But if all else fails here is something you can try:
>http://www.sqlservercentral.com/scripts/scriptdetails.asp
?scriptid=599
>Restoring a .mdf
>
>--
>Andrew J. Kelly
>SQL Server MVP
>
>"Sven Hansen" <svenhansen@.shaw.ca> wrote in message
>news:079001c3af02$a07d2fa0$a101280a@.phx.gbl...
>> As the subject says...
>> I will admit to some stupidity. I inadvertently
deleted
>> the log file.
>> On top of that, it appears my backups have failed, so
no
>> back up.
>> Data file still exists.
>> Please tell me there is a way to recover.
>> Thanks in advance.
>> Sven
>
>.
>

help! when I restore the database!

when I restore the database from a backup file.I failed
the code is "SQLstate 42000
because my sql server is chines
the message means
database "xxx" has 2 family members,but now provide 1
I think there is miss the log
how can I do?From the error msg it sounds like you striped your backup across multiple
devices and you have only specified 1 for the restore.
Provide all file locations that you backed up for that set when restoring.
--
Allan Mitchell (Microsoft SQL Server MVP)
MCSE,MCDBA
www.SQLDTS.com
I support PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org
"Silence" <anonymous@.discussions.microsoft.com> wrote in message
news:30617EBA-03E3-492F-986A-C85E94F15F72@.microsoft.com...
> when I restore the database from a backup file.I failed.
> the code is "SQLstate 42000"
> because my sql server is chinese
> the message means:
> database "xxx" has 2 family members,but now provide 1.
> I think there is miss the log.
> how can I do?|||but the file is my friend gave me
and now cannot backup again from original database
how can I do?|||> but the file is my friend gave me.
Can you re-phrase that?
> and now cannot backup again from original database.
> how can I do?
By original, do you mean the database you tried to restore into or the one that the backup was
produced on?
Can you explain a little bit more details what happened?
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Silence" <anonymous@.discussions.microsoft.com> wrote in message
news:6486E3F3-83D8-4506-91E7-F3B3B2344045@.microsoft.com...
> but the file is my friend gave me.
> and now cannot backup again from original database.
> how can I do?|||because the computer's hard disk was broken
so the data was los
he gave me the backup file is the only file.|||Just read about the RESTORE command in Books Online and do the restore based on your backup file
(from Query analyzer).
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Silence" <anonymous@.discussions.microsoft.com> wrote in message
news:A1A4F50B-4ED9-4634-BD25-AB89D21C2729@.microsoft.com...
> because the computer's hard disk was broken.
> so the data was lost
> he gave me the backup file is the only file.|||which topic can I found?
can you type the command for me?
thank you!
-- Tibor Karaszi wrote: --
Just read about the RESTORE command in Books Online and do the restore based on your backup file
(from Query analyzer).
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Silence" <anonymous@.discussions.microsoft.com> wrote in message
news:A1A4F50B-4ED9-4634-BD25-AB89D21C2729@.microsoft.com...
> because the computer's hard disk was broken.
> so the data was lost
> he gave me the backup file is the only file.|||The exact command to type depends on a lot of factors (the path to the backup file, the path to the
database files etc etc). In Books Online, you find the Transact-SQL Reference. Here you find the
RESTORE command documented.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"silence" <zjflyer@.hotmail.com> wrote in message
news:D32AE25A-E164-4B87-BD77-EE3B9E7C054C@.microsoft.com...
> which topic can I found?
> can you type the command for me?
> thank you!
> -- Tibor Karaszi wrote: --
> Just read about the RESTORE command in Books Online and do the restore based on your backup
file
> (from Query analyzer).
> --
> Tibor Karaszi, SQL Server MVP
> Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
>
> "Silence" <anonymous@.discussions.microsoft.com> wrote in message
> news:A1A4F50B-4ED9-4634-BD25-AB89D21C2729@.microsoft.com...
> > because the computer's hard disk was broken.
> > so the data was lost
> > he gave me the backup file is the only file.
>
>

Help! Suspect Databases - Hardware Failure

We have numerous suspect databases across multiple serverse due to a hardware
failure on our SAN. The part of the SAN that failed had a combination of data
and log files, but not both for a given database.
Right now we have services shut down on the server. When we bring the server
back up, after fixing our hardware failure, what would be the best steps?
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums.aspx/sql-server/200703/1
"cbrichards via droptable.com" <u3288@.uwe> wrote in message
news:6eca09c69ec9c@.uwe...
> We have numerous suspect databases across multiple serverse due to a
> hardware
> failure on our SAN. The part of the SAN that failed had a combination of
> data
> and log files, but not both for a given database.
> Right now we have services shut down on the server. When we bring the
> server
> back up, after fixing our hardware failure, what would be the best steps?
BEFORE bringing up the server, make complete backups of all files.
Then once you bring up the server, check the logs and find out why the
databases are suspect.
In some cases it may be as simple as the drive letters or paths no longer
being right and once you fix those, the database may come up cleanly.
If it's more complex, you'll have to do different things, but hard to
recommend w/o knowing in advance the exact nature of the problems.
No matter what I'd make sure to do a DBCC checkdb once the database is back
up, just to be sure.
(btw, I've found that it takes pretty bad problems to outright corrupt a SQL
2000/2005 database, so you may luck out.)

> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forums.aspx/sql-server/200703/1
>
Greg Moore
SQL Server DBA Consulting
sql (at) greenms.com http://www.greenms.com
|||Thanks Greg. Once the hardware was repaired and we restarted the services (we
had complete backups available) all databases came up cleanly.
If I were to set a job to execute DBCC CHECKDB WITH NO_INFOMSGS to run after
hours, if there were errors encountered, would I still be informed, even
though I had the "WITH NO_INFOMSGS" option?
Greg D. Moore (Strider) wrote:
>[quoted text clipped - 5 lines]
>BEFORE bringing up the server, make complete backups of all files.
>Then once you bring up the server, check the logs and find out why the
>databases are suspect.
>In some cases it may be as simple as the drive letters or paths no longer
>being right and once you fix those, the database may come up cleanly.
>If it's more complex, you'll have to do different things, but hard to
>recommend w/o knowing in advance the exact nature of the problems.
>No matter what I'd make sure to do a DBCC checkdb once the database is back
>up, just to be sure.
>(btw, I've found that it takes pretty bad problems to outright corrupt a SQL
>2000/2005 database, so you may luck out.)
>
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums.aspx/sql-server/200703/1
|||"cbrichards via droptable.com" <u3288@.uwe> wrote in message
news:6ecae312206bc@.uwe...
> Thanks Greg. Once the hardware was repaired and we restarted the services
> (we
> had complete backups available) all databases came up cleanly.
>
Glad to hear it.

> If I were to set a job to execute DBCC CHECKDB WITH NO_INFOMSGS to run
> after
> hours, if there were errors encountered, would I still be informed, even
> though I had the "WITH NO_INFOMSGS" option?
I believe so.

>
Greg Moore
SQL Server DBA Consulting
sql (at) greenms.com http://www.greenms.com

Help! Suspect Databases - Hardware Failure

We have numerous suspect databases across multiple serverse due to a hardware
failure on our SAN. The part of the SAN that failed had a combination of data
and log files, but not both for a given database.
Right now we have services shut down on the server. When we bring the server
back up, after fixing our hardware failure, what would be the best steps?
--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200703/1"cbrichards via SQLMonster.com" <u3288@.uwe> wrote in message
news:6eca09c69ec9c@.uwe...
> We have numerous suspect databases across multiple serverse due to a
> hardware
> failure on our SAN. The part of the SAN that failed had a combination of
> data
> and log files, but not both for a given database.
> Right now we have services shut down on the server. When we bring the
> server
> back up, after fixing our hardware failure, what would be the best steps?
BEFORE bringing up the server, make complete backups of all files.
Then once you bring up the server, check the logs and find out why the
databases are suspect.
In some cases it may be as simple as the drive letters or paths no longer
being right and once you fix those, the database may come up cleanly.
If it's more complex, you'll have to do different things, but hard to
recommend w/o knowing in advance the exact nature of the problems.
No matter what I'd make sure to do a DBCC checkdb once the database is back
up, just to be sure.
(btw, I've found that it takes pretty bad problems to outright corrupt a SQL
2000/2005 database, so you may luck out.)
> --
> Message posted via SQLMonster.com
> http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200703/1
>
--
Greg Moore
SQL Server DBA Consulting
sql (at) greenms.com http://www.greenms.com|||Thanks Greg. Once the hardware was repaired and we restarted the services (we
had complete backups available) all databases came up cleanly.
If I were to set a job to execute DBCC CHECKDB WITH NO_INFOMSGS to run after
hours, if there were errors encountered, would I still be informed, even
though I had the "WITH NO_INFOMSGS" option?
Greg D. Moore (Strider) wrote:
>> We have numerous suspect databases across multiple serverse due to a
>> hardware
>[quoted text clipped - 5 lines]
>> server
>> back up, after fixing our hardware failure, what would be the best steps?
>BEFORE bringing up the server, make complete backups of all files.
>Then once you bring up the server, check the logs and find out why the
>databases are suspect.
>In some cases it may be as simple as the drive letters or paths no longer
>being right and once you fix those, the database may come up cleanly.
>If it's more complex, you'll have to do different things, but hard to
>recommend w/o knowing in advance the exact nature of the problems.
>No matter what I'd make sure to do a DBCC checkdb once the database is back
>up, just to be sure.
>(btw, I've found that it takes pretty bad problems to outright corrupt a SQL
>2000/2005 database, so you may luck out.)
>
--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200703/1|||"cbrichards via SQLMonster.com" <u3288@.uwe> wrote in message
news:6ecae312206bc@.uwe...
> Thanks Greg. Once the hardware was repaired and we restarted the services
> (we
> had complete backups available) all databases came up cleanly.
>
Glad to hear it.
> If I were to set a job to execute DBCC CHECKDB WITH NO_INFOMSGS to run
> after
> hours, if there were errors encountered, would I still be informed, even
> though I had the "WITH NO_INFOMSGS" option?
I believe so.
>
--
Greg Moore
SQL Server DBA Consulting
sql (at) greenms.com http://www.greenms.com|||On 06.03.2007 22:11, cbrichards via SQLMonster.com wrote:
> Thanks Greg. Once the hardware was repaired and we restarted the services (we
> had complete backups available) all databases came up cleanly.
> If I were to set a job to execute DBCC CHECKDB WITH NO_INFOMSGS to run after
> hours, if there were errors encountered, would I still be informed, even
> though I had the "WITH NO_INFOMSGS" option?
Wouldn't it be better to run this first before using the DB again? I
mean if there were issues you'd rather want to fix them before you put
the DB back in production.
Kind regards
robert

Help! Suspect Databases - Hardware Failure

We have numerous suspect databases across multiple serverse due to a hardwar
e
failure on our SAN. The part of the SAN that failed had a combination of dat
a
and log files, but not both for a given database.
Right now we have services shut down on the server. When we bring the server
back up, after fixing our hardware failure, what would be the best steps?
Message posted via droptable.com
http://www.droptable.com/Uwe/Forum...server/200703/1"cbrichards via droptable.com" <u3288@.uwe> wrote in message
news:6eca09c69ec9c@.uwe...
> We have numerous suspect databases across multiple serverse due to a
> hardware
> failure on our SAN. The part of the SAN that failed had a combination of
> data
> and log files, but not both for a given database.
> Right now we have services shut down on the server. When we bring the
> server
> back up, after fixing our hardware failure, what would be the best steps?
BEFORE bringing up the server, make complete backups of all files.
Then once you bring up the server, check the logs and find out why the
databases are suspect.
In some cases it may be as simple as the drive letters or paths no longer
being right and once you fix those, the database may come up cleanly.
If it's more complex, you'll have to do different things, but hard to
recommend w/o knowing in advance the exact nature of the problems.
No matter what I'd make sure to do a DBCC checkdb once the database is back
up, just to be sure.
(btw, I've found that it takes pretty bad problems to outright corrupt a SQL
2000/2005 database, so you may luck out.)

> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forum...server/200703/1
>
Greg Moore
SQL Server DBA Consulting
sql (at) greenms.com http://www.greenms.com|||Thanks Greg. Once the hardware was repaired and we restarted the services (w
e
had complete backups available) all databases came up cleanly.
If I were to set a job to execute DBCC CHECKDB WITH NO_INFOMSGS to run after
hours, if there were errors encountered, would I still be informed, even
though I had the "WITH NO_INFOMSGS" option?
Greg D. Moore (Strider) wrote:
>[quoted text clipped - 5 lines]
>BEFORE bringing up the server, make complete backups of all files.
>Then once you bring up the server, check the logs and find out why the
>databases are suspect.
>In some cases it may be as simple as the drive letters or paths no longer
>being right and once you fix those, the database may come up cleanly.
>If it's more complex, you'll have to do different things, but hard to
>recommend w/o knowing in advance the exact nature of the problems.
>No matter what I'd make sure to do a DBCC checkdb once the database is back
>up, just to be sure.
>(btw, I've found that it takes pretty bad problems to outright corrupt a SQ
L
>2000/2005 database, so you may luck out.)
>
Message posted via droptable.com
http://www.droptable.com/Uwe/Forum...server/200703/1|||"cbrichards via droptable.com" <u3288@.uwe> wrote in message
news:6ecae312206bc@.uwe...
> Thanks Greg. Once the hardware was repaired and we restarted the services
> (we
> had complete backups available) all databases came up cleanly.
>
Glad to hear it.

> If I were to set a job to execute DBCC CHECKDB WITH NO_INFOMSGS to run
> after
> hours, if there were errors encountered, would I still be informed, even
> though I had the "WITH NO_INFOMSGS" option?
I believe so.

>
Greg Moore
SQL Server DBA Consulting
sql (at) greenms.com http://www.greenms.com|||On 06.03.2007 22:11, cbrichards via droptable.com wrote:
> Thanks Greg. Once the hardware was repaired and we restarted the services
(we
> had complete backups available) all databases came up cleanly.
> If I were to set a job to execute DBCC CHECKDB WITH NO_INFOMSGS to run aft
er
> hours, if there were errors encountered, would I still be informed, even
> though I had the "WITH NO_INFOMSGS" option?
Wouldn't it be better to run this first before using the DB again? I
mean if there were issues you'd rather want to fix them before you put
the DB back in production.
Kind regards
robertsql

Help! First timer with SQL

I am trying to write my first app using SQL Server. I am not able to even open a connection. I get the following error message:

Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.

I am not sure first of all why the user is listed as null. I hard coded a user name in for test purposes. Second, how DO I establish a trusted connection with a SQL Server. The SQL Server is located on an internal domain controller.

Also, is it necessary to have anything special installed on my remote machine? As I said, I am VERY new to Microsoft SQL ServerCan you post your conn string?|||Sure... here is the connection string. It was generated by default by the system.

data source=ERICSERVER;initial catalog=Northwind;integrated security=SSPI;persist security info=False;workstation id=ERIC;packet size=4096

Any ideas?|||ejcrammer I 2 am also in your shoes. I am new to SQL Server and ASP.NET. I also am trying to connect to a database and am receving the same error message you are. I have looked at your connection string but their does not seem to be one specific way to write the connection string because I have seen about 7 different versions all of which are not good and no one really explains them in detail. some ask for password and username some dont, I dont know. Anyway since were both in the same shoes I was wondering if you figure out this answere to this question you could post and let me know and I as well will post back if I figure out the answere to this problem we seem to be haveing.
Thanks

Help!

I have a SQL Server 7 running on NT 4.0 (not by choice). Last night at about 10:00 pm a scheduled DTS package failed. It has been running hourly for months without any problems. Suddenly I'm getting an error "Server could not load DCOM."

Has anyone else experienced this, and if so, how did you fix it?

THANKS!!!check security context of the account the server runs under.

Help!

I am trying to setup SQL server on MS Cluster Servers (with window 2003 OS).
I am always get following error during installation
"Setup failed to perform the required operation on the cluster nodes"
Base on sqlstp.log file (see below), it looks like cause by
10:35:07 C:\WINNT\TEMP\SqlSetup\Bin\remsetup.exe C:\WINNT\remsetup.ini
10:46:17 Process Exit Code: (2) The system cannot find the file specified.
Does anyone know how to solve this issue?
Thanks
Yong
10:35:07 Setup is performing required operations on cluster nodes. This may
take a few minutes...
10:35:07 C:\WINNT\TEMP\SqlSetup\Bin\remsetup.exe C:\WINNT\remsetup.ini
10:46:17 Process Exit Code: (2) The system cannot find the file specified.
10:46:17 Begin Action : GetRemsetupRetCode
10:46:17 Installation return status on SVMDB1 : 0
10:46:17 Installation return status on SVMDB2 : 2
10:46:17 End Action : GetRemsetupRetCode
#### SQL Server Remote Setup - Start Time 12/21/04 10:35:07 ####
CThreadPool::RunUntilCompleteHlpr create thread, index=0
CThread::Run thread [0x74] created for execution.
CThread::Process [0x74]
CThreadPool::RunUntilCompleteHlpr create thread, index=1
Running '\\SVMDB1\N$\ENGLISH\SQL2000\ENT\x86\setup\setupsq l.exe k=Nb k=Rm
k=Cl -SMS -s -f "\\SVMDB1\N$\ENGLISH\SQL2000\ENT\x86\setup\setup.i ns" -f1
\\SVMDB1\admin$\SVMDB1_SVMOBILE.iss -f2 "\\SVMDB1\admin$\setup.log" -e
"stpsilnt._ex" -b -x "C:\WINNT\TEMP\"' (SVMDB1) ...
CThread::Run thread [0x78] created for execution.
CThread::Process [0x78]
CThreadPool::RunUntilCompleteHlpr start thread [0x74],index=0
CThreadPool::RunUntilCompleteHlpr start thread [0x78],index=1
Script file copied to '\\SVMDB2\ADMIN$\SVMDB2_SVMOBILE.iss' successfully.
Installing remote service (SVMDB2)...
Running '\\SVMDB1\N$\ENGLISH\SQL2000\ENT\x86\setup\setupsq l.exe k=ClSec k=Rm
k=Cl -SMS -s -f "\\SVMDB1\N$\ENGLISH\SQL2000\ENT\x86\setup\setup.i ns" -f1
\\SVMDB2\ADMIN$\SVMDB2_SVMOBILE.iss -f2 "\\SVMDB2\admin$\setup.log" -e
"stpsilnt._ex" -x "C:\"' (SVMDB2) ...
CProcess::RunUntilComplete [0x74] exit code: 0
Remote process exit code was '0' (SVMDB1).
CThreadPool::RunUntilCompleteHlpr WaitForMultipleObjects returned: 0
CThreadPool::RunUntilCompleteHlpr signaled thread [0x74]
Thread [0x74] exit code: [0x0]
CRemoteProcess::RunUntilComplete [0x78] exit code: 2
Remote process exit code was '2' (SVMDB2).
CThreadPool::RunUntilCompleteHlpr WaitForMultipleObjects returned: 0
CThreadPool::RunUntilCompleteHlpr signaled thread [0x78]
Thread [0x78] exit code: [0x2]
CThreadPool::RunUntilComplete returned 2
CThreadPool::RunUntilComplete execution level=1, need execution: 0
One or more errors occurred while running the remote/unattended setups.
Disconnecting from remote machine (SVMDB1)...
Service removed successfully.
Remote files could not be removed.
#### SQL Server Remote Setup - Stop Time 12/21/04 10:45:59 ####
Disconnecting from remote machine (SVMDB2)...
Service removed successfully.
Remote files removed successfully.
#### SQL Server Remote Setup - Stop Time 12/21/04 10:46:16 ####
Have you tried coping the media onto the shared disk and running the install
from there? Have you already reboot both nodes? Make sure you reboot the
controlling node after any failure.
This should fix your issue.
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
http://msmvps.com/clustering - Blog
"Yong Zou (SearchIgnite)" <yz@.yz.com> wrote in message
news:eqpoTY35EHA.1596@.tk2msftngp13.phx.gbl...
>I am trying to setup SQL server on MS Cluster Servers (with window 2003
>OS).
> I am always get following error during installation
> "Setup failed to perform the required operation on the cluster nodes"
> Base on sqlstp.log file (see below), it looks like cause by
> 10:35:07 C:\WINNT\TEMP\SqlSetup\Bin\remsetup.exe C:\WINNT\remsetup.ini
> 10:46:17 Process Exit Code: (2) The system cannot find the file specified.
> Does anyone know how to solve this issue?
> Thanks
> Yong
> 10:35:07 Setup is performing required operations on cluster nodes. This
> may
> take a few minutes...
> 10:35:07 C:\WINNT\TEMP\SqlSetup\Bin\remsetup.exe C:\WINNT\remsetup.ini
> 10:46:17 Process Exit Code: (2) The system cannot find the file specified.
> 10:46:17 Begin Action : GetRemsetupRetCode
> 10:46:17 Installation return status on SVMDB1 : 0
> 10:46:17 Installation return status on SVMDB2 : 2
> 10:46:17 End Action : GetRemsetupRetCode
> #### SQL Server Remote Setup - Start Time 12/21/04 10:35:07 ####
> CThreadPool::RunUntilCompleteHlpr create thread, index=0
> CThread::Run thread [0x74] created for execution.
> CThread::Process [0x74]
> CThreadPool::RunUntilCompleteHlpr create thread, index=1
> Running '\\SVMDB1\N$\ENGLISH\SQL2000\ENT\x86\setup\setupsq l.exe k=Nb k=Rm
> k=Cl -SMS -s -f "\\SVMDB1\N$\ENGLISH\SQL2000\ENT\x86\setup\setup.i ns" -f1
> \\SVMDB1\admin$\SVMDB1_SVMOBILE.iss -f2 "\\SVMDB1\admin$\setup.log" -e
> "stpsilnt._ex" -b -x "C:\WINNT\TEMP\"' (SVMDB1) ...
> CThread::Run thread [0x78] created for execution.
> CThread::Process [0x78]
> CThreadPool::RunUntilCompleteHlpr start thread [0x74],index=0
> CThreadPool::RunUntilCompleteHlpr start thread [0x78],index=1
> Script file copied to '\\SVMDB2\ADMIN$\SVMDB2_SVMOBILE.iss' successfully.
> Installing remote service (SVMDB2)...
> Running '\\SVMDB1\N$\ENGLISH\SQL2000\ENT\x86\setup\setupsq l.exe k=ClSec
> k=Rm
> k=Cl -SMS -s -f "\\SVMDB1\N$\ENGLISH\SQL2000\ENT\x86\setup\setup.i ns" -f1
> \\SVMDB2\ADMIN$\SVMDB2_SVMOBILE.iss -f2 "\\SVMDB2\admin$\setup.log" -e
> "stpsilnt._ex" -x "C:\"' (SVMDB2) ...
> CProcess::RunUntilComplete [0x74] exit code: 0
> Remote process exit code was '0' (SVMDB1).
> CThreadPool::RunUntilCompleteHlpr WaitForMultipleObjects returned: 0
> CThreadPool::RunUntilCompleteHlpr signaled thread [0x74]
> Thread [0x74] exit code: [0x0]
> CRemoteProcess::RunUntilComplete [0x78] exit code: 2
> Remote process exit code was '2' (SVMDB2).
> CThreadPool::RunUntilCompleteHlpr WaitForMultipleObjects returned: 0
> CThreadPool::RunUntilCompleteHlpr signaled thread [0x78]
> Thread [0x78] exit code: [0x2]
> CThreadPool::RunUntilComplete returned 2
> CThreadPool::RunUntilComplete execution level=1, need execution: 0
> One or more errors occurred while running the remote/unattended setups.
> Disconnecting from remote machine (SVMDB1)...
> Service removed successfully.
> Remote files could not be removed.
> #### SQL Server Remote Setup - Stop Time 12/21/04 10:45:59 ####
> Disconnecting from remote machine (SVMDB2)...
> Service removed successfully.
> Remote files removed successfully.
> #### SQL Server Remote Setup - Stop Time 12/21/04 10:46:16 ####
>
|||Yes, I tried coping the media onto the shared disk and running the
installation from there. I also reboot both nodes after failure. I still get
same error
Thanks
Yong
"Rodney R. Fournier [MVP]" <rod@.die.spam.die.nw-america.com> wrote in
message news:%23XXHAf35EHA.1264@.TK2MSFTNGP12.phx.gbl...
> Have you tried coping the media onto the shared disk and running the
install[vbcol=seagreen]
> from there? Have you already reboot both nodes? Make sure you reboot the
> controlling node after any failure.
> This should fix your issue.
> Cheers,
> Rod
> MVP - Windows Server - Clustering
> http://www.nw-america.com - Clustering
> http://msmvps.com/clustering - Blog
> "Yong Zou (SearchIgnite)" <yz@.yz.com> wrote in message
> news:eqpoTY35EHA.1596@.tk2msftngp13.phx.gbl...
specified.[vbcol=seagreen]
specified.[vbcol=seagreen]
k=Rm[vbcol=seagreen]
"\\SVMDB1\N$\ENGLISH\SQL2000\ENT\x86\setup\setup.i ns" -f1[vbcol=seagreen]
successfully.[vbcol=seagreen]
"\\SVMDB1\N$\ENGLISH\SQL2000\ENT\x86\setup\setup.i ns" -f1
>
|||Darn, we had that issue here last night on two new clusters, IPSEC and a
firewall in between, local copy fixed it.
Ok, try these articles:
http://support.microsoft.com/default...b;en-us;818548
http://support.microsoft.com/default...b;en-us;318672
http://support.microsoft.com/default...b;en-us;302491
http://support.microsoft.com/default...b;en-us;321063
Please let me know which if any of these fix you issue.
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
http://msmvps.com/clustering - Blog
"Yong Zou (SearchIgnite)" <yz@.yz.com> wrote in message
news:Ogix7r45EHA.1028@.TK2MSFTNGP10.phx.gbl...
> Yes, I tried coping the media onto the shared disk and running the
> installation from there. I also reboot both nodes after failure. I still
> get
> same error
> Thanks
> Yong
> "Rodney R. Fournier [MVP]" <rod@.die.spam.die.nw-america.com> wrote in
> message news:%23XXHAf35EHA.1264@.TK2MSFTNGP12.phx.gbl...
> install
> specified.
> specified.
> k=Rm
> "\\SVMDB1\N$\ENGLISH\SQL2000\ENT\x86\setup\setup.i ns" -f1
> successfully.
> "\\SVMDB1\N$\ENGLISH\SQL2000\ENT\x86\setup\setup.i ns" -f1
>
|||Yong,
I think you hit the issue described in following article. Most often I have
seen this issue if the network connection name contains spaces or
parenthesis e.g. it should not be "Local Area Connection" or "Local Area
Connection 1" and should be something like "PUBLIC" or "PRIVATE". If this
does not solve the issue, you can try following other workarounds mentioned
in the article.
http://support.microsoft.com/kb/302491/EN-US/
PRB: SQL Server 2000 Cluster Setup may fail to perform required operations
on the cluster nodes when special characters are used in the resource name
Hope this helps.
Regards,
Shon Shah
Software Design Engineer/Test
Microsoft Cluster Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples, if any, are subject to the terms specified
at http://www.microsoft.com/info/cpyright.htm
Please do not send email directly to this alias. This alias is for newsgroup
purposes only.
"Yong Zou (SearchIgnite)" <yz@.yz.com> wrote in message
news:eqpoTY35EHA.1596@.tk2msftngp13.phx.gbl...
>I am trying to setup SQL server on MS Cluster Servers (with window 2003
>OS).
> I am always get following error during installation
> "Setup failed to perform the required operation on the cluster nodes"
> Base on sqlstp.log file (see below), it looks like cause by
> 10:35:07 C:\WINNT\TEMP\SqlSetup\Bin\remsetup.exe C:\WINNT\remsetup.ini
> 10:46:17 Process Exit Code: (2) The system cannot find the file specified.
> Does anyone know how to solve this issue?
> Thanks
> Yong
> 10:35:07 Setup is performing required operations on cluster nodes. This
> may
> take a few minutes...
> 10:35:07 C:\WINNT\TEMP\SqlSetup\Bin\remsetup.exe C:\WINNT\remsetup.ini
> 10:46:17 Process Exit Code: (2) The system cannot find the file specified.
> 10:46:17 Begin Action : GetRemsetupRetCode
> 10:46:17 Installation return status on SVMDB1 : 0
> 10:46:17 Installation return status on SVMDB2 : 2
> 10:46:17 End Action : GetRemsetupRetCode
> #### SQL Server Remote Setup - Start Time 12/21/04 10:35:07 ####
> CThreadPool::RunUntilCompleteHlpr create thread, index=0
> CThread::Run thread [0x74] created for execution.
> CThread::Process [0x74]
> CThreadPool::RunUntilCompleteHlpr create thread, index=1
> Running '\\SVMDB1\N$\ENGLISH\SQL2000\ENT\x86\setup\setupsq l.exe k=Nb k=Rm
> k=Cl -SMS -s -f "\\SVMDB1\N$\ENGLISH\SQL2000\ENT\x86\setup\setup.i ns" -f1
> \\SVMDB1\admin$\SVMDB1_SVMOBILE.iss -f2 "\\SVMDB1\admin$\setup.log" -e
> "stpsilnt._ex" -b -x "C:\WINNT\TEMP\"' (SVMDB1) ...
> CThread::Run thread [0x78] created for execution.
> CThread::Process [0x78]
> CThreadPool::RunUntilCompleteHlpr start thread [0x74],index=0
> CThreadPool::RunUntilCompleteHlpr start thread [0x78],index=1
> Script file copied to '\\SVMDB2\ADMIN$\SVMDB2_SVMOBILE.iss' successfully.
> Installing remote service (SVMDB2)...
> Running '\\SVMDB1\N$\ENGLISH\SQL2000\ENT\x86\setup\setupsq l.exe k=ClSec
> k=Rm
> k=Cl -SMS -s -f "\\SVMDB1\N$\ENGLISH\SQL2000\ENT\x86\setup\setup.i ns" -f1
> \\SVMDB2\ADMIN$\SVMDB2_SVMOBILE.iss -f2 "\\SVMDB2\admin$\setup.log" -e
> "stpsilnt._ex" -x "C:\"' (SVMDB2) ...
> CProcess::RunUntilComplete [0x74] exit code: 0
> Remote process exit code was '0' (SVMDB1).
> CThreadPool::RunUntilCompleteHlpr WaitForMultipleObjects returned: 0
> CThreadPool::RunUntilCompleteHlpr signaled thread [0x74]
> Thread [0x74] exit code: [0x0]
> CRemoteProcess::RunUntilComplete [0x78] exit code: 2
> Remote process exit code was '2' (SVMDB2).
> CThreadPool::RunUntilCompleteHlpr WaitForMultipleObjects returned: 0
> CThreadPool::RunUntilCompleteHlpr signaled thread [0x78]
> Thread [0x78] exit code: [0x2]
> CThreadPool::RunUntilComplete returned 2
> CThreadPool::RunUntilComplete execution level=1, need execution: 0
> One or more errors occurred while running the remote/unattended setups.
> Disconnecting from remote machine (SVMDB1)...
> Service removed successfully.
> Remote files could not be removed.
> #### SQL Server Remote Setup - Stop Time 12/21/04 10:45:59 ####
> Disconnecting from remote machine (SVMDB2)...
> Service removed successfully.
> Remote files removed successfully.
> #### SQL Server Remote Setup - Stop Time 12/21/04 10:46:16 ####
>
|||Thanks Shon. Looks like this is not the source of cause my problem. I also
checked SQLSTPx.Log file, and find interesting things,
14:53:12 C:\PROGRA~1\COMMON~1\MICROS~1\SQLDEB~1\sqldbreg.ex e -RegServer
14:53:12 Process Exit Code: (-2147312566) Error loading type library/DLL.
and don't know this is cause of my problem. If it is, any idea how to avoid
this?
Thanks again for your help
Yong
14:53:02 Begin Action PostSetupRegistry:
14:53:02 C:\WINNT\TEMP\SqlSetup\Bin\scm.exe -Silent 1 -Action 7 -Service
MSSQL$SVM -SvcStartType 1 -SvcAccount "TestNew\Administrator" -SvcEPwd
14:53:03 Process Exit Code: (0)
14:53:03 C:\WINNT\TEMP\SqlSetup\Bin\scm.exe -Silent 1 -Action 5 -Service
"SQLAgent$SVM" -Dependencies MSSQL$SVM -ExePath "C:\Program Files\Microsoft
SQL Server\MSSQL$SVM\binn\sqlagent.exe" -SvcAccount
"TestNew\Administrator" -SvcEPwd
14:53:12 Process Exit Code: (0)
14:53:12 SetupSQLExecSecurity returned: 0
14:53:12 PerfmonLoad returned: 0
14:53:12 C:\PROGRA~1\MICROS~1\80\Tools\Binn\dcomscm.exe /RegServer
14:53:12 Process Exit Code: (0)
14:53:12 C:\PROGRA~1\COMMON~1\MICROS~1\SQLDEB~1\sqldbreg.ex e -RegServer
14:53:12 Process Exit Code: (-2147312566) Error loading type library/DLL.
14:53:12 regsvr32.exe /s "C:\PROGRA~1\MICROS~1\80\COM\repldsui.dll"
14:53:13 Process Exit Code: (0)
14:53:13 **** File registered: C:\Program Files\Microsoft SQL
Server\80\COM\repldsui.dll
"Shon Shah [MSFT]" <shonsh@.online.microsoft.com> wrote in message
news:%232xR4645EHA.1524@.TK2MSFTNGP09.phx.gbl...
> Yong,
> I think you hit the issue described in following article. Most often I
have
> seen this issue if the network connection name contains spaces or
> parenthesis e.g. it should not be "Local Area Connection" or "Local Area
> Connection 1" and should be something like "PUBLIC" or "PRIVATE". If this
> does not solve the issue, you can try following other workarounds
mentioned
> in the article.
> http://support.microsoft.com/kb/302491/EN-US/
> PRB: SQL Server 2000 Cluster Setup may fail to perform required operations
> on the cluster nodes when special characters are used in the resource name
> Hope this helps.
> --
> Regards,
> Shon Shah
> Software Design Engineer/Test
> Microsoft Cluster Server
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> Use of included script samples, if any, are subject to the terms specified
> at http://www.microsoft.com/info/cpyright.htm
> Please do not send email directly to this alias. This alias is for
newsgroup[vbcol=seagreen]
> purposes only.
> "Yong Zou (SearchIgnite)" <yz@.yz.com> wrote in message
> news:eqpoTY35EHA.1596@.tk2msftngp13.phx.gbl...
specified.[vbcol=seagreen]
specified.[vbcol=seagreen]
m[vbcol=seagreen]
"\\SVMDB1\N$\ENGLISH\SQL2000\ENT\x86\setup\setup.i ns" -f1[vbcol=seagreen]
successfully.[vbcol=seagreen]
"\\SVMDB1\N$\ENGLISH\SQL2000\ENT\x86\setup\setup.i ns" -f1
>
|||Thanks Rod, I checked all of these, and looks like it still didn't solve my
problem. Base onSQLSTPx.Log file,
14:53:12 C:\PROGRA~1\COMMON~1\MICROS~1\SQLDEB~1\sqldbreg.ex e -RegServer
14:53:12 Process Exit Code: (-2147312566) Error loading type library/DLL.
I think this may be the cause of my issue, but don't know how to fix it
Thanks again for your helps
Yong
"Rodney R. Fournier [MVP]" <rod@.die.spam.die.nw-america.com> wrote in
message news:efnag445EHA.936@.TK2MSFTNGP12.phx.gbl...[vbcol=seagreen]
> Darn, we had that issue here last night on two new clusters, IPSEC and a
> firewall in between, local copy fixed it.
> Ok, try these articles:
> http://support.microsoft.com/default...b;en-us;818548
> http://support.microsoft.com/default...b;en-us;318672
> http://support.microsoft.com/default...b;en-us;302491
> http://support.microsoft.com/default...b;en-us;321063
> Please let me know which if any of these fix you issue.
> Cheers,
> Rod
> MVP - Windows Server - Clustering
> http://www.nw-america.com - Clustering
> http://msmvps.com/clustering - Blog
> "Yong Zou (SearchIgnite)" <yz@.yz.com> wrote in message
> news:Ogix7r45EHA.1028@.TK2MSFTNGP10.phx.gbl...
the[vbcol=seagreen]
2003[vbcol=seagreen]
C:\WINNT\remsetup.ini[vbcol=seagreen]
C:\WINNT\remsetup.ini[vbcol=seagreen]
"\\SVMDB1\admin$\setup.log" -e[vbcol=seagreen]
k=ClSec[vbcol=seagreen]
"\\SVMDB2\admin$\setup.log" -e[vbcol=seagreen]
setups.
>
|||Please check this one out
http://support.microsoft.com/default...;en-us;810343, sure sounds
promising.
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
http://msmvps.com/clustering - Blog
"Yong Zou (SearchIgnite)" <yz@.yz.com> wrote in message
news:%230lmyq55EHA.3828@.TK2MSFTNGP09.phx.gbl...
> Thanks Rod, I checked all of these, and looks like it still didn't solve
> my
> problem. Base onSQLSTPx.Log file,
> 14:53:12 C:\PROGRA~1\COMMON~1\MICROS~1\SQLDEB~1\sqldbreg.ex e -RegServer
> 14:53:12 Process Exit Code: (-2147312566) Error loading type library/DLL.
> I think this may be the cause of my issue, but don't know how to fix it
> Thanks again for your helps
> Yong
> "Rodney R. Fournier [MVP]" <rod@.die.spam.die.nw-america.com> wrote in
> message news:efnag445EHA.936@.TK2MSFTNGP12.phx.gbl...
> the
> 2003
> C:\WINNT\remsetup.ini
> C:\WINNT\remsetup.ini
> "\\SVMDB1\admin$\setup.log" -e
> k=ClSec
> "\\SVMDB2\admin$\setup.log" -e
> setups.
>
|||It might be time to call PSS.
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
http://msmvps.com/clustering - Blog
"Yong Zou (SearchIgnite)" <yz@.yz.com> wrote in message
news:OiAEC9D6EHA.1188@.tk2msftngp13.phx.gbl...
> Rod,
> Thanks again for your help. Still have problem.. Also this is happening
> before I apply SP3a. Any other suggestions?
> Yong
> "Rodney R. Fournier [MVP]" <rod@.die.spam.die.nw-america.com> wrote in
> message news:ukYtaZ75EHA.2540@.TK2MSFTNGP09.phx.gbl...
> sounds
> library/DLL.
> a
> k=Nb
> 0
> 0
>
|||Was one system an upgrade from Win 2000 and another one built from scratch?
The C:\WINNT folder is the old name. Windows server 2003 uses C:\Windows as
the default system folder name. Setup expects a parallel folder structure
on all nodes.
Also, make sure your TMP and TEMP system variables are set on all nodes to a
valid folder. Finally, log into the console of each node using all accounts
involoved (Setup Launch, Cluster, and SQL Service accounts.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Yong Zou (SearchIgnite)" <yz@.yz.com> wrote in message
news:eqpoTY35EHA.1596@.tk2msftngp13.phx.gbl...
> I am trying to setup SQL server on MS Cluster Servers (with window 2003
OS).
> I am always get following error during installation
> "Setup failed to perform the required operation on the cluster nodes"
> Base on sqlstp.log file (see below), it looks like cause by
> 10:35:07 C:\WINNT\TEMP\SqlSetup\Bin\remsetup.exe C:\WINNT\remsetup.ini
> 10:46:17 Process Exit Code: (2) The system cannot find the file specified.
> Does anyone know how to solve this issue?
> Thanks
> Yong
> 10:35:07 Setup is performing required operations on cluster nodes. This
may
> take a few minutes...
> 10:35:07 C:\WINNT\TEMP\SqlSetup\Bin\remsetup.exe C:\WINNT\remsetup.ini
> 10:46:17 Process Exit Code: (2) The system cannot find the file specified.
> 10:46:17 Begin Action : GetRemsetupRetCode
> 10:46:17 Installation return status on SVMDB1 : 0
> 10:46:17 Installation return status on SVMDB2 : 2
> 10:46:17 End Action : GetRemsetupRetCode
> #### SQL Server Remote Setup - Start Time 12/21/04 10:35:07 ####
> CThreadPool::RunUntilCompleteHlpr create thread, index=0
> CThread::Run thread [0x74] created for execution.
> CThread::Process [0x74]
> CThreadPool::RunUntilCompleteHlpr create thread, index=1
> Running '\\SVMDB1\N$\ENGLISH\SQL2000\ENT\x86\setup\setupsq l.exe k=Nb k=Rm
> k=Cl -SMS -s -f "\\SVMDB1\N$\ENGLISH\SQL2000\ENT\x86\setup\setup.i ns" -f1
> \\SVMDB1\admin$\SVMDB1_SVMOBILE.iss -f2 "\\SVMDB1\admin$\setup.log" -e
> "stpsilnt._ex" -b -x "C:\WINNT\TEMP\"' (SVMDB1) ...
> CThread::Run thread [0x78] created for execution.
> CThread::Process [0x78]
> CThreadPool::RunUntilCompleteHlpr start thread [0x74],index=0
> CThreadPool::RunUntilCompleteHlpr start thread [0x78],index=1
> Script file copied to '\\SVMDB2\ADMIN$\SVMDB2_SVMOBILE.iss' successfully.
> Installing remote service (SVMDB2)...
> Running '\\SVMDB1\N$\ENGLISH\SQL2000\ENT\x86\setup\setupsq l.exe k=ClSec
k=Rm
> k=Cl -SMS -s -f "\\SVMDB1\N$\ENGLISH\SQL2000\ENT\x86\setup\setup.i ns" -f1
> \\SVMDB2\ADMIN$\SVMDB2_SVMOBILE.iss -f2 "\\SVMDB2\admin$\setup.log" -e
> "stpsilnt._ex" -x "C:\"' (SVMDB2) ...
> CProcess::RunUntilComplete [0x74] exit code: 0
> Remote process exit code was '0' (SVMDB1).
> CThreadPool::RunUntilCompleteHlpr WaitForMultipleObjects returned: 0
> CThreadPool::RunUntilCompleteHlpr signaled thread [0x74]
> Thread [0x74] exit code: [0x0]
> CRemoteProcess::RunUntilComplete [0x78] exit code: 2
> Remote process exit code was '2' (SVMDB2).
> CThreadPool::RunUntilCompleteHlpr WaitForMultipleObjects returned: 0
> CThreadPool::RunUntilCompleteHlpr signaled thread [0x78]
> Thread [0x78] exit code: [0x2]
> CThreadPool::RunUntilComplete returned 2
> CThreadPool::RunUntilComplete execution level=1, need execution: 0
> One or more errors occurred while running the remote/unattended setups.
> Disconnecting from remote machine (SVMDB1)...
> Service removed successfully.
> Remote files could not be removed.
> #### SQL Server Remote Setup - Stop Time 12/21/04 10:45:59 ####
> Disconnecting from remote machine (SVMDB2)...
> Service removed successfully.
> Remote files removed successfully.
> #### SQL Server Remote Setup - Stop Time 12/21/04 10:46:16 ####
>