- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-22-2014 01:46 PM
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
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-22-2014 11:18 PM
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-22-2014 11:18 PM
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-22-2014 11:38 PM
Make sure the SNC user whom you are using for the basic authentication has the soap_admin role.
Thanks & Regards,
Hari
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-22-2024 03:57 AM
Sorry, @harikrish_v I couldn't find any role named soap_admin, I gave soap_create and all the other remaining roles related to soap but still am getting
Please share further insights onto this
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-14-2024 02:03 AM
Hi Aniket,
Did u find any fix for this issue? we are facing similar issue.
Thanks,
