After upgrading our Dataminer lab System from 10.4.2 to 10.4.10, the upgrade went without any errors, however, when we log into cube there are no automation or correlation scripts present anymore. Looking at the C:\SkylineDataminer\scripts folder we can see the scripts are present on the hard drive just not present in the Cube display. Wehn trying to create a new script (to see if we could) we get an error "This name already exists".
This happens from both the Server Cube client and remote client.
The automation log has errors as follows:
2024/10/24 11:46:32.383|SLAutomation.exe 10.4.2435.84|24092|15744|CRequest::AddLocalInfo|DBG|-1|-- Added local SLNetCom info: VT_BSTR : 10.254.40.23
2024/10/24 11:46:32.386|SLAutomation.exe 10.4.2435.84|24092|15744|CAutomationBase::GetCookie|ERR|-1|Getting the cookie for 'SCRIPT:SRM_ForceStateTransition' failed: The client is unknown. 0x8004028ah.
2024/10/24 11:46:32.386|SLAutomation.exe 10.4.2435.84|24092|15744|CFolderInfo::LoadScriptInfo|DBG|-1|Failed to load info for script 'SRM_ForceStateTransition' (No XML cookie found)
2024/10/24 11:46:32.386|SLAutomation.exe 10.4.2435.84|24092|15744|CAutomationBase::GetCookie|ERR|-1|Getting the cookie for 'SCRIPT:SRM_QuarantineInformation' failed: The client is unknown. 0x8004028ah.
2024/10/24 11:46:32.386|SLAutomation.exe 10.4.2435.84|24092|15744|CFolderInfo::LoadScriptInfo|DBG|-1|Failed to load info for script 'SRM_QuarantineInformation' (No XML cookie found)
2024/10/24 11:46:32.387|SLAutomation.exe 10.4.2435.84|24092|15744|CAutomationBase::GetCookie|ERR|-1|Getting the cookie for 'SCRIPT:SRM_MigrateSrmServiceInfo' failed: The client is unknown. 0x8004028ah.
2024/10/24 11:46:32.387|SLAutomation.exe 10.4.2435.84|24092|15744|CFolderInfo::LoadScriptInfo|DBG|-1|Failed to load info for script 'SRM_MigrateSrmServiceInfo' (No XML cookie found)
Thanks for your assistance..
Steve
This happens on both DMA server Cube and remote client Cube. We also uninstalled and reinstalled cube to be sure the version matched with no difference. Also, we upgraded a second server with no problems. So, issue at this point, seems localized to this DMA server.
Hi Steve,
The Client is unknown here refers to the internal SLAutomation user, not the user you are logged in with. The error indicates that this user is not registered in the SLDataMiner process (which should happen at startup). So it is indeed purely within the DataMiner server.
One thing to check for that particular version, is if the domain name of the Agent is “DATAMINER” (or any variant in casing). This can lead to issues with the security and inter-process communication and should be fixed in the upcoming 10.4.12 (RN40743), Changing the domain name would be the workaround in this case followed by a dataminer restart.
If this is not the case a logCollector with a dump of SLDataMiner/SLAutomation would be helpful for further investigation.
Hi Steve,
The error you posted and the versions seems to point to the problem described in
Problem when DMA server is named DATAMINER | DataMiner Docs
In a nutshell, if the name of the server where the agent is running is called DATAMINER (case insensitive) we run into some issues with the security on inter-process communication leading to all kind of issues like the one you see.
This issue will be fixed in the upcoming 10.4.12/10.4CU9. Alternatively changing the name of the server will resolve the issue as well (keep in mind that this may need a new license).
Hope this helps.
Just a first quick thought, your client was updated? Do you get the same if you RDP the DMA and open Cube on the desktop of the DMA?