Join the #BuildWithBuildAgent Challenge! Get recognized, earn exclusive swag, and inspire the ServiceNow Community with what you can build using Build Agent.  Join the Challenge.

Getting error "Insufficient rights for creating new records:"

allen_pitts
Giga Expert

Hello Support,

 

Our Production instance was cloned into the Testing
environment. Since then have been getting

Insufficient rights for creating new records: com.glide.processors.soap.SOAPProcessingException: Insufficient rights for creating new records: com.glide.processors.soap.command.Insert.process(Insert.java:42)

com.glide.processors.soap.SOAPProcessorThread.doCommand(SOAPProcessorThread.java:288)

com.glide.processors.soap.SOAPProcessorThread.doCommand(SOAPProcessorThread.java:277)

com.glide.processors.soap.SOAPProcessorThread.processStandardWebService(SOAPProcessorThread.java:212)

com.glide.processors.soap.SOAPProcessorThread.processBody(SOAPProcessorThread.java:192)ing

 

Believe has to do with Discovery MIDserver but not sure.
Tried deactivating the MIDServer schedule and rebuilding the
MIDserver user object. Still getting this message nine times
a second. Really filling up the system log.

 

How can I get this to stop?

 

Thanks.

 

Allen Pitts
LHP Hospital Group

1 ACCEPTED SOLUTION

Jamie_douglas
Giga Expert

Hi Allen.



In which environment are you getting these error messages?



TEST


If you are getting these errors in TEST, make sure you disable any outbound SOAP messages in TEST as you may be sending messages to an endpoint that is NOT expecting traffic from your TEST instance.



PROD


If you are getting these errors in PROD, also make sure that you disable the outbound messages in TEST - If the errors are production, what I am thinking may be happening is that some messages are being sent from TEST to an end point which is then replying to your PROD instance rather than responding back to TEST - this would be the case if the end point is hard coded to reply to your PROD.



Please let us know how you get on after disabling the soap integration's in TEST.


View solution in original post

5 REPLIES 5

No wasn't able to figure out any appropriate fix for the issue