locked
Error en SQL RRS feed

  • Question

  • Buenas gente,

     

    Te copio un error que estoy teniendo en una base del sql que me arroja este siguiente error:

    Alguien me puede ayudar ??

     

     

    Error de biblioteca SQL: error de OLEDB encontrado al llamar a IDBInitialize::Initialize. HR = 0x80004005. SQLSTATE: 42000, Native Error: 18461
    Error state: 1, Severity: 14
    Source: Microsoft SQL Native Client
    Error message: Error de inicio de sesión del usuario 'NT AUTHORITY\SYSTEM'. Motivo: el servidor está en modo de usuario único. En este momento sólo puede conectarse un administrador.
    DBPROP_INIT_DATASOURCE: NEARBA-S1003\SQLEXPRESS_AXOFT
    DBPROP_INIT_CATALOG: master
    DBPROP_AUTH_INTEGRATED: SSPI


    For more information, see Help and Support Center at

     

    Saludos.


    Gaston Dominguez
    Tuesday, February 15, 2011 11:38 PM

Answers

  • Hi Jonathan & akoes,

    In my case and following the jonathan's advices i find the C:\WINDOWS\SoftwareDistribution\Download and erase all download on the server.

    This action resolved my problem and then i saw that i have onather installation frist.

    I had installed Microsoft SQL Server 2005 Service Pack 4 before.

    regards


    Gaston Dominguez
    • Proposed as answer by Naomi N Tuesday, February 22, 2011 10:21 PM
    • Marked as answer by WeiLin Qiao Friday, February 25, 2011 4:56 AM
    Tuesday, February 22, 2011 6:50 PM

All replies

  • Perdona mi mal español, Inglés es mi langugage primaria, pero voy a tratar de ayudarle en español con su problema.

    Este
    error te está diciendo que el servidor SQL Server está en modo de usuario único, que sólo permite una conexión. En este caso de que algo más ha conectado con el servidor SQL Server. ¿Qué estás tratando de hacer, o sabes por qué SQL Server está en modo de usuario único?

    Jonathan Kehayias | Senior Database Administrator and Consultant
    Feel free to contact me through My Blog or Twitter
    Please click the Mark as Answer button if a post solves your problem!
    Wednesday, February 16, 2011 2:16 AM
  • Hi jonathan lets talk with your primary language no problema.

    Well i don't have much expirence with sql server and i don't why happen this ??

     

    How i can solved ?? Do you know ??

     

    Regards.


    Gaston Dominguez
    Wednesday, February 16, 2011 2:35 AM
  • How was SQL Server started and what is connecting to it that is getting this error?  The first thing to attempt would be to stop the SQL Server (SQLEXPRESS_AXOFT) service using either the SQL Server Configuration Manager (Start-> Programs -> Microsoft SQL Server XXXX-> Configuration Tools) or the Services Snapin (services.msc) and then restart it.  If that does not resolve the issue, right click on the SQL Server (SQLEXPRESS_AXOFT) service in the SQL Server Configuration Manager, click on the Advanced Tab at the top and look at the Startup Parameters option.  Make sure that there is not a -m -c -f or -T3608 parameter in the list.  If there is remove it and try to restart the service again.  While you are in there, look at the -e parameter and it will tell you the path and filename to the SQL Server ErrorLog.  Open that file, and copy/paste its contents back into this thread.


    Jonathan Kehayias | Senior Database Administrator and Consultant
    Feel free to contact me through My Blog or Twitter
    Please click the Mark as Answer button if a post solves your problem!
    Wednesday, February 16, 2011 2:45 AM
  • Thanks Jonathan I restarted the services and it's working again.

    regards.


    Gaston Dominguez
    Wednesday, February 16, 2011 11:47 AM
  • Well i am back because i see the event again.

    this is the parameters on SQL Server Configuration Manager:

    -dC:\Program Files\Microsoft SQL Server\MSSQL.4\MSSQL\DATA\master.mdf;-eC:\Program Files\Microsoft SQL Server\MSSQL.4\MSSQL\LOG\ERRORLOG;-lC:\Program Files\Microsoft SQL Server\MSSQL.4\MSSQL\DATA\mastlog.ldf

    Content Error Log:

    2011-02-16 08:56:06.42 Server      Microsoft SQL Server 2005 - 9.00.4035.00 (Intel X86)
     Nov 24 2008 13:01:59
     Copyright (c) 1988-2005 Microsoft Corporation
     Express Edition on Windows NT 5.2 (Build 3790: Service Pack 2)

    2011-02-16 08:56:06.42 Server      (c) 2005 Microsoft Corporation.
    2011-02-16 08:56:06.42 Server      All rights reserved.
    2011-02-16 08:56:06.42 Server      Server process ID is 1560.
    2011-02-16 08:56:06.42 Server      Authentication mode is MIXED.
    2011-02-16 08:56:06.42 Server      Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL.4\MSSQL\LOG\ERRORLOG'.
    2011-02-16 08:56:06.42 Server      This instance of SQL Server last reported using a process ID of 592 at 16/02/2011 08:54:16 a.m. (local) 16/02/2011 11:54:16 a.m. (UTC). This is an informational message only; no user action is required.
    2011-02-16 08:56:06.42 Server      Registry startup parameters:
    2011-02-16 08:56:06.43 Server        -d C:\Program Files\Microsoft SQL Server\MSSQL.4\MSSQL\DATA\master.mdf
    2011-02-16 08:56:06.43 Server        -e C:\Program Files\Microsoft SQL Server\MSSQL.4\MSSQL\LOG\ERRORLOG
    2011-02-16 08:56:06.43 Server        -l C:\Program Files\Microsoft SQL Server\MSSQL.4\MSSQL\DATA\mastlog.ldf
    2011-02-16 08:56:06.43 Server      Command Line Startup Parameters:
    2011-02-16 08:56:06.43 Server        -m SqlSetup
    2011-02-16 08:56:06.43 Server        SqlSetup
    2011-02-16 08:56:06.44 Servidor    SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
    2011-02-16 08:56:06.45 Servidor    Detected 8 CPUs. This is an informational message; no user action is required.
    2011-02-16 08:56:06.70 Servidor    Using dynamic lock allocation.  Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node.  This is an informational message only.  No user action is required.
    2011-02-16 08:56:07.02 Servidor    Database Mirroring Transport is disabled in the endpoint configuration.
    2011-02-16 08:56:07.04 spid5s      Warning ******************
    2011-02-16 08:56:07.04 spid5s      SQL Server started in single-user mode. This an informational message only. No user action is required.
    2011-02-16 08:56:07.09 spid5s      Starting up database 'master'.
    2011-02-16 08:56:07.39 spid5s      Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
    2011-02-16 08:56:07.53 spid5s      SQL Trace ID 1 was started by login "sa".
    2011-02-16 08:56:07.56 spid5s      Starting up database 'mssqlsystemresource'.
    2011-02-16 08:56:07.60 spid5s      The resource database build version is 9.00.4035. This is an informational message only. No user action is required.
    2011-02-16 08:56:07.79 spid7s      Starting up database 'model'.
    2011-02-16 08:56:07.79 spid5s      Server name is 'NEARBA-S1003\SQLEXPRESS_AXOFT'. This is an informational message only. No user action is required.
    2011-02-16 08:56:07.79 spid5s      Starting up database 'msdb'.
    2011-02-16 08:56:07.87 Servidor    The certificate was successfully loaded for encryption.
    2011-02-16 08:56:07.89 Servidor    Server is listening on [ 'any' <ipv4> 1434].
    2011-02-16 08:56:07.89 Servidor    Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\SQLEXPRESS_AXOFT ].
    2011-02-16 08:56:07.89 Servidor    Server local connection provider is ready to accept connection on [ \\.\pipe\MSSQL$SQLEXPRESS_AXOFT\sql\query ].
    2011-02-16 08:56:07.89 Servidor    Dedicated administrator connection support was not started because it is not available on this edition of SQL Server. This is an informational message only. No user action is required.
    2011-02-16 08:56:07.98 Servidor    SQL Server is now ready for client connections. This is an informational message; no user action is required.
    2011-02-16 08:56:08.04 spid7s      Clearing tempdb database.
    2011-02-16 08:56:08.61 spid7s      Starting up database 'tempdb'.
    2011-02-16 08:56:08.67 spid5s      Recovery is complete. This is an informational message only. No user action is required.
    2011-02-16 11:00:07.56             Error: 18461, gravedad: 14, estado: 1.
    2011-02-16 11:00:07.56             Login failed for user 'NT AUTHORITY\SYSTEM'. Reason: Server is in single user mode. Only one administrator can connect at this time. [CLIENTE: <local machine>]
    2011-02-16 11:00:07.57             Error: 18461, gravedad: 14, estado: 1.
    2011-02-16 11:00:07.57             Login failed for user 'NT AUTHORITY\SYSTEM'. Reason: Server is in single user mode. Only one administrator can connect at this time. [CLIENTE: <local machine>]
    2011-02-16 11:00:07.57             Error: 18461, gravedad: 14, estado: 1.
    2011-02-16 11:00:07.57             Login failed for user 'NT AUTHORITY\SYSTEM'. Reason: Server is in single user mode. Only one administrator can connect at this time. [CLIENTE: <local machine>]
    2011-02-16 11:00:07.58             Error: 18461, gravedad: 14, estado: 1.
    2011-02-16 11:00:07.58             Login failed for user 'NT AUTHORITY\SYSTEM'. Reason: Server is in single user mode. Only one administrator can connect at this time. [CLIENTE: <local machine>]

     


    Gaston Dominguez
    Wednesday, February 16, 2011 5:44 PM
  • Gaston,

    Looking at the ErrorLog entries the following stands out:

    2011-02-16 08:56:06.43 Server      Command Line Startup Parameters:
    2011-02-16 08:56:06.43 Server        -m SqlSetup
    2011-02-16 08:56:06.43 Server        SqlSetup

    This shows that SqlSetup started SQL in single user mode which generally means that a service pack or patch is attempting to install.  Check and see if you have Windows Update turned on to automatically apply hot fixes on the machine.  Also look at the %ProgramFiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files folder to see if you have logs of a setup attempt with today/yesterdays datetime stamp on it.


    Jonathan Kehayias | Senior Database Administrator and Consultant
    Feel free to contact me through My Blog or Twitter
    Please click the Mark as Answer button if a post solves your problem!
    Wednesday, February 16, 2011 7:10 PM
  • Well, yes i have this update to install Microsoft SQL Server 2005 Express Edition Service Pack 4 .

    But by other side, I'm seeing that i have installed Microsoft SQL Server 2005 Service Pack 4.

    what i can do with it ??

    regards.


    Gaston Dominguez
    Wednesday, February 16, 2011 8:33 PM
  • Hi Gaston and Jonathan!

    Good to see we are not alone - a customer of ours is having similar trouble while running the following update

    Microsoft SQL Server 2005 Express Edition Service Pack 4 (KB2463332 )

    on his Windows 2008 Standard Server (32bit) running as member server. This server is also serving WSUS and a centralised management-console of his antivirus-solution - both relying on SQL Express / Windows internal database.

    The setup rolled out with WSUS was unsusccessfull. Manual installation revealed several troubles - leaving the system unusable after the failed update (no matter if done by WSUS or manual).

    LinkID    20476
    Produktename    Microsoft SQL Server
    Produktversion 9.00.5000.00
    Meldungsquelle    setup.rll
    Meldungs-ID    2259
    EvtType    darlib}\viewinstaller.cpp@ValidateUp

    Details

    ID: 2259                                             
    Source: setup.rll 

    This error mentioned not being able to update tables.

    Further errors had no source:

    Details
    ID: 17656                                             
    Quelle: 

    Details
    ID: 17148                                             
    Quelle:

    Details
    ID: 18461                                             
    Quelle:

    Our customer had to go back by disaster-recovery (snapshot) - to service WSUS and antivirus-solutions.

    @Jonathan: Any comments on the failed SP4 Update are welcome.

    Tuesday, February 22, 2011 11:07 AM
  • akoes,

    Can you go into the Setup Bootstrap folder and post the contents of the summary.txt file for the SP4 failed install attempt?  I've asked a friend on the Microsoft PSS team if he knows of any issues, but the contents of the setup logs are going to have the failures he will need to look for any related cases in their support systems.


    Jonathan Kehayias | Senior Database Administrator and Consultant
    Feel free to contact me through My Blog or Twitter
    Please click the Mark as Answer button if a post solves your problem!
    Tuesday, February 22, 2011 1:07 PM
  • The 2259 error is most likely popping up from a previous failed upgrade/setup attempt against the SQL Express Instance.  See the comments on the following connect Feedback item:

    http://connect.microsoft.com/SQLServer/feedback/details/296206/sql-server-express-advance-setup-error-code-2259-datebase-table-s-update-failed#details

    You can validate this is the case by looking at the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.X\Setup\Resume key in the registry where is the Instance Number to SQL Express as listed in the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\Instance Names\SQL key.  If Resume = 1 that is the failed update sign and you should follow the work around in the Connect feedback of repairing the instance and then reapply SP4.  If that all fails, you can attempt to manually change this key to 0 and then rerun SP4, but that is at your own risk and could force you to have to uninstall the SQL Express Instance and reinstall it using the SP4 installer from scratch after rebooting the machine.


    Jonathan Kehayias | Senior Database Administrator and Consultant
    Feel free to contact me through My Blog or Twitter
    Please click the Mark as Answer button if a post solves your problem!
    Tuesday, February 22, 2011 5:51 PM
  • Hi Jonathan & akoes,

    In my case and following the jonathan's advices i find the C:\WINDOWS\SoftwareDistribution\Download and erase all download on the server.

    This action resolved my problem and then i saw that i have onather installation frist.

    I had installed Microsoft SQL Server 2005 Service Pack 4 before.

    regards


    Gaston Dominguez
    • Proposed as answer by Naomi N Tuesday, February 22, 2011 10:21 PM
    • Marked as answer by WeiLin Qiao Friday, February 25, 2011 4:56 AM
    Tuesday, February 22, 2011 6:50 PM