Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

service desk sp2: An error occured. please try your request later

Created: 28 Jun 2012 • Updated: 29 Jun 2012 | 8 comments

Hi,

Error in Service Desk Sp2, upon creating ticket, an error prompted:

An error occured, please try your request later or contact at....

Any known issue?

Thanks

Comments 8 CommentsJump to latest comment

reecardo's picture

Is there anything being reported in the incident management logs? They're located at <install>/Logs.

gBBB's picture

As reecardo mentioned, there will be more information in the logs. You can use the log viewer to see all entries for all processes (located in Start Menu at Symantec\Workflow Designer\Tools). Or you can go straight to log files.

MGerio's picture

Please see attached logs from our 2nd testing machine, same problem is encountered

Thanks

AttachmentSize
LogViewer Data2.xlsx 9.99 KB
reecardo's picture

I am seeing a couple things... the first is a 404 error when trying to contact the SMP during some component runs. I'd verify your SMP credentails added during install are correct in Workflow Explorer. If they are, I'd verify that Administrator SDK is installed on the SMP (required for report component runs)

I'm also seeing "Invalid session ID". Unsure if this is related, but we have some fixed to "empty session ID" checked into the SP2 rollup available.

gBBB's picture

I agree with reecardo - check your SMP credentials in Workflow Credentials Manager (a different tab in Workflow Explorer - the same UI for the Log Viewer). Verify your address and credentials and use the Test function on your SMP credential entry.

However, i don't believe this is what is causing your submission failure. I noticed the "Verify Session ID failed" error for the SD.Feeder.GeneralIncidentSubmitForm process. How have you configured your Process Manager authentication on this server, and which user account are you using to try to submit your incident? This error can be caused by manually modifying the Admin account, among other causes.

The log you posted from your first server showed a variety of errors, but none specifically from Incident Submission. It may be helpful to clear the log, perform your test, and then capture the log immediately afterward.