Event ID 32073: An error was encountered when executing the stored procedure

twitterlinkedinmail

Environment:

Lync Server 2013 On-Premise

  • Front-End Pool
  • Edge Pool

Issue:

During a SQL hardening exercise to ensure that all local SQL Express servers were up to date and adhere to the corporate policies we encountered an error :

“An error was encountered when executing the stored procedure that logs errors to the back-end database.

Execution Result: 0, Native Error: 6005, Severity: 14, Line Number: 1, Sql State: 2, ODBC State: 42000, Error Text: [# [Microsoft]



SHUTDOWN is in progress. #].

Cause: Possible issues with back-end database. Resolution: Ensure the back-end is functioning correctly.”

eventid32073error

Resolution:

  1. Tried to connect using SQL Management Studio to the Front-end Server\RTCLocal to see if there was something wrong with the databases however we could not connect and received the following erroreventid32073sqlmgmterror
  2. Opened SQL Server Configuration Manager
    1. Expanded SQL Server Network Configuration
    2. Right Clicked -> Protocols for RTCLOCAL -> Selected Properties
    3. Under the Flags Tab, Hide Instance was set to Yeseventid32073issue
    4. Changed the option from Yes to Noeventid32073fix
    5. Clicked Apply.
  3. Restarted the SQL Express Service for RTCLOCAL
  4. Tried to connect using SQL Management Studio to the Front-end Server\RTCLocal and was now able to connect.eventid32073working
  5. Repeated the above steps for Front-end Server\LyncLocal
  6. The rebooted the server
  7. Once the services came back up the error messages had been resolved and we were able to perform all Lync Server 2013 functions.

As it turns out one of the hardening functions hides the SQL Express instance so that the services were unable to see or reach the SQL Express database instance, once we made the database instance available again the services were able to connect.

 

twitterlinkedinmail

3 comments on “Event ID 32073: An error was encountered when executing the stored procedure

  1. Why that hiding is in place, if it breaks the whole database? Didnt you just not follow further configuration required, if hiding is enabled?

    1. Hi there, hiding was set to No by default during the installation. The SQL DBA during a recent hardening exercise set it to Yes (hiding enabled), which is what we had found out broke the communication so we made it visible again and the services came up.

      1. Yes I understand. What I mean is, that if somebody is reading an SQL hardening guide, does that hardening guide say what are the consequences of hiding an instance, and how to workaround those consequences? There has to be a reason why this hiding exist, otherwise how can any other SQL connection work in your environment? I am really interested now, if that SQL hardening guide is coming directly from MSFT (is it publicly reachable), or some 3rd party/ private document?

Leave a Reply

Your email address will not be published. Required fields are marked *

*