Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Tuesday, March 12, 2019 10:19 AM
Hi everyone,
i get an Error when opening the Console:
[httpWebRequest_WebException_RemoteServer]
Arguments: NotFound
Debugging resource strings are unavailable. Often the key and arguments provide sufficient information to diagnose the problem
See http://go.microBLAHBLAH
Having the same issue as written in here: https://social.technet.microsoft.com/Forums/en-US/c3afc430-5811-4c8c-a797-79c98459d792/console-fails-to-open-error-executing-the-current-operation?forum=scogeneral
I tried every suggested solution, but it didn't work for me.
- Checked Account in IIS like in http://technet.microsoft.com/de-de/library/hh473578.aspx
- Changed ApplicationPool in Advanced Settings of the WebSites in IIS to "System Center 2012 Orchestrator Web Features"
- Checked Identity in the Application pool if it is my service account with the correct Access Rights to Orchestrator DB
- Doublechecked if Service Account has "log on as batch Job" Rights on the server
- Even reinstalled Web-Services and Orchestration console (version 1801) but still no luck.
Has anybody any more ideas?
All replies (30)
Tuesday, March 12, 2019 10:37 AM | 2 votes
Hello!
Did you try running the following SQL query on the Orchestrator database?
GRANT EXECUTE ON object::[Microsoft.SystemCenter.Orchestrator].[GetSecurityToken] TO [Microsoft.SystemCenter.Orchestrator.Operators]
GRANT SELECT ON object::[Microsoft.SystemCenter.Orchestrator.Internal].[Settings] TO [Microsoft.SystemCenter.Orchestrator.Operators]
Best regards,
Leon
Blog: https://thesystemcenterblog.com LinkedIn:
Tuesday, March 12, 2019 12:17 PM | 1 vote
Hi,
can you open http://NameOfOrchestratorWebService:81/orchestrator2012/orchestrator.svc ?
Regards
Stefan
More and news about System Center at stillcool.de and sc-orchestartor.eu .
Tuesday, March 12, 2019 12:21 PM
Thank you for your answer!
I did not try that until now. But it didn't do the trick. Still same issue.
Tuesday, March 12, 2019 12:23 PM
Hi,
thank you for your answer. I am able to open it.
Is this what it should look like?
Tuesday, March 12, 2019 12:28 PM
Could you check which application pool the Orchestrator Web Console is using in IIS?
Blog: https://thesystemcenterblog.com LinkedIn:
Tuesday, March 12, 2019 1:20 PM
Hey,
it was the Default AppPool, and I found in the other thread that you should change it to 
Tuesday, March 12, 2019 1:26 PM
Did it help? Might want to restart IIS completely by running the command: iisreset
Blog: https://thesystemcenterblog.com LinkedIn:
Tuesday, March 12, 2019 1:29 PM
No :-) It should not be "Request Error": http://sc-orchestrator.vasoft.de/request-error-while-opening-orchestrator-web-services/
More and news about System Center at stillcool.de and sc-orchestartor.eu .
Tuesday, March 12, 2019 1:34 PM
Already did so, but no change for my issue. Still the same.
Tuesday, March 12, 2019 1:36 PM
Oh ok. So one more symptom. The the SQL Query didn't help. The SQL commands executed successfully though.
Tuesday, March 12, 2019 1:42 PM
Another step you may want to do is in IIS Manager go to that application pool System Center 2012 Orchestrator Web Features and click Advanced Settings.
Find the Process Model -> Identity, this should be the service account from Orchestrator.
Go into that by selecting the radio button […] button in that line and re-enter the username and password.
Also check the web.config file
(C:\Program Files (x86)\Microsoft System Center 2012 R2\Orchestrator\Orchestration Console\web.config)
You should have a line like this:
<add key="ScoServiceUri" value="http://SERVERNAME1:81/Orchestrator2012/Orchestrator.svc"/>
You can try changing it to use FQDN, like this:
<add key="ScoServiceUri" value="http://servername.domain.name:81/Orchestrator2012/Orchestrator.svc"/>
Then save the file, restart the services or the whole server and try again.
Blog: https://thesystemcenterblog.com LinkedIn:
Tuesday, March 12, 2019 1:45 PM
Thanks for the good hints, but I already tried that as suggested in these threads
and
So it did not work for me.
Tuesday, March 12, 2019 1:45 PM
But it works now, right?
Your solution was to change the AppPool for Orchestrator Web Services to "System Center Orchestrator Web Featues" as Leon suggested?
Regards,
Stefan
More and news about System Center at stillcool.de and sc-orchestartor.eu .
Tuesday, March 12, 2019 2:13 PM
Hi Stefan,
no it did not work! I still have the issue.
I also doublechecked the identity, which has correct permissions on the Orchestrator Database.
Tuesday, March 12, 2019 2:29 PM
What permissions does it have in the Orchestrator database?
By the way, did you try running Internet Explorer as administrator?
Blog: https://thesystemcenterblog.com LinkedIn:
Tuesday, March 12, 2019 2:36 PM
Permission in SQL DB is sysadmin
Didn't try "Run as Administrator" until now. So I ran as Admin but still no change. Thanks for the idea anyway.
Tuesday, March 12, 2019 2:56 PM
The strange thing is that your Orchestrator Web Service URL is also giving an error.(http://orchestratorserver:81/orchestrator2012/orchestrator.svc)
Are you trying to access the URL from a remote computer or from within the Orchestrator management server?
Did you try using all the following URLs?
- http://localhost:82 (Locally)
- http://orchestratorserver:82 (Locally and Remotely)
- http://orchestratorserver.domain.com:82 (Locally and Remotely)
If you have any firewall, try disabling it temporarily, did you check that nothing else is using these ports?
Blog: https://thesystemcenterblog.com LinkedIn:
Tuesday, March 12, 2019 4:36 PM
Hi,
before Orchestrator Web Services with http://localhost:81/orchestrator2012/orchestrator.svc will not look like below it will not work.
Below the AppPool from a Demo-System:
Does "Test settings" for the Basic settings of the site work?
Regards,
Stefan
More and news about System Center at stillcool.de and sc-orchestartor.eu .
Tuesday, March 12, 2019 4:45 PM
Also make sure the Orchestrator services and the SQL Server services are running, this exact behavior can happen if the services are not running (tested in my lab just now).
Blog: https://thesystemcenterblog.com LinkedIn:
Wednesday, March 13, 2019 9:19 AM
Thanks for your effort!
But still no success. Same Error with all of the suggested URLs remotely and local.
I checked if Port is not used by another process. It is not.
Windows Firewall is disabled for Testing. Port is not blocked:
Wednesday, March 13, 2019 9:27 AM
Thank you for your answer... and special thanks for the screenshots of your working Demo environment :)
but my configuration looks just as yours (with some extra Settings you demo-env. does not list.
Wednesday, March 13, 2019 9:32 AM
I checked:
Looks good, they are running. SQL Database is also running, and I'm able to browse through my runbooks with Runbook designer, so I assume Database is up and running.
But still no Working WebService.
I currently cannot check the services on the SQL Server. But I will as soon as I can.
Thank you guys a lot for trying to help me out :)
Wednesday, March 13, 2019 3:55 PM | 1 vote
Hi,
you're welcome!
you wrote that you already "- Checked Account in IIS like in http://technet.microsoft.com/de-de/library/hh473578.aspx"
It looks like below, right? Especially the highlighted part:
"povider connection string="Data Source=NameOfSqlServer\InstanceIfyouhave;Initial Catalog=Orchestrator;Integrated Security=True;"
Regards,
Stefan
More and news about System Center at stillcool.de and sc-orchestartor.eu .
Thursday, March 14, 2019 10:06 AM
Yeah I just checked it again in case I was somehow missing something:
Thursday, March 14, 2019 12:29 PM
so strange...
Anything useful in the logs if you enable and activate Failed Request Tracing Rules in IIS for Site Microsoft System Center Orchestrator Web Service: https://benperk.github.io/msdn/2012/2012-01-enable-and-activate-failed-request-tracing-rules.html
?
Regards,
Stefan
More and news about System Center at stillcool.de and sc-orchestartor.eu .
Thursday, March 14, 2019 12:38 PM
Might have to back track a bit, how did you install Orchestrator? Did you follow some guide or just by yourself? Were all prerequisites met? Is both hardware and software supported/compatible?
Blog: https://thesystemcenterblog.com LinkedIn:
Thursday, March 14, 2019 2:38 PM
I "just installed" it. had some issues and you two tried to help me out before:
https://social.technet.microsoft.com/Forums/en-US/32520f5e-f1c1-4dde-bc06-87193788047c/orchestrator-web-console-cannot-be-installed?forum=scodeployment
there it was a GPO hiding C:\ which caused the issue...
Maybe it is something like this again.
Thursday, March 14, 2019 2:40 PM
GPOs can cause various of problems yes, maybe you should go through all the GPOs that are applied to the server and check if there's anything that could be blocking.
Blog: https://thesystemcenterblog.com LinkedIn:
Thursday, March 14, 2019 2:41 PM
Thanks for the hint, but I will not pursue this any further, as my time is running out. The customer told my I should quit Troubleshooting. We will install SCORCH 2019 as soon as it is released.
Without his help I cannot do any further troubleshooting the issue as I need his help to connect to Environment.
If anything should change here I will post it.
Thanks for your time and help so far!
Thursday, March 14, 2019 2:46 PM
You're welcome, sorry for not being able to solve this issue for now.
I will also perform an Orchestrator 2019 installation at a customer soon!
What I would recommend is to document everything so that you can easily check what you have done in case it still doesn't work or something starts failing later on.
Blog: https://thesystemcenterblog.com LinkedIn: