This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Failure with Connect SMC APP to SMC Server

Hello Guys,

 

we have issues with the SMC App to connect to tthe Server.

 

In this Time we have SMC aaS, and would turn to SMC 6.1.4 local installed.

First i have Setup a new Server Win Server 2012 R2 with SMC 6.1.4, with the same Settings an Rules from our SMC aaS.

Now if i want to Register a new Mobile Device the App says Connection failed.

I have saved the log file.

 

Here the log:

2017/01/19 09:25:51:952 | Could not delete Sophos Container with AccessGroup 2H5GFH3774.com.sophos.container. OSStatus -25300
{
    agrp = "2H5GFH3774.com.sophos.container";
    class = genp;
}
E | 2017/01/19 09:25:51:956 | OSStatus: -25300
E | 2017/01/19 09:25:51:959 | OSStatus: -25300
E | 2017/01/19 09:26:01:628 | Could not delete Sophos Container with AccessGroup 2H5GFH3774.com.sophos.container. OSStatus -25300
{
    agrp = "2H5GFH3774.com.sophos.container";
    class = genp;
}
E | 2017/01/19 09:26:01:632 | OSStatus: -25300
E | 2017/01/19 09:26:01:637 | OSStatus: -25300
E | 2017/01/19 09:26:01:643 | OSStatus: -25300
E | 2017/01/19 09:26:03:846 | Couldn't remove last invalid cert hash
E | 2017/01/19 09:26:04:326 | error sending activation data, no response from server
E | 2017/01/19 09:26:04:328 | activationWizardViewControllerDidFinishWithError: {
    reason = ErrorUndefined;
    summary = ErrorCouldNotActivate;
}
E | 2017/01/19 09:26:04:329 | ActivationDidFinishWithError: {
    reason = ErrorUndefined;
    summary = ErrorCouldNotActivate;
}
E | 2017/01/19 09:26:48:333 | Could not delete Sophos Container with AccessGroup 2H5GFH3774.com.sophos.container. OSStatus -25300
{
    agrp = "2H5GFH3774.com.sophos.container";
    class = genp;
}
E | 2017/01/19 09:26:48:336 | OSStatus: -25300
E | 2017/01/19 09:26:48:339 | OSStatus: -25300
V | 2017/01/19 09:27:03:119 | Verbose now logged...
D | 2017/01/19 09:27:03:119 | Debug now logged...
I | 2017/01/19 09:27:03:119 | Info now logged...
W | 2017/01/19 09:27:03:119 | Warn now logged...
E | 2017/01/19 09:27:03:119 | Error now logged...

Did anyone have a Suggestion to fix it?

 

Thank you



This thread was automatically locked due to age.