Error: 'Unable to checkout' when trying to check out a GPO in the Repository. (NETIQKB33999)

  • 7733999
  • 02-Feb-2007
  • 07-Apr-2009

Environment

fact
NetIQ Group Policy Administrator 3.0

fact
NetIQ Group Policy Administrator 4.x

fact
NetIQ Group Policy Administrator 5.0

fact
NetIQ Group Policy Administrator 6.0

symptom
Error: 'Unable to checkout' when trying to check out a GPO in the Repository.

symptom
Unable to check out a GPO in the repository.

symptom

Error message: "Server name cannot be empty"

Resolution

To resolve this error:

    1. Start the SQL Query Analyzer or the SQL Server Management Studio

    2. Run this query on the Repository Server:

        Select @@SERVERNAME servername

        (Please use this query exactly as shown without substituting your real server name.)

        It should return a result of the actual server name, or it may return a result of NULL.

        (If it returns the actual server name, this is not the cause of the issue.)

        If this test produces a NULL result, please follow these steps: 

    3. Execute the following queries:

         a)  sp_dropserver 'servername', droplogins
              (replace 'servername' with the name of the SQL server)

              Note:  You must drop any remote logins and external logins before you can drop the server.  The above command will do this.

         b)  sp_addserver 'servername', local
              (replace 'servername' with the name of the SQL server)

    4. NOTE: You now need to restart the SQL service. 

        After restarting SQL, you can execute the following query to verify the server name:

    5. Select @@SERVERNAME servername
         (Please use this query exactly as shown without substituting your real server name.)

         This should return the actual server name as a result. 

    6.  Re-open the NetIQ GPA GUI and attempt a Checkout operation.

Cause

cause
The cause of this issue maybe due to the Repository not capturing the name of the server.  This can typically happen if you have multiple instances of SQL running and the database holds the value of the server as NULL.  This can also happen if another database, that is installed on the Repository server, sets the SERVER value to <Null>

Additional Information

Formerly known as NETIQKB33999