Cannot login into server after single user mode

Stopped the sqlserver agent first.

included -m option in the startup options of the SQL SERVER virtual server .

restarted the sql server ..

Now it is in single user mode.

after this I cannot do anything I cannot even right click on the server

" throws me error saying server in single user mode user cannot login"

Database is sqlserver 2000

os win2003

clustered 2 nodes.

rebooted the nodes , restarted the sql server many times tried login with sa, services running user account.

still cannot login into the server thru EM from outside and from server itself.

sql server agent cannot be brought up...

how do I overcome this now.........Need to bring the server in multiple user mode...

any suggestions will be greatly appriciated.

Thanks

Have you removed the -m from the startup options?

|||how to remove -m from the startup parameters is the q?....now don't tell me right click and change at the properties....I cannot right click on the server ..it says ..cannot login only one user can login as administrator|||

You don't need to access SQL Server to remove this option. You need to:

1. Open Computer Management

2. Expand Services And Applications.

3. Expand SQL Server 2005 Services.

4. Find your SQL Server service and double click it.

5. Click on the Advanced tab.

6. Find the property called 'Startup Parameters'.

You need to be a little careful here, maybe copy and paste it into notepad so you can see the entire string. Remove the -m from the string and click ok. You will need to stop and re-start the SQL Server service for the changes to take affect.

HTH

Ray

|||

dude,

you still didn't understand the problem here.......when you give -m option in the startup parameters ...you cannot even right click on the EM .....it will throw you error saying only one admin can login in single user mode.... even though you

reboot the servers/service/////////what ever...

solution I found in the internet today morning.... is

go and change the registry for the parameter settings:

it worked like a charm.......

Thanks

Sameer

Cannot login into server after single user mode

Stopped the sqlserver agent first.

included -m option in the startup options of the SQL SERVER virtual server .

restarted the sql server ..

Now it is in single user mode.

after this I cannot do anything I cannot even right click on the server

" throws me error saying server in single user mode user cannot login"

Database is sqlserver 2000

os win2003

clustered 2 nodes.

rebooted the nodes , restarted the sql server many times tried login with sa, services running user account.

still cannot login into the server thru EM from outside and from server itself.

sql server agent cannot be brought up...

how do I overcome this now.........Need to bring the server in multiple user mode...

any suggestions will be greatly appriciated.

Thanks

Have you removed the -m from the startup options?

|||how to remove -m from the startup parameters is the q?....now don't tell me right click and change at the properties....I cannot right click on the server ..it says ..cannot login only one user can login as administrator|||

You don't need to access SQL Server to remove this option. You need to:

1. Open Computer Management

2. Expand Services And Applications.

3. Expand SQL Server 2005 Services.

4. Find your SQL Server service and double click it.

5. Click on the Advanced tab.

6. Find the property called 'Startup Parameters'.

You need to be a little careful here, maybe copy and paste it into notepad so you can see the entire string. Remove the -m from the string and click ok. You will need to stop and re-start the SQL Server service for the changes to take affect.

HTH

Ray

|||

dude,

you still didn't understand the problem here.......when you give -m option in the startup parameters ...you cannot even right click on the EM .....it will throw you error saying only one admin can login in single user mode.... even though you

reboot the servers/service/////////what ever...

solution I found in the internet today morning.... is

go and change the registry for the parameter settings:

it worked like a charm.......

Thanks

Sameer

Cannot kill process

process with status runnable in MASTER db (waiting for lock shown in mmc).
as consequence, SQL Server agent is not starting anymore!
how can I kill this process?
master..sysobjects shows this process as non-blocked (blocked=0).
in tempdb the entry is shown with SPID #51 correponding to the running process
but it is not terminating since several days.
Thanks a lot in advance for help!Urban,
Try:
KILL <SPID> WITH STATUSONLY.
HTH
Jerry
"Urban" <urban@.nospamplease> wrote in message
news:7D887B89-D4DC-45E3-A2F3-2994CD423DA8@.microsoft.com...
> process with status runnable in MASTER db (waiting for lock shown in mmc).
> as consequence, SQL Server agent is not starting anymore!
> how can I kill this process?
> master..sysobjects shows this process as non-blocked (blocked=0).
> in tempdb the entry is shown with SPID #51 correponding to the running
> process
> but it is not terminating since several days.
> Thanks a lot in advance for help!
>|||process with status runnable in MASTER db (waiting for lock shown in mmc).
as consequence, SQL Server agent is not starting anymore!
how can I kill this process?
master..sysobjects shows this process as non-blocked (blocked=0).
in tempdb the entry is shown with SPID #51 correponding to the running process
but it is not terminating since several days.
SORRY, forgot to mention, that I tryed KILL 51, of course.
Thanks a lot in advance for help!|||Urban,
STATUSONLY will show you the estimated rollback completion. Is this a test
box, you could try stopping the SQL Server service and then starting the SQL
Server service then the SQL Server Agent service. Any errors reported in
either the SQL logs or the app event logs?
HTH
Jerry
"Urban" <urban@.nospamplease> wrote in message
news:CDE764AB-E274-4480-A61B-3A31C9BC0426@.microsoft.com...
> process with status runnable in MASTER db (waiting for lock shown in mmc).
> as consequence, SQL Server agent is not starting anymore!
> how can I kill this process?
> master..sysobjects shows this process as non-blocked (blocked=0).
> in tempdb the entry is shown with SPID #51 correponding to the running
> process
> but it is not terminating since several days.
> SORRY, forgot to mention, that I tryed KILL 51, of course.
>
> Thanks a lot in advance for help!
>|||Query analyser returns:
Status report cannot be obtained. Rollback operation for Process ID 51 is
not in progress.
Kill 51 is making the entries in tempd, but not killing the process.
"Jerry Spivey" wrote:
> Urban,
> Try:
> KILL <SPID> WITH STATUSONLY.
> HTH
> Jerry
> "Urban" <urban@.nospamplease> wrote in message
> news:7D887B89-D4DC-45E3-A2F3-2994CD423DA8@.microsoft.com...
> > process with status runnable in MASTER db (waiting for lock shown in mmc).
> > as consequence, SQL Server agent is not starting anymore!
> > how can I kill this process?
> > master..sysobjects shows this process as non-blocked (blocked=0).
> > in tempdb the entry is shown with SPID #51 correponding to the running
> > process
> > but it is not terminating since several days.
> >
> > Thanks a lot in advance for help!
> >
>
>|||Restart tried several times, even restatred machine.
No errors reported, Just that Process 51 has been killed, but is a true lie;-)
the process is still alive!
"Jerry Spivey" wrote:
> Urban,
> STATUSONLY will show you the estimated rollback completion. Is this a test
> box, you could try stopping the SQL Server service and then starting the SQL
> Server service then the SQL Server Agent service. Any errors reported in
> either the SQL logs or the app event logs?
> HTH
> Jerry
> "Urban" <urban@.nospamplease> wrote in message
> news:CDE764AB-E274-4480-A61B-3A31C9BC0426@.microsoft.com...
> > process with status runnable in MASTER db (waiting for lock shown in mmc).
> > as consequence, SQL Server agent is not starting anymore!
> > how can I kill this process?
> > master..sysobjects shows this process as non-blocked (blocked=0).
> > in tempdb the entry is shown with SPID #51 correponding to the running
> > process
> > but it is not terminating since several days.
> > SORRY, forgot to mention, that I tryed KILL 51, of course.
> >
> >
> > Thanks a lot in advance for help!
> >
>
>|||How are you looking that this? EM, current activity? Perhaps this is your connection that EM is
using to show you the information?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Urban" <urban@.nospamplease> wrote in message
news:7D887B89-D4DC-45E3-A2F3-2994CD423DA8@.microsoft.com...
> process with status runnable in MASTER db (waiting for lock shown in mmc).
> as consequence, SQL Server agent is not starting anymore!
> how can I kill this process?
> master..sysobjects shows this process as non-blocked (blocked=0).
> in tempdb the entry is shown with SPID #51 correponding to the running process
> but it is not terminating since several days.
> Thanks a lot in advance for help!
>|||Thanks a lot! I'm ashamed, you're right!!!!
It is indeed my own process. I didn't recognize, because I used the run as
command for mmc with the same user that is running SQL-Server, and not my
common user.
I understand, that the prozess is not allowed to kill itself. - Strange,
that it was alive for more than 10 days.
Meanwile, SQL Server Agent was able to start, after about 10 days. This I
don't understand. But even after restarting the databse it works fine.
Propably a problem when patching the server.
Anyway, you have solved my Problem, Tibor. Thanks a lot!
"Tibor Karaszi" wrote:
> How are you looking that this? EM, current activity? Perhaps this is your connection that EM is
> using to show you the information?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Urban" <urban@.nospamplease> wrote in message
> news:7D887B89-D4DC-45E3-A2F3-2994CD423DA8@.microsoft.com...
> > process with status runnable in MASTER db (waiting for lock shown in mmc).
> > as consequence, SQL Server agent is not starting anymore!
> > how can I kill this process?
> > master..sysobjects shows this process as non-blocked (blocked=0).
> > in tempdb the entry is shown with SPID #51 correponding to the running process
> > but it is not terminating since several days.
> >
> > Thanks a lot in advance for help!
> >
>

Cannot kill process

process with status runnable in MASTER db (waiting for lock shown in mmc).
as consequence, SQL Server agent is not starting anymore!
how can I kill this process?
master..sysobjects shows this process as non-blocked (blocked=0).
in tempdb the entry is shown with SPID #51 correponding to the running process
but it is not terminating since several days.
Thanks a lot in advance for help!
Urban,
Try:
KILL <SPID> WITH STATUSONLY.
HTH
Jerry
"Urban" <urban@.nospamplease> wrote in message
news:7D887B89-D4DC-45E3-A2F3-2994CD423DA8@.microsoft.com...
> process with status runnable in MASTER db (waiting for lock shown in mmc).
> as consequence, SQL Server agent is not starting anymore!
> how can I kill this process?
> master..sysobjects shows this process as non-blocked (blocked=0).
> in tempdb the entry is shown with SPID #51 correponding to the running
> process
> but it is not terminating since several days.
> Thanks a lot in advance for help!
>
|||process with status runnable in MASTER db (waiting for lock shown in mmc).
as consequence, SQL Server agent is not starting anymore!
how can I kill this process?
master..sysobjects shows this process as non-blocked (blocked=0).
in tempdb the entry is shown with SPID #51 correponding to the running process
but it is not terminating since several days.
SORRY, forgot to mention, that I tryed KILL 51, of course.
Thanks a lot in advance for help!
|||Urban,
STATUSONLY will show you the estimated rollback completion. Is this a test
box, you could try stopping the SQL Server service and then starting the SQL
Server service then the SQL Server Agent service. Any errors reported in
either the SQL logs or the app event logs?
HTH
Jerry
"Urban" <urban@.nospamplease> wrote in message
news:CDE764AB-E274-4480-A61B-3A31C9BC0426@.microsoft.com...
> process with status runnable in MASTER db (waiting for lock shown in mmc).
> as consequence, SQL Server agent is not starting anymore!
> how can I kill this process?
> master..sysobjects shows this process as non-blocked (blocked=0).
> in tempdb the entry is shown with SPID #51 correponding to the running
> process
> but it is not terminating since several days.
> SORRY, forgot to mention, that I tryed KILL 51, of course.
>
> Thanks a lot in advance for help!
>
|||Query analyser returns:
Status report cannot be obtained. Rollback operation for Process ID 51 is
not in progress.
Kill 51 is making the entries in tempd, but not killing the process.
"Jerry Spivey" wrote:

> Urban,
> Try:
> KILL <SPID> WITH STATUSONLY.
> HTH
> Jerry
> "Urban" <urban@.nospamplease> wrote in message
> news:7D887B89-D4DC-45E3-A2F3-2994CD423DA8@.microsoft.com...
>
>
|||Restart tried several times, even restatred machine.
No errors reported, Just that Process 51 has been killed, but is a true lie;-)
the process is still alive!
"Jerry Spivey" wrote:

> Urban,
> STATUSONLY will show you the estimated rollback completion. Is this a test
> box, you could try stopping the SQL Server service and then starting the SQL
> Server service then the SQL Server Agent service. Any errors reported in
> either the SQL logs or the app event logs?
> HTH
> Jerry
> "Urban" <urban@.nospamplease> wrote in message
> news:CDE764AB-E274-4480-A61B-3A31C9BC0426@.microsoft.com...
>
>
|||How are you looking that this? EM, current activity? Perhaps this is your connection that EM is
using to show you the information?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Urban" <urban@.nospamplease> wrote in message
news:7D887B89-D4DC-45E3-A2F3-2994CD423DA8@.microsoft.com...
> process with status runnable in MASTER db (waiting for lock shown in mmc).
> as consequence, SQL Server agent is not starting anymore!
> how can I kill this process?
> master..sysobjects shows this process as non-blocked (blocked=0).
> in tempdb the entry is shown with SPID #51 correponding to the running process
> but it is not terminating since several days.
> Thanks a lot in advance for help!
>
|||Thanks a lot! I'm ashamed, you're right!!!!
It is indeed my own process. I didn't recognize, because I used the run as
command for mmc with the same user that is running SQL-Server, and not my
common user.
I understand, that the prozess is not allowed to kill itself. - Strange,
that it was alive for more than 10 days.
Meanwile, SQL Server Agent was able to start, after about 10 days. This I
don't understand. But even after restarting the databse it works fine.
Propably a problem when patching the server.
Anyway, you have solved my Problem, Tibor. Thanks a lot!
"Tibor Karaszi" wrote:

> How are you looking that this? EM, current activity? Perhaps this is your connection that EM is
> using to show you the information?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Urban" <urban@.nospamplease> wrote in message
> news:7D887B89-D4DC-45E3-A2F3-2994CD423DA8@.microsoft.com...
>

Cannot kill process

process with status runnable in MASTER db (waiting for lock shown in mmc).
as consequence, SQL Server agent is not starting anymore!
how can I kill this process?
master..sysobjects shows this process as non-blocked (blocked=0).
in tempdb the entry is shown with SPID #51 correponding to the running proce
ss
but it is not terminating since several days.
Thanks a lot in advance for help!Urban,
Try:
KILL <SPID> WITH STATUSONLY.
HTH
Jerry
"Urban" <urban@.nospamplease> wrote in message
news:7D887B89-D4DC-45E3-A2F3-2994CD423DA8@.microsoft.com...
> process with status runnable in MASTER db (waiting for lock shown in mmc).
> as consequence, SQL Server agent is not starting anymore!
> how can I kill this process?
> master..sysobjects shows this process as non-blocked (blocked=0).
> in tempdb the entry is shown with SPID #51 correponding to the running
> process
> but it is not terminating since several days.
> Thanks a lot in advance for help!
>|||process with status runnable in MASTER db (waiting for lock shown in mmc).
as consequence, SQL Server agent is not starting anymore!
how can I kill this process?
master..sysobjects shows this process as non-blocked (blocked=0).
in tempdb the entry is shown with SPID #51 correponding to the running proce
ss
but it is not terminating since several days.
SORRY, forgot to mention, that I tryed KILL 51, of course.
Thanks a lot in advance for help!|||Urban,
STATUSONLY will show you the estimated rollback completion. Is this a test
box, you could try stopping the SQL Server service and then starting the SQL
Server service then the SQL Server Agent service. Any errors reported in
either the SQL logs or the app event logs?
HTH
Jerry
"Urban" <urban@.nospamplease> wrote in message
news:CDE764AB-E274-4480-A61B-3A31C9BC0426@.microsoft.com...
> process with status runnable in MASTER db (waiting for lock shown in mmc).
> as consequence, SQL Server agent is not starting anymore!
> how can I kill this process?
> master..sysobjects shows this process as non-blocked (blocked=0).
> in tempdb the entry is shown with SPID #51 correponding to the running
> process
> but it is not terminating since several days.
> SORRY, forgot to mention, that I tryed KILL 51, of course.
>
> Thanks a lot in advance for help!
>|||Query analyser returns:
Status report cannot be obtained. Rollback operation for Process ID 51 is
not in progress.
Kill 51 is making the entries in tempd, but not killing the process.
"Jerry Spivey" wrote:

> Urban,
> Try:
> KILL <SPID> WITH STATUSONLY.
> HTH
> Jerry
> "Urban" <urban@.nospamplease> wrote in message
> news:7D887B89-D4DC-45E3-A2F3-2994CD423DA8@.microsoft.com...
>
>|||Restart tried several times, even restatred machine.
No errors reported, Just that Process 51 has been killed, but is a true lie;
-)
the process is still alive!
"Jerry Spivey" wrote:

> Urban,
> STATUSONLY will show you the estimated rollback completion. Is this a tes
t
> box, you could try stopping the SQL Server service and then starting the S
QL
> Server service then the SQL Server Agent service. Any errors reported in
> either the SQL logs or the app event logs?
> HTH
> Jerry
> "Urban" <urban@.nospamplease> wrote in message
> news:CDE764AB-E274-4480-A61B-3A31C9BC0426@.microsoft.com...
>
>|||How are you looking that this? EM, current activity? Perhaps this is your co
nnection that EM is
using to show you the information?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Urban" <urban@.nospamplease> wrote in message
news:7D887B89-D4DC-45E3-A2F3-2994CD423DA8@.microsoft.com...
> process with status runnable in MASTER db (waiting for lock shown in mmc).
> as consequence, SQL Server agent is not starting anymore!
> how can I kill this process?
> master..sysobjects shows this process as non-blocked (blocked=0).
> in tempdb the entry is shown with SPID #51 correponding to the running pro
cess
> but it is not terminating since several days.
> Thanks a lot in advance for help!
>|||Thanks a lot! I'm ashamed, you're right!!!!
It is indeed my own process. I didn't recognize, because I used the run as
command for mmc with the same user that is running SQL-Server, and not my
common user.
I understand, that the prozess is not allowed to kill itself. - Strange,
that it was alive for more than 10 days.
Meanwile, SQL Server Agent was able to start, after about 10 days. This I
don't understand. But even after restarting the databse it works fine.
Propably a problem when patching the server.
Anyway, you have solved my Problem, Tibor. Thanks a lot!
"Tibor Karaszi" wrote:

> How are you looking that this? EM, current activity? Perhaps this is your
connection that EM is
> using to show you the information?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Urban" <urban@.nospamplease> wrote in message
> news:7D887B89-D4DC-45E3-A2F3-2994CD423DA8@.microsoft.com...
>

Cannot install SQL Server 2005 Standard WinXP Pro SP2

Hello,

I have SQL Server 2000 Developer Edition already installed. Before starting
the SQL Server 2005 Standard setup, I exited the SQL server agent running in
my system tray.

I am logged on as Administrator and no other desktop apps are running. SQL
Server 2005 Setup reports several "Setup failed." error messages after the
install. I am choosing (for now) ONLY the workstation tools and books online
check mark. The installation presents a screen that says that these products
were successfully installed ("Setup finished"):
- MSXML6
- OWC11
- SQL Server Backward-Compatibility Files
However, these items have a red x next to them:
- SQL Server Books Online
- SQL Server Support Files
- SQLXML4
- SQL Native Client
- Workstation Components, Books Online, ...

My Setup log file terminates with a few messages--one of which contains the
words "Configuration failed." (This is the ONLY mention of the word "fail" in
the Setup log--see the excerpt below.)

Any ideas? I'm stuck without SQL Server 2005 running so this is a
productivity killer for me.

More info: Here is what I have done, to no avail:

1) Installed the OWC11 components using a direct download from Microsoft.
That install worked. But when it runs again from the SQL Server 2005 DVD, it
fails.
2) Logged on not as a user with Admin rights, but as ADMINISTRATOR. Same
results--the SQL Server 2005 Standard setup failed.
3) Installed SQL Server 2005 Express successfully. Afterwards, tried again
to install SQL Server 2005 Standard, and that setup failed.
4) Cleared registry values for SQL Server 2005 under HKLM.../Software as
described in KB article. Also deleted the installation folder ...90. Tried
again to install SQL Server 2005 Standard, and that setup failed.
5) Tried the 180-day trial of SQL Server 2005 Enterprise--to no avail. Same
results.

Found error logs but they did not help me pinpoint the root cause for the
failed installation.

Thank you,
-- Jonathan

SQLSetup0004_zzzzz_SQLNCLI_1.log Excerpt:
============================+
MSI (s) (60:90) [12:01:14:390]: Note: 1: 1729
MSI (s) (60:90) [12:01:14:406]: Product: Microsoft SQL Server Native Client
-- Configuration failed.

MSI (s) (60:90) [12:01:14:406]: Cleaning up uninstalled install packages, if
any exist
MSI (s) (60:90) [12:01:14:406]: MainEngineThread is returning 1603
MSI (s) (60:68) [12:01:14:406]: Destroying RemoteAPI object.
MSI (s) (60:9C) [12:01:14:406]: Custom Action Manager thread ending.
=== Logging stopped: 2/8/2007 12:01:14 ===
MSI (c) (8C:4C) [12:01:14:406]: Decrementing counter to disable shutdown. If
counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (8C:4C) [12:01:14:406]: MainEngineThread is returning 1603
=== Verbose logging stopped: 2/8/2007 12:01:14 ===

As a first check have you disabled Anti-virus and Anti-firewall before installing?|||

Yes, anti-virus software is OFF and my XP Firewall is OFF.

I re-ran SQL Server 2005 Standard Setup, and here is some more information.

Setup Support files install properly.
Installation Wizard begins.
Status of ALL requirements is "Success".
Windows Installer launches.
I click Next on Serial Number screen after completing the form.
In Components to Install, I select only "Workstation components, Books Online and development tools"
A screen acknowledges that only Client Components will be installed.
I click Install.
A status dialog appears. Setup clearly begins to install files. Then it shows, one-by-one:

1. SQL Setup Support Files FAILED.
2. SQL Native Client FAILED.
3. OWC11 Setup finished.
4. Then I see "Removing backup files"
5. Then Sql Server Books Online failed, along with other failed statuses.

Any ideas?

|||

OK--If anyone cannot help on Microsoft TechNet, can anyone point me in the right direction on how to solve this issue?

1) Are there other web sites that might offer help?

2) Will Microsoft charge an incident fee for this issue since it appears to be a problem with Setup?

3) Does anyone have any suggestions?

This machine has Visual Studio 2003, Visual Studio 6, Macromedia 8, Adobe Photoshop CS2, IE7, and several other high-end products, such as InstallShield 12 Premium. All of those installed and are running without incident.

I can't imagine why SQL Server 2005 setup can't detect what's wrong and provide a successful installation.

Thank you.

|||Install sqlncli.msi before installing mssql2005.|||

Hello:

I ran the sqlncli.msi and received an error that I had a higher version already installed on my machine. I then used Add/Remove programs to remove the SQL Native Client--and then I re-ran sqlncli.msi successfully.

I then re-ran SQL Server 2005 Standard setup and received all the same installation errors already reported.

What now?

|||

I'm contacting Microsoft Support. I thank you for those who tried to help but it is a bit ridiculous to have a support group that can't even troubleshoot getting the product installed!

I will report the root cause here (if Microsoft is able to figure it out).

Thank you,

Jon500

Cannot install SQL Server 2005 Standard WinXP Pro SP2

Hello,

I have SQL Server 2000 Developer Edition already installed. Before starting
the SQL Server 2005 Standard setup, I exited the SQL server agent running in
my system tray.

I am logged on as Administrator and no other desktop apps are running. SQL
Server 2005 Setup reports several "Setup failed." error messages after the
install. I am choosing (for now) ONLY the workstation tools and books online
check mark. The installation presents a screen that says that these products
were successfully installed ("Setup finished"):
- MSXML6
- OWC11
- SQL Server Backward-Compatibility Files
However, these items have a red x next to them:
- SQL Server Books Online
- SQL Server Support Files
- SQLXML4
- SQL Native Client
- Workstation Components, Books Online, ...

My Setup log file terminates with a few messages--one of which contains the
words "Configuration failed." (This is the ONLY mention of the word "fail" in
the Setup log--see the excerpt below.)

Any ideas? I'm stuck without SQL Server 2005 running so this is a
productivity killer for me.

More info: Here is what I have done, to no avail:

1) Installed the OWC11 components using a direct download from Microsoft.
That install worked. But when it runs again from the SQL Server 2005 DVD, it
fails.
2) Logged on not as a user with Admin rights, but as ADMINISTRATOR. Same
results--the SQL Server 2005 Standard setup failed.
3) Installed SQL Server 2005 Express successfully. Afterwards, tried again
to install SQL Server 2005 Standard, and that setup failed.
4) Cleared registry values for SQL Server 2005 under HKLM.../Software as
described in KB article. Also deleted the installation folder ...90. Tried
again to install SQL Server 2005 Standard, and that setup failed.
5) Tried the 180-day trial of SQL Server 2005 Enterprise--to no avail. Same
results.

Found error logs but they did not help me pinpoint the root cause for the
failed installation.

Thank you,
-- Jonathan

SQLSetup0004_zzzzz_SQLNCLI_1.log Excerpt:
============================+
MSI (s) (60:90) [12:01:14:390]: Note: 1: 1729
MSI (s) (60:90) [12:01:14:406]: Product: Microsoft SQL Server Native Client
-- Configuration failed.

MSI (s) (60:90) [12:01:14:406]: Cleaning up uninstalled install packages, if
any exist
MSI (s) (60:90) [12:01:14:406]: MainEngineThread is returning 1603
MSI (s) (60:68) [12:01:14:406]: Destroying RemoteAPI object.
MSI (s) (60:9C) [12:01:14:406]: Custom Action Manager thread ending.
=== Logging stopped: 2/8/2007 12:01:14 ===
MSI (c) (8C:4C) [12:01:14:406]: Decrementing counter to disable shutdown. If
counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (8C:4C) [12:01:14:406]: MainEngineThread is returning 1603
=== Verbose logging stopped: 2/8/2007 12:01:14 ===

As a first check have you disabled Anti-virus and Anti-firewall before installing?|||

Yes, anti-virus software is OFF and my XP Firewall is OFF.

I re-ran SQL Server 2005 Standard Setup, and here is some more information.

Setup Support files install properly.
Installation Wizard begins.
Status of ALL requirements is "Success".
Windows Installer launches.
I click Next on Serial Number screen after completing the form.
In Components to Install, I select only "Workstation components, Books Online and development tools"
A screen acknowledges that only Client Components will be installed.
I click Install.
A status dialog appears. Setup clearly begins to install files. Then it shows, one-by-one:

1. SQL Setup Support Files FAILED.
2. SQL Native Client FAILED.
3. OWC11 Setup finished.
4. Then I see "Removing backup files"
5. Then Sql Server Books Online failed, along with other failed statuses.

Any ideas?

|||

OK--If anyone cannot help on Microsoft TechNet, can anyone point me in the right direction on how to solve this issue?

1) Are there other web sites that might offer help?

2) Will Microsoft charge an incident fee for this issue since it appears to be a problem with Setup?

3) Does anyone have any suggestions?

This machine has Visual Studio 2003, Visual Studio 6, Macromedia 8, Adobe Photoshop CS2, IE7, and several other high-end products, such as InstallShield 12 Premium. All of those installed and are running without incident.

I can't imagine why SQL Server 2005 setup can't detect what's wrong and provide a successful installation.

Thank you.

|||Install sqlncli.msi before installing mssql2005.|||

Hello:

I ran the sqlncli.msi and received an error that I had a higher version already installed on my machine. I then used Add/Remove programs to remove the SQL Native Client--and then I re-ran sqlncli.msi successfully.

I then re-ran SQL Server 2005 Standard setup and received all the same installation errors already reported.

What now?

|||

I'm contacting Microsoft Support. I thank you for those who tried to help but it is a bit ridiculous to have a support group that can't even troubleshoot getting the product installed!

I will report the root cause here (if Microsoft is able to figure it out).

Thank you,

Jon500

Cannot get proxy account to work.

For some reason I cannot get a job to run under a different account other
than the SQL Agent. What I have done is the following.
1)Created a credential called operations that has the domain\user format
with its password. The user used is the SA of the sql server.
2)I created a proxy that is linked to this credential. In this Proxy I have
set it up to run all subsystems. I have also linked two users to this proxy.
3)I changed the job owner to be a user that will use the proxy
4)I changed each job step to run as the proxy created.
When I run the job, the job instantly fails. I keep getting the following
error.
Executed as user: DOMAIN\user. The process could not be created for step 1
of job 0x34E60C35C09E184EA8FD2E9E223821E2 (reason: A required privilege is
not held by the client). The step failed.
At one time this worked great. I believe this broke because of an update
that was applied.
I have recreated the credential and the proxy several times and I cannot see
what I am doing wrong.
Can anyone help me.
Hi Chris, please take a look at this tip on what to take care of when running
a SQL Server Agent job using a proxy account:
http://www.sqlcommunity.com/Default.aspx?id=97&tabid=77
Thank you,
Saleem Hakani
HTTP://WWW.SQLCOMMUNITY.COM (SQL Server Community)
SQLTips, SQL Forums, SQL Blogs, SQL RADIO, SQL Events, SQL Scripts, SQL
Articles, SQL Clinic and a lot of SQL fun.
"Chris Lumnah" wrote:

> For some reason I cannot get a job to run under a different account other
> than the SQL Agent. What I have done is the following.
> 1)Created a credential called operations that has the domain\user format
> with its password. The user used is the SA of the sql server.
> 2)I created a proxy that is linked to this credential. In this Proxy I have
> set it up to run all subsystems. I have also linked two users to this proxy.
> 3)I changed the job owner to be a user that will use the proxy
> 4)I changed each job step to run as the proxy created.
> When I run the job, the job instantly fails. I keep getting the following
> error.
> Executed as user: DOMAIN\user. The process could not be created for step 1
> of job 0x34E60C35C09E184EA8FD2E9E223821E2 (reason: A required privilege is
> not held by the client). The step failed.
> At one time this worked great. I believe this broke because of an update
> that was applied.
> I have recreated the credential and the proxy several times and I cannot see
> what I am doing wrong.
> Can anyone help me.
|||Thank you for the reply. I will try this out. Is this aimed at the SQL
Agent Service account or the proxy account? Should I apply it to both?
Thanks again.
"Saleem Hakani" wrote:
[vbcol=seagreen]
> Hi Chris, please take a look at this tip on what to take care of when running
> a SQL Server Agent job using a proxy account:
> http://www.sqlcommunity.com/Default.aspx?id=97&tabid=77
> --
> Thank you,
> Saleem Hakani
> HTTP://WWW.SQLCOMMUNITY.COM (SQL Server Community)
> SQLTips, SQL Forums, SQL Blogs, SQL RADIO, SQL Events, SQL Scripts, SQL
> Articles, SQL Clinic and a lot of SQL fun.
>
> "Chris Lumnah" wrote:
|||That's correct Chris. It's for SQL Server Agent service but you can applyit
for both as well.
Thank you,
Saleem Hakani
HTTP://WWW.SQLCOMMUNITY.COM (SQL Server Community)
SQLTips, SQL Forums, SQL Blogs, SQL RADIO, SQL Events, SQL Scripts, SQL
Articles, SQL Clinic and a lot of SQL fun.
"Chris Lumnah" wrote:
[vbcol=seagreen]
> Thank you for the reply. I will try this out. Is this aimed at the SQL
> Agent Service account or the proxy account? Should I apply it to both?
> Thanks again.
> "Saleem Hakani" wrote:
|||Saleem,
I have done what you suggested. However I still have the same problem. I
did all the items on that list, short of rebooting the server. Any other
ideas?
"Saleem Hakani" wrote:
[vbcol=seagreen]
> That's correct Chris. It's for SQL Server Agent service but you can applyit
> for both as well.
> --
> Thank you,
> Saleem Hakani
> HTTP://WWW.SQLCOMMUNITY.COM (SQL Server Community)
> SQLTips, SQL Forums, SQL Blogs, SQL RADIO, SQL Events, SQL Scripts, SQL
> Articles, SQL Clinic and a lot of SQL fun.
>
> "Chris Lumnah" wrote:

Cannot get proxy account to work.

For some reason I cannot get a job to run under a different account other
than the SQL Agent. What I have done is the following.
1)Created a credential called operations that has the domain\user format
with its password. The user used is the SA of the sql server.
2)I created a proxy that is linked to this credential. In this Proxy I have
set it up to run all subsystems. I have also linked two users to this proxy
.
3)I changed the job owner to be a user that will use the proxy
4)I changed each job step to run as the proxy created.
When I run the job, the job instantly fails. I keep getting the following
error.
Executed as user: DOMAIN\user. The process could not be created for step 1
of job 0x34E60C35C09E184EA8FD2E9E223821E2 (reason: A required privilege is
not held by the client). The step failed.
At one time this worked great. I believe this broke because of an update
that was applied.
I have recreated the credential and the proxy several times and I cannot see
what I am doing wrong.
Can anyone help me.Hi Chris, please take a look at this tip on what to take care of when runnin
g
a SQL Server Agent job using a proxy account:
http://www.sqlcommunity.com/Default.aspx?id=97&tabid=77
Thank you,
Saleem Hakani
HTTP://WWW.SQLCOMMUNITY.COM (SQL Server Community)
SQLTips, SQL Forums, SQL Blogs, SQL RADIO, SQL Events, SQL Scripts, SQL
Articles, SQL Clinic and a lot of SQL fun.
"Chris Lumnah" wrote:

> For some reason I cannot get a job to run under a different account other
> than the SQL Agent. What I have done is the following.
> 1)Created a credential called operations that has the domain\user format
> with its password. The user used is the SA of the sql server.
> 2)I created a proxy that is linked to this credential. In this Proxy I ha
ve
> set it up to run all subsystems. I have also linked two users to this pro
xy.
> 3)I changed the job owner to be a user that will use the proxy
> 4)I changed each job step to run as the proxy created.
> When I run the job, the job instantly fails. I keep getting the following
> error.
> Executed as user: DOMAIN\user. The process could not be created for step 1
> of job 0x34E60C35C09E184EA8FD2E9E223821E2 (reason: A required privilege is
> not held by the client). The step failed.
> At one time this worked great. I believe this broke because of an update
> that was applied.
> I have recreated the credential and the proxy several times and I cannot s
ee
> what I am doing wrong.
> Can anyone help me.|||Thank you for the reply. I will try this out. Is this aimed at the SQL
Agent Service account or the proxy account? Should I apply it to both?
Thanks again.
"Saleem Hakani" wrote:
[vbcol=seagreen]
> Hi Chris, please take a look at this tip on what to take care of when runn
ing
> a SQL Server Agent job using a proxy account:
> http://www.sqlcommunity.com/Default.aspx?id=97&tabid=77
> --
> Thank you,
> Saleem Hakani
> HTTP://WWW.SQLCOMMUNITY.COM (SQL Server Community)
> SQLTips, SQL Forums, SQL Blogs, SQL RADIO, SQL Events, SQL Scripts, SQL
> Articles, SQL Clinic and a lot of SQL fun.
>
> "Chris Lumnah" wrote:
>|||That's correct Chris. It's for SQL Server Agent service but you can applyit
for both as well.
Thank you,
Saleem Hakani
HTTP://WWW.SQLCOMMUNITY.COM (SQL Server Community)
SQLTips, SQL Forums, SQL Blogs, SQL RADIO, SQL Events, SQL Scripts, SQL
Articles, SQL Clinic and a lot of SQL fun.
"Chris Lumnah" wrote:
[vbcol=seagreen]
> Thank you for the reply. I will try this out. Is this aimed at the SQL
> Agent Service account or the proxy account? Should I apply it to both?
> Thanks again.
> "Saleem Hakani" wrote:
>|||Saleem,
I have done what you suggested. However I still have the same problem. I
did all the items on that list, short of rebooting the server. Any other
ideas?
"Saleem Hakani" wrote:
[vbcol=seagreen]
> That's correct Chris. It's for SQL Server Agent service but you can applyi
t
> for both as well.
> --
> Thank you,
> Saleem Hakani
> HTTP://WWW.SQLCOMMUNITY.COM (SQL Server Community)
> SQLTips, SQL Forums, SQL Blogs, SQL RADIO, SQL Events, SQL Scripts, SQL
> Articles, SQL Clinic and a lot of SQL fun.
>
> "Chris Lumnah" wrote:
>

Cannot get proxy account to work.

For some reason I cannot get a job to run under a different account other
than the SQL Agent. What I have done is the following.
1)Created a credential called operations that has the domain\user format
with its password. The user used is the SA of the sql server.
2)I created a proxy that is linked to this credential. In this Proxy I have
set it up to run all subsystems. I have also linked two users to this proxy.
3)I changed the job owner to be a user that will use the proxy
4)I changed each job step to run as the proxy created.
When I run the job, the job instantly fails. I keep getting the following
error.
Executed as user: DOMAIN\user. The process could not be created for step 1
of job 0x34E60C35C09E184EA8FD2E9E223821E2 (reason: A required privilege is
not held by the client). The step failed.
At one time this worked great. I believe this broke because of an update
that was applied.
I have recreated the credential and the proxy several times and I cannot see
what I am doing wrong.
Can anyone help me.Hi Chris, please take a look at this tip on what to take care of when running
a SQL Server Agent job using a proxy account:
http://www.sqlcommunity.com/Default.aspx?id=97&tabid=77
--
Thank you,
Saleem Hakani
HTTP://WWW.SQLCOMMUNITY.COM (SQL Server Community)
SQLTips, SQL Forums, SQL Blogs, SQL RADIO, SQL Events, SQL Scripts, SQL
Articles, SQL Clinic and a lot of SQL fun.
"Chris Lumnah" wrote:
> For some reason I cannot get a job to run under a different account other
> than the SQL Agent. What I have done is the following.
> 1)Created a credential called operations that has the domain\user format
> with its password. The user used is the SA of the sql server.
> 2)I created a proxy that is linked to this credential. In this Proxy I have
> set it up to run all subsystems. I have also linked two users to this proxy.
> 3)I changed the job owner to be a user that will use the proxy
> 4)I changed each job step to run as the proxy created.
> When I run the job, the job instantly fails. I keep getting the following
> error.
> Executed as user: DOMAIN\user. The process could not be created for step 1
> of job 0x34E60C35C09E184EA8FD2E9E223821E2 (reason: A required privilege is
> not held by the client). The step failed.
> At one time this worked great. I believe this broke because of an update
> that was applied.
> I have recreated the credential and the proxy several times and I cannot see
> what I am doing wrong.
> Can anyone help me.|||Thank you for the reply. I will try this out. Is this aimed at the SQL
Agent Service account or the proxy account? Should I apply it to both?
Thanks again.
"Saleem Hakani" wrote:
> Hi Chris, please take a look at this tip on what to take care of when running
> a SQL Server Agent job using a proxy account:
> http://www.sqlcommunity.com/Default.aspx?id=97&tabid=77
> --
> Thank you,
> Saleem Hakani
> HTTP://WWW.SQLCOMMUNITY.COM (SQL Server Community)
> SQLTips, SQL Forums, SQL Blogs, SQL RADIO, SQL Events, SQL Scripts, SQL
> Articles, SQL Clinic and a lot of SQL fun.
>
> "Chris Lumnah" wrote:
> > For some reason I cannot get a job to run under a different account other
> > than the SQL Agent. What I have done is the following.
> > 1)Created a credential called operations that has the domain\user format
> > with its password. The user used is the SA of the sql server.
> >
> > 2)I created a proxy that is linked to this credential. In this Proxy I have
> > set it up to run all subsystems. I have also linked two users to this proxy.
> >
> > 3)I changed the job owner to be a user that will use the proxy
> >
> > 4)I changed each job step to run as the proxy created.
> >
> > When I run the job, the job instantly fails. I keep getting the following
> > error.
> >
> > Executed as user: DOMAIN\user. The process could not be created for step 1
> > of job 0x34E60C35C09E184EA8FD2E9E223821E2 (reason: A required privilege is
> > not held by the client). The step failed.
> >
> > At one time this worked great. I believe this broke because of an update
> > that was applied.
> >
> > I have recreated the credential and the proxy several times and I cannot see
> > what I am doing wrong.
> >
> > Can anyone help me.|||That's correct Chris. It's for SQL Server Agent service but you can applyit
for both as well.
--
Thank you,
Saleem Hakani
HTTP://WWW.SQLCOMMUNITY.COM (SQL Server Community)
SQLTips, SQL Forums, SQL Blogs, SQL RADIO, SQL Events, SQL Scripts, SQL
Articles, SQL Clinic and a lot of SQL fun.
"Chris Lumnah" wrote:
> Thank you for the reply. I will try this out. Is this aimed at the SQL
> Agent Service account or the proxy account? Should I apply it to both?
> Thanks again.
> "Saleem Hakani" wrote:
> > Hi Chris, please take a look at this tip on what to take care of when running
> > a SQL Server Agent job using a proxy account:
> > http://www.sqlcommunity.com/Default.aspx?id=97&tabid=77
> >
> > --
> > Thank you,
> > Saleem Hakani
> > HTTP://WWW.SQLCOMMUNITY.COM (SQL Server Community)
> > SQLTips, SQL Forums, SQL Blogs, SQL RADIO, SQL Events, SQL Scripts, SQL
> > Articles, SQL Clinic and a lot of SQL fun.
> >
> >
> >
> > "Chris Lumnah" wrote:
> >
> > > For some reason I cannot get a job to run under a different account other
> > > than the SQL Agent. What I have done is the following.
> > > 1)Created a credential called operations that has the domain\user format
> > > with its password. The user used is the SA of the sql server.
> > >
> > > 2)I created a proxy that is linked to this credential. In this Proxy I have
> > > set it up to run all subsystems. I have also linked two users to this proxy.
> > >
> > > 3)I changed the job owner to be a user that will use the proxy
> > >
> > > 4)I changed each job step to run as the proxy created.
> > >
> > > When I run the job, the job instantly fails. I keep getting the following
> > > error.
> > >
> > > Executed as user: DOMAIN\user. The process could not be created for step 1
> > > of job 0x34E60C35C09E184EA8FD2E9E223821E2 (reason: A required privilege is
> > > not held by the client). The step failed.
> > >
> > > At one time this worked great. I believe this broke because of an update
> > > that was applied.
> > >
> > > I have recreated the credential and the proxy several times and I cannot see
> > > what I am doing wrong.
> > >
> > > Can anyone help me.|||Saleem,
I have done what you suggested. However I still have the same problem. I
did all the items on that list, short of rebooting the server. Any other
ideas?
"Saleem Hakani" wrote:
> That's correct Chris. It's for SQL Server Agent service but you can applyit
> for both as well.
> --
> Thank you,
> Saleem Hakani
> HTTP://WWW.SQLCOMMUNITY.COM (SQL Server Community)
> SQLTips, SQL Forums, SQL Blogs, SQL RADIO, SQL Events, SQL Scripts, SQL
> Articles, SQL Clinic and a lot of SQL fun.
>
> "Chris Lumnah" wrote:
> > Thank you for the reply. I will try this out. Is this aimed at the SQL
> > Agent Service account or the proxy account? Should I apply it to both?
> >
> > Thanks again.
> >
> > "Saleem Hakani" wrote:
> >
> > > Hi Chris, please take a look at this tip on what to take care of when running
> > > a SQL Server Agent job using a proxy account:
> > > http://www.sqlcommunity.com/Default.aspx?id=97&tabid=77
> > >
> > > --
> > > Thank you,
> > > Saleem Hakani
> > > HTTP://WWW.SQLCOMMUNITY.COM (SQL Server Community)
> > > SQLTips, SQL Forums, SQL Blogs, SQL RADIO, SQL Events, SQL Scripts, SQL
> > > Articles, SQL Clinic and a lot of SQL fun.
> > >
> > >
> > >
> > > "Chris Lumnah" wrote:
> > >
> > > > For some reason I cannot get a job to run under a different account other
> > > > than the SQL Agent. What I have done is the following.
> > > > 1)Created a credential called operations that has the domain\user format
> > > > with its password. The user used is the SA of the sql server.
> > > >
> > > > 2)I created a proxy that is linked to this credential. In this Proxy I have
> > > > set it up to run all subsystems. I have also linked two users to this proxy.
> > > >
> > > > 3)I changed the job owner to be a user that will use the proxy
> > > >
> > > > 4)I changed each job step to run as the proxy created.
> > > >
> > > > When I run the job, the job instantly fails. I keep getting the following
> > > > error.
> > > >
> > > > Executed as user: DOMAIN\user. The process could not be created for step 1
> > > > of job 0x34E60C35C09E184EA8FD2E9E223821E2 (reason: A required privilege is
> > > > not held by the client). The step failed.
> > > >
> > > > At one time this worked great. I believe this broke because of an update
> > > > that was applied.
> > > >
> > > > I have recreated the credential and the proxy several times and I cannot see
> > > > what I am doing wrong.
> > > >
> > > > Can anyone help me.

Cannot fine the object “MSmerge_ctsv_... Because it does not exists or you do not have permissio

I keep getting the following error message during the initial merge agent.

· “The merge process was unable to deliver the snapshot to the subscriber.If using Web synchronization, the merge process may have been unable to create or write the message file, when troubleshooting, restart the sychronzation with verbose history loggin and specify an output file to write.

· Cannot fine the object “MSmerge_ctsv_B5ECD41086F24A64B8040A41A75B2DC4”, Because it does not exists or you do not have permission.(source: MSSQLServer, Error number 15151)

I do see this view in the publication and if I run the following command on the publisher I get…

select * from Msmerge_ctsv_B5ECD41086F24A64B8040A41A75B2DC4

I get

tablenick rowguid generation partchangegen lineage colv1 marker logical_record_parent_rowguid logical_record_lineage

(0 row(s) affected)

I have another publication working on this same server that is working, both are from a copy from a template database.Please advise to what this problem could be and what I can do to resolve this.

Thank you,

Pauly C

The issue was the mobile server name was changed but not dropped and re-added back so the values of@.@.servername and serverproperty(‘servername’) did not match. Once I fixed this everything replicated fine. Not a very intuitive error but if the error returns somethign like "Cannot fine the object “MSmerge_ctsv_..." check the subscriber server name by running

select @.@.servername as oldservername, serverproperty('servername') as newservername, case when @.@.servername <> serverproperty('servername') then '*** Error - Server name changed, replication will not work' else 'Replication friendly' end as cMessage

also this is a script I use to run the procs to drop and add the server...

Use Master

IF (select SERVERPROPERTY('ServerName')) <> (SELECT @.@.Servername )

begin

DECLARE @.SQL VARCHAR(256), @.oldsvrname varchar(128), @.newsvrname varchar(128)

select @.oldsvrname = cast(@.@.servername as varchar(128)), @.newsvrname = cast(SERVERPROPERTY('ServerName') as varchar(128))

set @.SQL = 'Sp_DropServer @.server = ''' + @.oldsvrname + ''', @.droplogins =''droplogins'''

exec( @.SQL)

SET @.SQL = 'Sp_Addserver @.server =''' + @.newsvrname + ''', @.local= ''LOCAL'' , @.duplicate_ok = ''duplicate_OK'' '

exec(@.SQL )

end

** must restart services at this point.

Thank you,

Pauly C

|||Maybe if you would run the agent with a higher OutputVerboseLevel, perhaps it may have given you clues.|||Actually I did that but it gave the same error message.