Still having intermittent issues here. This is in a production environment. Our load is really quite light all things considered. It will work OK for days but then start erroring out with the 404 errors.
I had a real bad case of it last week and recreating the Orchestrator connector seemed to fix it for a while. From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Rob Plank Sent: Tuesday, August 20, 2013 12:41 PM To: servman@lists.myitforum.com; Anshuman Nangia Subject: [servman] RE: Service Manager and Orchestrator hiccups My issues actually have gotten worse, it is in my production environment, we currently don’t see any resource issues with the management server or the orchestrator server. The connector was working fine with the fixes I had put in place up until last week, when all of my runbooks stop executing. The runbook logs show this error : Runbook invocation failed because the Runbook contract has changed. See eventlog for additional information The connector view doesn’t update correctly shows that the connector has not run in weeks and the last run was successful. Upon investigating the logs it shows a 404 error looking for Query: http://<server>:81/orchestrator2012/orchestrator.svc/Folders(guid'667bd46d-bcdc-42c2-9509-0c34d0dbdba6')<http://%3cserver%3e:81/orchestrator2012/orchestrator.svc/Folders(guid'667bd46d-bcdc-42c2-9509-0c34d0dbdba6')> I have not finished testing everything I want to test but I do see that a few things return different results in the SCSM console depending on if I check from the server or a remote workstation. My next step is to build a new Orchestrator server and see if it has the same issues. ______________________________________________________________ Rob Plank Data Center Manager, Infrastructure LogixHealth ▪ 8 Oak Park Drive, Bedford, MA 01730 Phone: 781.280.1528 ▪ Fax: 781.276.6472 rpl...@logixhealth.com<mailto:rpl...@logixhealth.com> ▪ Mobile: 617.699.6102 www.logixhealth.com<http://www.logixhealth.com> ______________________________________________________________ Confidentiality notice: This communication and any accompanying document(s) are confidential and privileged. They are intended for the sole use of the addressee for business pertaining to LogixHealth. If you received this transmission in error, you are advised that any disclosure, copying, distribution, or the taking of any action in reliance upon the communication is strictly prohibited. From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Travis Wright Sent: Tuesday, August 20, 2013 2:05 PM To: servman@lists.myitforum.com<mailto:servman@lists.myitforum.com>; Anshuman Nangia Subject: [servman] RE: Service Manager and Orchestrator hiccups Coming back around to this…. For those of you that are experiencing this issue- is it happening in a production environment or is it happening in something more like a test lab/demo machine etc. that has limited HW resources? From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Robertson, Casey Sent: Monday, August 5, 2013 3:42 PM To: servman@lists.myitforum.com<mailto:servman@lists.myitforum.com> Subject: [servman] RE: Service Manager and Orchestrator hiccups Just wanted to bump this topic. Thankfully we don’t have a super busy environment because occasionally I still get failed RB automation activities with the 404 error. I started nightly reboots of the SCORCH server last week and it didn’t happen for about 5 days but today the bug is back. So I go through the truncate routine, bouncing the services, resetting IIS etc and eventually it works but even my ‘fixes’ never always work. Wish I could get to the bottom of it as resubmitting the runbooks is really a pain (esp. when they fail 3 more times before working). From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Towler, Angelia N Sent: Thursday, April 18, 2013 1:27 PM To: servman@lists.myitforum.com<mailto:servman@lists.myitforum.com> Subject: [servman] RE: Service Manager and Orchestrator hiccups Rob, thanks so much….I did not realize you can rerun the activities that is terrific information. I recently had the same issue Casey reported but it seemed to correct itself. Thanks, Angelia From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Rob Plank Sent: Tuesday, April 16, 2013 6:51 PM To: servman@lists.myitforum.com<mailto:servman@lists.myitforum.com> Subject: [servman] RE: Service Manager and Orchestrator hiccups I have had the SCSM/SCORCH connector fail where the runbooks are missing in SCSM, on me 2 times since we started our deployment of 2012 almost a year ago. I am not sure of the root cause of the issue, but I have found two solutions that have worked for me. The first time I restarted the SCORCH services and then reran the connector. The second time I ran the truncate table command on the authorizationCache then reran the SCORCH connector. After the second time I created a runbook that runs the truncate command every night before the SCORCH connector is scheduled to run. I am not sure this is the solution since I set this up somewhat recently. For the Failed SR you can open the activity tab right click the failed activity and click return to activity this will trigger the runbook to run again and the status of the SR to go to in progress. Rob ______________________________________________________________ Rob Plank Data Center Manager, Infrastructure LogixHealth ▪ 8 Oak Park Drive, Bedford, MA 01730 Phone: 781.280.1528 ▪ Fax: 781.276.6472 rpl...@logixhealth.com<mailto:rpl...@logixhealth.com> ▪ Mobile: 617.699.6102 www.logixhealth.com<http://www.logixhealth.com> ______________________________________________________________ Confidentiality notice: This communication and any accompanying document(s) are confidential and privileged. They are intended for the sole use of the addressee for business pertaining to LogixHealth. If you received this transmission in error, you are advised that any disclosure, copying, distribution, or the taking of any action in reliance upon the communication is strictly prohibited. From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com]<mailto:[mailto:listsad...@lists.myitforum.com]> On Behalf Of Robertson, Casey Sent: Tuesday, April 16, 2013 6:31 PM To: 'servman@lists.myitforum.com' (servman@lists.myitforum.com<mailto:servman@lists.myitforum.com>) Subject: [servman] Service Manager and Orchestrator hiccups At times SCSM just won’t see the Orchestrator web service. I will kick off a service request that contains a runbook. It will fail and it’s always the runbook that it says it can’t find or enumerate. If I cycle all SM services and SCORCH services they start talking again (IIS, Runbook services etc). Do any of you have this happen? Should I be proactively recycling these services? We are just about to go live with some service requests and I don’t want it to fall on its face. Thanks. P.S. – do you all have subscriptions set up or anything to notify you when a SR goes to “Failed”? Because when that first runbook step goes bad the whole SR dies. Let’s say I fix the SCSM/SCORCH connection – is there a way to kick off that SR again or is it dead and a new one needs creation? Casey ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information of Cameron and its Operating Divisions. Any unauthorized use or disclosure is prohibited. If you are not the intended recipient, please contact the sender by reply email and delete and destroy all copies of the original message inclusive of any attachments. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
