Error while using Remote Connection

First question, what version are you using?

V7.0.1

As the error contains SSPI, this has something to do with your authentication between the client and the server where the job service is running on for the remote connection.

A Google search using the error message provides several reasons for that to happen. From wrongly configures service principal names (SPNs) over changed service accounts for the SQL Server to bad Windows 10 updates.

I suggest you check some of the given solutions that seem to fit in your case.

You can of course contact support to help you out.

Thanks for Your response ! I have gone through some of the solutions provided in google .. But I am not getting where exactly is SPN configured ?
Can you please suggest on that .

It is not the SPN from the job service it doesn't have one.

For starters, what type of connector are you trying to use remote connection for? Is your job service running with a service account configured? Are you client and your server in the same domain? etc.

These are all questions support can walk you through but they make troubleshooting here in the community hard to do.

UPADATE:

We were under the impression that the 'Remote Connect Plugin' was working fine after its recent installation. But, when we checked the job service logs today, we found that there is an issue with starting the 'Remote Connect Plugin'. The error shown in the logs is as follows:

<x><e>2017-08-23 11:51:46 +02:00 - Exception occurred in Job Service (thread: <Unknown>):

[821049] Error starting One Identity Manager Service.

[821061] Error starting plugin 'Remote Connect Plugin'.

[System.ServiceModel.CommunicationObjectFaultedException] The communication object, System.ServiceModel.ServiceHost, cannot be used for communication because it is in the Faulted state.<x>

<d> at VI.JobService.JobService._StartJobService()

---- Start of Inner Exception ----

at VI.JobService.JobService._StartJobService()

at VI.Projector.JobService.Plugins.RemoteConnectService.RemoteConnectPlugin.Start()

at System.ServiceModel.ServiceHostBase.System.IDisposable.Dispose()

at System.ServiceModel.Channels.CommunicationObject.Close(TimeSpan timeout)<x>

Also, as a aresult, the job queue became extremeley slow.



May be the above error has a relation with the remote connection issue we've been facing?

Same questions as before:

• Is your job service running with a service account configured?
• Are your client and your server in the same domain?

And one additional question:

• Did you configure an AD group that defines which users are allowed to use the remote connection plugin in Job Service Configurator?
  

• Yes Markus, the job service runs with a service account configured.

• The client and the server are also on the same domain.

• Yes, we did configure the Remote Connect Plugin with ADGroup Authentication, and provided the SID of the ADGroup, the members of which are allowed to use  Remote connection.

Also, the error - 'Error starting plugin Remote Connect Plugin' gets generated in the logs when the job services are restarted.

Thank you!

Your error maybe as simple is some other process is listening on the Remote Connection Plugin port of 2880. I would do a netstat to see if it's open. If it's in used, then I would change it to something else.

Hi,

i did a netstat-an on the cmd of the jobserver, and I couldn't find port 2880 listed anywhere. I think it means port 2880 is not being used by any other process.

I also used the command 'telnet host 2880' on the cmd, which gave a message 'Could not open connection to the host, on port 2880, connection failed'. I assume it means no process is running on the port.

Thanks for your response!