none
HPC Server Diagnostics fail due to missing access for 'NT AUTHORITY\ANONYMOUS LOGON' RRS feed

  • Question

  • Hi,

    I have a small HPC Server 2008 cluster (8 nodes) completely new installed. The installation worked like charm, but now I cannot run the diagnostics. I get the following error for all the nodes:

    ---------------------------
    HPC Cluster Manager
    ---------------------------
    [Error] The Management service encountered an error while performing a change on this node. Access is denied to user 'NT AUTHORITY\ANONYMOUS LOGON'. Check the operation log in the Administration Console for more information. 
    [Warning] The compute node failed to execute the operation.
    
    ---------------------------
    OK   
    ---------------------------
    I am logged on as the cluster user (specified in the configuration tab), which is also member of the "Domain Admins" group. The network topology is no. 1, i. e. the head nodes is the gateway to the enterprise network and all compute nodes are in a private network.

    As the nodes could be installed fully automatically, I assume that the cluster has access to the PDC, which is a separate Win2k8 server (std. ed.).

    Additionally, I can tell you that it is also not possible to run any remote command (as the cluster admin) from the server console on any remote node. I therefore assume, that the scheduler cannot log on to the compute node. A web search revealed only one significant hit, indicating that there might be a problem with the group policy of the domain. However, I do not know what to change. All servers (PDC, HPC master and compute nodes) are just out-of-the-box installations of Win2k8 without any special permissions set by me.

    I would be happy about any suggestions how to fix that.

    Thanks in advance,
    Christoph
    Monday, August 3, 2009 6:27 PM

Answers

  • Hello Christoph,

    It would be tough to figure out what went wrong without gather some more data, but since this is a new cluster you can export all your nodes to a node.xml. Then remove them from the cluster and re-add back in using the node.xml. Hopefully this should get back up and running.

    Thanks,
    Ben
    Thursday, August 6, 2009 5:12 PM
  • Hi Ben,

    thanks for the answer. I already did this, but it did not help, presumably because I corrupted the SDM data base somehow - don't ask me, how.

    As the cluster was newly installed, indeed, I had no log or performance data to lose and decided to drop the data base on the head node and also to re-install the HPC pack on the head node. Exporting the nodes to XML is of course a good idea, but I was really delighted that the newly installed head node automatically recognised the nodes that were OK and offered them for adding. The other ones could be easily installed from the XML backup without any big effort. It was also helpful that the head node remembered the network configuration from the registry somehow - it took me less than an hour for the whole process.

    Again, thanks for your response,
    Christoph
    Thursday, August 6, 2009 7:32 PM

All replies

  • In the meantime, I found out that - except for one node - I forgot to re-add the nodes after renaming some of them. However, re-adding did not work in any case, several nodes fail. The log output is

       at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
       at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
       at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
       at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
       at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)
       at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)
       at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe)
       at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
       at Microsoft.SystemDefinitionModel.Store.StoreWriter.SaveDataWithTransaction(SqlConnection connection, SqlTransaction transaction)
       at Microsoft.SystemDefinitionModel.Store.StoreWriter.SaveData(SqlConnection connection)
       at Microsoft.SystemDefinitionModel.Store.SdmSqlStore.UpdateChange(ChangeWriter change)
       --- End of inner exception stack trace ---
       at Microsoft.SystemDefinitionModel.Store.SdmSqlStore.ThrowStoreException(Exception e)
       at Microsoft.SystemDefinitionModel.Store.SdmSqlStore.UpdateChange(ChangeWriter change)
       at Microsoft.SystemDefinitionModel.Service.SdmStore.UpdateChange(ChangeData change)
    
    Inner exception:
    System.Data.SqlClient.SqlException: Only an administrator or the owner can change the owner the instance 266ED240-1917-4F4A-8512-B518092D4691.
    You do not have permission to update reference members on an instance 266ED240-1917-4F4A-8512-B518092D4691 in the change.
    Only an administrator or the owner can change the owner the instance 266ED240-1917-4F4A-8512-B518092D4691.
    You do not have permission to update reference members on an instance 266ED240-1917-4F4A-8512-B518092D4691 in the change.
    Only an administrator or the owner can change the owner the instance 266ED240-1917-4F4A-8512-B518092D4691.
    You do not have permission to update reference members on an instance 266ED240-1917-4F4A-8512-B518092D4691 in the change.
    Only an administrator or the owner can change the owner the instance 266ED240-1917-4F4A-8512-B518092D4691.
    You do not have permission to update reference members on an instance 266ED240-1917-4F4A-8512-B518092D4691 in the change.
    Only an administrator or the owner can change the owner the instance 266ED240-1917-4F4A-8512-B518092D4691.
    You do not have permission to update reference members on an instance 266ED240-1917-4F4A-8512-B518092D4691 in the change.
    Only an administrator or the owner can change the owner the instance 266ED240-1917-4F4A-8512-B518092D4691.
    You do not have permission to update reference members on an instance 266ED240-1917-4F4A-8512-B518092D4691 in the change.
    Only an administrator or the owner can change the owner the instance 266ED240-1917-4F4A-8512-B518092D4691.
    You do not have permission to update reference members on an instance 266ED240-1917-4F4A-8512-B518092D4691 in the change.
    Only an administrator or the owner can change the owner the instance 266ED240-1917-4F4A-8512-B518092D4691.
    You do not have permission to update reference members on an instance 266ED240-1917-4F4A-8512-B518092D4691 in the change.
    Only an administrator or the owner can change the owner the instance 266ED240-1917-4F4A-8512-B518092D4691.
    You do not have permission to update reference members on an instance 266ED240-1917-4F4A-8512-B518092D4691 in the change.
    Only an administrator or the owner can change the owner the instance 7C08C0CE-1371-4928-820F-C579D2E98AFB.
    You do not have permission to update setting values for the instance 7C08C0CE-1371-4928-820F-C579D2E98AFB in the change.
    You do not have permission to update reference members on an instance 7C08C0CE-1371-4928-820F-C579D2E98AFB in the change.
    Only an administrator or the owner can change the owner the instance 7C08C0CE-1371-4928-820F-C579D2E98AFB.
    You do not have permission to update setting values for the instance 7C08C0CE-1371-4928-820F-C579D2E98AFB in the change.
    You do not have permission to update reference members on an instance 7C08C0CE-1371-4928-820F-C579D2E98AFB in the change.
    Only an administrator or the owner can change the owner the instance 7C08C0CE-1371-4928-820F-C579D2E98AFB.
    You do not have permission to update setting values for the instance 7C08C0CE-1371-4928-820F-C579D2E98AFB in the change.
    You do not have permission to update reference members on an instance 7C08C0CE-1371-4928-820F-C579D2E98AFB in the change.
    Only an administrator or the owner can change the owner the instance 7C08C0CE-1371-4928-820F-C579D2E98AFB.
    You do not have permission to update setting values for the instance 7C08C0CE-1371-4928-820F-C579D2E98AFB in the change.
    You do not have permission to update reference members on an instance 7C08C0CE-1371-4928-820F-C579D2E98AFB in the change.
    Only an administrator or the owner can change the owner the instance 7C08C0CE-1371-4928-820F-C579D2E98AFB.
    You do not have permission to update setting values for the instance 7C08C0CE-1371-4928-820F-C579D2E98AFB in the change.
    You do not have permission to update reference members on an instance 7C08C0CE-1371-4928-820F-C579D2E98AFB in the change.
    Only an administrator or the owner can change the owner the instance 7C08C0CE-1371-4928-820F-C579D2E98AFB.
    You do not have permission to update setting values for the instance 7C08C0CE-1371-4928-820F-C579D2E98AFB in the change.
    You do not have permission to update reference members on an instance 7C08C0CE-1371-4928-820F-C579D2E98AFB in the change.
    Only an administrator or the owner can change the owner the instance 7C08C0CE-1371-4928-820F-C579D2E98AFB.
    You do not have permission to update setting values for the instance 7C08C0CE-1371-4928-820F-C579D2E98AFB in the change.
    You do not have permission to update reference members on an instance 7C08C0CE-1371-4928-820F-C579D2E98AFB in the change.
    Only an administrator or the owner can change the owner the instance 7C08C0CE-1371-4928-820F-C579D2E98AFB.
    You do not have permission to update setting values for the instance 7C08C0CE-1371-4928-820F-C579D2E98AFB in the change.
    You do not have permission to update reference members on an instance 7C08C0CE-1371-4928-820F-C579D2E98AFB in the change.
    Only an administrator or the owner can change the owner the instance 7C08C0CE-1371-4928-820F-C579D2E98AFB.
    You do not have permission to update setting values for the instance 7C08C0CE-1371-4928-820F-C579D2E98AFB in the change.
    You do not have permission to update reference members on an instance 7C08C0CE-1371-4928-820F-C579D2E98AFB in the change.
    Only an administrator or the owner can change the owner the instance 3D24DCEF-5CCA-4C57-B37B-E8C9A93D37A9.
    You do not have permission to update setting values for the instance 3D24DCEF-5CCA-4C57-B37B-E8C9A93D37A9 in the change.
    Only an administrator or the owner can change the owner the instance 3D24DCEF-5CCA-4C57-B37B-E8C9A93D37A9.
    You do not have permission to update setting values for the instance 3D24DCEF-5CCA-4C57-B37B-E8C9A93D37A9 in the change.
    Only an administrator or the owner can change the owner the instance 3D24DCEF-5CCA-4C57-B37B-E8C9A93D37A9.
    You do not have permission to update setting values for the instance 3D24DCEF-5CCA-4C57-B37B-E8C9A93D37A9 in the change.
    Only an administrator or the owner can change the owner the instance 3D24DCEF-5CCA-4C57-B37B-E8C9A93D37A9.
    You do not have permission to update setting values for the instance 3D24DCEF-5CCA-4C57-B37B-E8C9A93D37A9 in the change.
    Only an administrator or the owner can change the owner the instance 3D24DCEF-5CCA-4C57-B37B-E8C9A93D37A9.
    You do not have permission to update setting values for the instance 3D24DCEF-5CCA-4C57-B37B-E8C9A93D37A9 in the change.
    Only an administrator or the owner can change the owner the instance 3D24DCEF-5CCA-4C57-B37B-E8C9A93D37A9.
    You do not have permission to update setting values for the instance 3D24DCEF-5CCA-4C57-B37B-E8C9A93D37A9 in the change.
    Only an administrator or the owner can change the owner the instance 3D24DCEF-5CCA-4C57-B37B-E8C9A93D37A9.
    You do not have permission to update setting values for the instance 3D24DCEF-5CCA-4C57-B37B-E8C9A93D37A9 in the change.
    Only an administrator or the owner can change the owner the instance 3D24DCEF-5CCA-4C57-B37B-E8C9A93D37A9.
    You do not have permission to update setting values for the instance 3D24DCEF-5CCA-4C57-B37B-E8C9A93D37A9 in the change.
    Only an administrator or the owner can change the owner the instance 3D24DCEF-5CCA-4C57-B37B-E8C9A93D37A9.
    You do not have permission to update setting values for the instance 3D24DCEF-5CCA-4C57-B37B-E8C9A93D37A9 in the change.
    It seems some kind of permission problem in the SQL database of the head node. Any ideas about that?
    Wednesday, August 5, 2009 7:35 AM
  • Hello Christoph,

    It would be tough to figure out what went wrong without gather some more data, but since this is a new cluster you can export all your nodes to a node.xml. Then remove them from the cluster and re-add back in using the node.xml. Hopefully this should get back up and running.

    Thanks,
    Ben
    Thursday, August 6, 2009 5:12 PM
  • Hi Ben,

    thanks for the answer. I already did this, but it did not help, presumably because I corrupted the SDM data base somehow - don't ask me, how.

    As the cluster was newly installed, indeed, I had no log or performance data to lose and decided to drop the data base on the head node and also to re-install the HPC pack on the head node. Exporting the nodes to XML is of course a good idea, but I was really delighted that the newly installed head node automatically recognised the nodes that were OK and offered them for adding. The other ones could be easily installed from the XML backup without any big effort. It was also helpful that the head node remembered the network configuration from the registry somehow - it took me less than an hour for the whole process.

    Again, thanks for your response,
    Christoph
    Thursday, August 6, 2009 7:32 PM