Shulou(Shulou.com)06/03 Report--

Fix System Center Orchestrator Runbook Service Error%-2147467259 And HttpWebRequest_WebException_RemoteServer phenomenon and background update Orchestrator 2012 R2 KB4047356, while applying the KB4058494 service Orchestrator Runbook Service can not start, check the system log found the following error: the Orchestrator Runbook Service service stopped due to the following error:%-2147467259 according to the instructions in Kb2702157, it should be the problem of database connection. So we looked at the log file under C:\ ProgramData\ Microsoft System Center 2012\ Orchestrator\ RunbookService.exe\ Logs and found the following error. Process ID: 25104Version: 7.2.239.0Computer: SC2012ORC01User: MSFUNDS\ orchestratorService2018-05-27 11:40:01 [3752] 1 Exception caught in long _ _ thiscall COpalisActionService2Module::PreMessageLoop (int) throw () OpalisActionService2.cpp (3752): Opalis::Exceptionclass std::basic_string _ _ cdecl `anonymous-namespace'::getConnectionString (void) ActionServerRegistrar.cpp (31) _ com_error this computer cannot communicate with the computer providing the server. -2147467235 solution prompts KB to install SQL Server native Client according to the information in the following Microsoft Forum post. So I installed sql server native client, downloaded x64 with version 2012, and found that rebooting Orchestrator Runbook Service still reported an error. Refer to another piece of information in the above post: "After the Orchestrator updates are installed, reconfigure the Orchestrator database by using the existing database according to these guidelines.", reconfigure the database according to this document, enter the database host address, select to use the existing database, and then choose to overwrite the existing data. Then start Orchestrator Runbook Service problem resolution. Find a new problem access Orchesrtator web Console prompt HttpWebRequest_WebException_RemoteServer to solve a new problem when this document is found to reconfigure the database, web uses a different configuration from the local application, and web uses an IIS connection string. I found in iis that the existing connection string configuration is set to local SQLEXPRESS. Decrypt the database connection string PS C:\ > C:\ Windows\ Microsoft.NET\ Framework\ v4.0.30319\ aspnet_regiis.exe-pdf "connectionStrings"C:\ Program Files (x86)\ Microsoft System Center 2012 R2\ Orchestrator\ Web Service\ Orchestrator2012" Microsoft (R) ASP.NET RegIIS version 4.0.30319.36415Administration utility to install and uninstall ASP.NET on the local machine.Copyright (C) Microsoft Corporation in webservice. All rights reserved.Decrypting configuration section...Succeeded! Refer to this document to modify the database connection string of webservice

4. Encrypt the connection string of IIS after modification.

C:\ Windows\ Microsoft.NET\ Framework\ v4.0.30319\ aspnet_regiis.exe-pef "connectionStrings"C:\ Program Files (x86)\ Microsoft System Center 2012 R2\ Orchestrator\ Web Service\ Orchestrator2012" follow steps similar to the above to change the database connection string of web Console's website # first decrypt the string C:\ Windows\ Microsoft.NET\ Framework\ v4.0.30319\ aspnet_regiis.exe-pdf " ConnectionStrings "C:\ Program Files (x86)\ Microsoft System Center 2012 R2\ Orchestrator\ Orchestration Console" # modify the database connection string used by the web Console website # the database connection string used to encrypt the web Console website C:\ Windows\ Microsoft.NET\ Framework\ v4.0.30319\ aspnet_regiis.exe-pef "connectionStrings"C" :\ Program Files (x86)\ Microsoft System Center 2012 R2\ Orchestrator\ Orchestration Console After restarting IIS and all orchesrator services, it was found that the access webconsole still reported an error. Solve the problem after executing the following SQL command on the orchestrator database GRANT EXECUTE ON object:: [Microsoft.SystemCenter.Orchestrator]. [Settings] TO [Microsoft.SystemCenter.Orchestrator.Operators] GRANT SELECT ON object:: [Microsoft.SystemCenter.Orchestrator.Internal]. [Settings] TO [Microsoft.SystemCenter.Orchestrator.Operators] finally concluded that the KB4047356 RU is not careful enough, and the Orchestrator prompts are not comprehensive, and the focus is on the corner.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.