解决rpc服务（Resolving the RPC service）

解决rpc服务（Resolving the RPC service） 解决rpc服务(Resolving the RPC service) The RPC server must not be resolved on the 2007-11-12 11:03 solution Method 1: modify the registry Run registry editor, open the HKEY_LOCAL_MACHINEsystemCurrentControl - SetServicesRpcSs branch, amend the Start item value from the "4" to "2", which set the startup type to automatic, reboot the system. Method 2: use the "SC" command Enter the command prompt window and type the "sc config RpcSs start = auto" command, which will show the "sc ChangeServiceConfig SUCCESS" so that the RPC service can be enabled successfully. Method 3: use the failover console Take Windows 2003 as an example, start with a cd-rom, enter the Windows 2003 installation interface, press the "R" button to log in to the failover console. In the failover control stage, type "enable RpcSs service_auto_start" command, then type "exit" command, restart the system, login in normal mode, and enable RPC service successfully. Second, there is a question on the Internet that has the following problem. If there is a problem, do it his way. "I didn't succeed in using any of the above methods, so I thought I'd have to do it by myself. I would like to see some key values in my list change so that they can be enabled. Restore the pre-disabled backup registry to the disabled registry, indicating that it cannot be imported and unsuccessful. Unable to enable. The disable before and after disabling two registry (branch), only take HKEY_LOCAL_MACHINESYSTEM content into a Word document, and then use the Word "compare and merge document" in the function, can automatically find the difference between two registry. Through comparative analysis, I found that there are the following branches in the disabled registry: 1. HKEY_LOCAL_MACHINESYSTEMCurr - entControlSetHardwareProfiles001SystemCurrentControlSetEnumROOTLEGACY_RPCSS 2. HKEY_LOCAL_MACHINESYSTEMCurr - entControlSetHardwareProfilesCurrentSystemCurrentControlSetEnumROOTLEGACY_RPCSS There are no two branches in the previous registry. With further action, you find that you can restart the RPC service if you remove the first branch. The previous three methods only apply to the case where the RPC service boot type has been changed to a ban. The author closes the RPC service not to change the boot type, but to prohibit the hardware configuration file service associated with it, and the value of the "Start" item is still "2", unchanged. So to enable RPC service, you first need to enable the hardware configuration file service. " Once again, I find that I can't solve my problem by using the above two steps. What should I do? I found the crux of the problem through my own analysis. In fact, the above two-step implementation is based on the Dcom service. Similarly, the Dcom service is also in the service, in the "start" - "run" to enter "services. MSC", to find a service project starting with Dcom, and change to "manual" mode, Then "start" the service. That's it! Solution 2 To solve this problem, follow these steps: 1. Click start, click run, type the following command line in the open box, and then click ok: Net start RPCSS Test to see if this solves the problem. If this problem is still present, proceed to the next step. Click start, point to the program, point to the attachment, and then click the command prompt. At the command prompt, type the ping servername, where the servername is to test its connected server, NetBIOS, DNS, or GUID name. If one of the computers has a connection problem, contact your network administrator to solve the problem. If this problem is still present, proceed to the next step. 4. Use the Netdiag tool included in the Microsoft Windows support tool (included in the Windows cd-rom) to determine whether the domain controller is working properly. You can use MSRPC, DNS, NBT, LDAP or TCP protocol to perform network tracing. If the domain controller has problems, contact the network administrator to solve the problem. If this problem is still present, proceed to the next step. 5. Use the Netdom tool included in the Windows support tool to verify network trust relationships and then reset or build connections to the server. For more information You may need to create secondary DNS zones to properly name parsing between multiple domains or forests. On the primary DNS server in each domain, create a secondary area for your attempt to create a domain for trusting relationships. For example, create a secondary area similar to the following areas:? Domain1 DC1.Domain1.com - hosts the DNS main area of Domain1.com ? Domain2 DC1.Domain2.com The RPC server is not available for 2007-11-12 11:03 Solution 1 Method 1: modify the registry Run registry editor, open the HKEY_LOCAL_MACHINEsystemCurrentControl - SetServicesRpcSs branch, amend the Start item value from the "4" to "2", which set the startup type to automatic, reboot the system. Method 2: use the "SC" command Enter the command prompt window and type the "sc config RpcSs start = auto" command, which will show the "sc ChangeServiceConfig SUCCESS" so that the RPC service can be enabled successfully. Method 3: use the failover console Take Windows 2003 as an example, start with a cd-rom, enter the Windows 2003 installation interface, press the "R" button to log in to the failover console. In the failover control stage, type "enable RpcSs service_auto_start" command, then type "exit" command, restart the system, login in normal mode, and enable RPC service successfully. Second, there is a question on the Internet that has the following problem. If there is a problem, do it his way. "I didn't succeed in using any of the above methods, and it seemed that I had solved it myself. I think some key values in the registry must change so that they can be enabled. Restore the pre-disabled backup registry to the disabled registry, indicating that it cannot be imported and unsuccessful. Unable to enable. The disable before and after disabling two registry (branch), only take HKEY_LOCAL_MACHINESYSTEM content into a Word document, and then use the Word "compare and merge document" in the function, can automatically find the difference between two registry. Through comparative analysis, I found that there are the following branches in the disabled registry: 1. HKEY_LOCAL_MACHINESYSTEMCurr - entControlSetHardwareProfiles001SystemCurrentControlSetEnumROOTLEGACY_RPCSS 2. HKEY_LOCAL_MACHINESYSTEMCurr - entControlSetHardwareProfilesCurrentSystemCurrentControlSetEnumROOTLEGACY_RPCSS There are no two branches in the previous registry. With further action, you find that you can restart the RPC service if you remove the first branch. The previous three methods only apply to the case where the RPC service boot type has been changed to a ban. The author closes the RPC service not to change the boot type, but to prohibit the hardware configuration file service associated with it, and the value of the "Start" item is still "2", unchanged. So to enable RPC service, you first need to enable the hardware configuration file service. " Once again, I find that I can't solve my problem by using the above two steps. What should I do? I found the crux of the problem through my own analysis. In fact, the above two-step implementation is based on the Dcom service. Similarly, Dcom that service is in service, in the "start" - "run" input "services. MSC", to find a service project, starting with Dcom is changed to "manual" mode, and then "start" service. That's it! Solution 2 To solve this problem, follow these steps: 1. Click start, click run, type the following command line in the open box, and then click ok: Net start RPCSS Test to see if this solves the problem. If this problem is still present, proceed to the next step. Click start, point to the program, point to the attachment, and then click the command prompt. At the command prompt, type the ping servername, where the servername is to test its connected server, NetBIOS, DNS, or GUID name. If one of the computers has a connection problem, contact your network administrator to solve the problem. If this problem is still present, proceed to the next step. 4. Use the Netdiag tool included in the Microsoft Windows support tool (included in the Windows cd-rom) to determine whether the domain controller is working properly. You can use MSRPC, DNS, NBT, LDAP or TCP protocol to perform network tracing. If the domain controller has problems, contact the network administrator to solve the problem. If this problem is still present, proceed to the next step. 5. Use the Netdom tool included in the Windows support tool to validate network trust relationships and then reset or establish a connection to the server. For more information You may need to create secondary DNS zones to properly name parsing between multiple domains or forests. On the primary DNS server in each domain, create a secondary area for your attempt to create a domain for trusting relationships. For example, create a secondary area similar to the following areas:? Domain1 DC1.Domain1.com - hosts the DNS main area of Domain1.com ? Domain2 DC1.Domain2.com - hosts the DNS primary area of Domain2.com When the trust relationship is established or validated, the two areas may receive the following message: The RPC Server is unavailable To solve this problem, configure the secondary area as follows:? Domain1 DC1.Domain1.com - a secondary area of Domain1.com's DNS main area and Domain2.com ? Domain2 DC1.Domain2.com - a secondary area of Domain2.com's DNS main area and Domain1.com When DNS name resolution is properly configured for these two domains, they can communicate with each other - host Domain2.com's DNS primary area When the trust relationship is established or validated, the two areas may receive the following message: The RPC Server is unavailable To solve this problem, configure the secondary area as follows:? Domain1 DC1.Domain1.com - a secondary area of Domain1.com's DNS main area and Domain2.com ? Domain2 DC1.Domain2.com - a secondary area of Domain2.com's DNS main area and Domain1.com When DNS name resolution is correctly configured for these two domains, they can communicate with each other The cold standby data must be that the database is not open. The following steps provide a detailed process. The cold standby data must be that the database is not open. The following steps will give you a detailed process: (1) close DB: shutdown immediate; (2) : copy oradata all files in the directory, including data files, control files, redo, and so on, also need to copy the password file The PWD file of the database under the directory ora92. All copy to a security directory. In SQL, you can simply add a host and use the DOS command. If the host copy... (3) : if the operating system is reinstalled, as long as it is the same system, the same database version can be used for cold standby recovery. The next step is to re-install the system. (4) : normal install oracle software (in the pub before a brother said don't need to install the oracle, you could just doubt), only need to install the software, can need not build instance, build instance is also long, also not necessary. Once the software has been installed, it is ready to resume. (5) : data coverage used to include PWD files, in the original directory. If the directory changes, you need to set up control files and modify pfile. (6) establishment of service: using oradim command, under the CMD, oradim-new-sid erp is established to establish a service, and sid is erp. An additional explanation is given for the oradim command. (7) : establish the listening: net configuration assintant, or use the script to establish and open. (8) open database: with OEM or CMD. The set is = erp; Up sqlplus "/ as sysdba"; Startup; Select * from v $instance; So far, cold backup has been successful. Even if you're now using an OEM to open your database, you can't find the sid, but you've already made it, and you just need to reboot your server.