When you use windows Service Management to stop or restart WAS, a credential failure error occurs in the background.

When you use windows Service Management to stop or restart WAS, a credential failure error occurs in the background.

Recently, WAS on the company's testing server does not work when it is restarted or stopped through the windows Service Manager. Although it seems that the entire operation has been completed, the Java Process does not exist, and the background stopServer. log reports an error as follows:
* *********** Start Display Current Environment ************
Host Operating System is Windows Server 2008, version 6.1 build 7600
Java version = J2RE 1.6.0 IBM J9 2.4 Windows Server 2008 amd64-64 jvmwa6460-20080816_22093 (JIT enabled, AOT enabled)
J9VM-20080816_022093_LEdSMr
JIT-r9_20080721_1330ifx2
GC-20080724_AA, Java Compiler = j9jit24, Java VM name = IBM J9 VM
Was. install. root = C: \ Program Files \ IBM \ WebSphere \ AppServer
User. install. root = C: \ Program Files \ IBM \ WebSphere \ AppServer \ profiles \ invalid rv01
Java Home = C: \ Program Files \ IBM \ WebSphere \ AppServer \ java \ jre
Ws. ext. dirs = C :\\ Program Files \ IBM \ WebSphere \ AppServer \ java \ lib; C: \ Program Files \ IBM \ WebSphere \ AppServer \ classes; C: \ Program Files \ IBM \ WebSphere \ AppServer \ lib; C: \ Program Files \ IBM \ WebSphere \ AppServer \ installedChannels; C: \ Program Files \ IBM \ WebSphere \ AppServer \ lib \ ext; c: \ Program Files \ IBM \ WebSphere \ AppServer \ web \ help; C: \ Program Files \ IBM \ WebSphere \ AppServer \ deploytool \ IBD \ plugins \ com. ibm. ls. ejbdeploy \ runtime
Classpath = C: \ Program Files \ IBM \ WebSphere \ AppServer \ profiles \ invalid rv01 \ properties; C: \ Program Files \ IBM \ WebSphere \ AppServer \ properties; C: \ Program Files \ IBM \ WebSphere \ AppServer \ lib \ startup. jar; C: \ Program Files \ IBM \ WebSphere \ AppServer \ lib \ bootstrap. jar; C: \ Program Files \ IBM \ WebSphere \ AppServer/lib/lmproxy. jar; C: \ Program Files \ IBM \ WebSphere \ AppServer/lib/urlprotocols. jar; C: \ Program Files \ IBM \ WebSphere \ AppServer \ java \ lib \ tools. jar
Java Library path = C: \ Program Files \ IBM \ WebSphere \ AppServer \ java \ jre \ bin \ default; C: \ Program Files \ IBM \ WebSphere \ AppServer \ java \ jre \ bin ;.; c: \ Program Files \ IBM \ WebSphere \ AppServer \ bin; C: \ Program Files \ IBM \ WebSphere \ AppServer \ java \ bin; C: \ Program Files \ IBM \ WebSphere \ AppServer \ java \ jre \ bin; C: \ Windows \ system32; C: \ Windows \ System32 \ Wbem; C: \ Windows \ System32 \ WindowsPowerShell \ v1.0 \;
Current trace specification = * = info: com. ibm. * = all
* *********** End Display Current Environment *************
[14-10-17 15: 29: 49: 312 CST] 00000000 ManagerAdmin I TRAS0017I: the startup trace status is * = info: com. ibm. * = all.
[14-10-17 15: 29: 49: 343 CST] 00000000 WsServerContr 1 Executing executeUtilityOnWindows with args: C: \ Program Files \ IBM \ WebSphere \ AppServer \ profiles \ invalid rv01 \ config WIN-APKCNRO4348Node01Cell WIN-APKCNRO4348Node01 server1-fromWinService \\. \ pipe \ w6SvcPipe_29F1A_15E15-username wasadmin-password ********
[14-10-17 15: 29: 49: 343 CST] 00000000 WsServerContr 1 invokedByWindowsService has been set to true earlier
[14-10-17 15: 29: 49: 343 CST] 00000000 ManagerAdmin I TRAS0018I: The trail status has changed. The new tracking status is * = info.
[14-10-17 15: 29: 49: 500 CST] 00000000 AdminTool A ADMU0128I: starting A tool with the 2017rv01 Profile
[14-10-17 15: 29: 49: 500 CST] 00000000 AdminTool A ADMU3100I: Reading configuration from server: server1
[14-10-17 15: 29: 49: 546 CST] 00000000 ModelMgr I WSVR0801I: initializing all server configuration models
[14-10-17 15: 29: 51: 671 CST] 00000000 SSLConfig W CWPKI0041W: one or more keystore uses the default password.
[14-10-17 15: 29: 51: 687 CST] 00000000 SSLConfigMana I CWPKI0027I: Disable default host name verification for HTTPS URL connections.
[14-10-17 15: 29: 51: 703 CST] 00000000 SecurityObjec I Client code attempting to load security configuration
[14-10-17 15: 29: 53: 000 CST] 00000000 SecurityObjec I Client code attempting to load security configuration
[14-10-17 15: 29: 53: 265 CST] 00000000 WsServerStop E ADMU3002E: An exception occurred when trying to process server server1
[14-10-17 15: 29: 53: 265 CST] 00000000 WsServerStop E ADMU3007E: exception javax. management. JMRuntimeException: ADMN0022E: The stop operation of Server MBean cannot be accessed due to insufficient creden。 or empty creden.
[14-10-17 15: 29: 53: 265 CST] 00000000 WsServerStop A ADMU3007E: exception javax. management. JMRuntimeException: ADMN0022E: The stop operation of Server MBean cannot be accessed due to insufficient creden。 or empty creden.
At com. ibm. ws. management. connector. soap. SOAPConnectorClient. handleAdminFault (SOAPConnectorClient. java: 945)
At com. ibm. ws. management. connector. soap. SOAPConnectorClient. invokeTemplateOnce (SOAPConnectorClient. java: 910)
At com. ibm. ws. management. connector. soap. SOAPConnectorClient. invokeTemplate (SOAPConnectorClient. java: 675)
At com. ibm. ws. management. connector. soap. SOAPConnectorClient. invokeTemplate (SOAPConnectorClient. java: 665)
At com. ibm. ws. management. connector. soap. SOAPConnectorClient. invoke (SOAPConnectorClient. java: 651)
At com. ibm. ws. management. connector. soap. SOAPConnectorClient. invoke (SOAPConnectorClient. java: 473)
At $ Proxy0.invoke (Unknown Source)
At com. ibm. ws. management. AdminClientImpl. invoke (AdminClientImpl. java: 224)
At com. ibm. ws. management. tools. WsServerStop. sendWaitStop (WsServerStop. java: 535)
At com. ibm. ws. management. tools. WsServerStop. runTool (WsServerStop. java: 410)
At com.ibm.ws.management.tools.AdminTool.exe cuteUtility (AdminTool. java: 272)
At com.ibm.ws.management.tools.WsServerController.exe cuteUtilityOnWindows (WsServerController. java: 136)
At com. ibm. ws. management. tools. WsServerStop. main (WsServerStop. java: 118)
At sun. reflect. NativeMethodAccessorImpl. invoke0 (Native Method)
At sun. reflect. NativeMethodAccessorImpl. invoke (NativeMethodAccessorImpl. java: 45)
At sun. reflect. DelegatingMethodAccessorImpl. invoke (DelegatingMethodAccessorImpl. java: 37)
At java. lang. reflect. Method. invoke (Method. java: 599)
At com. ibm. wsspi. bootstrap. WSLauncher. launchMain (WSLauncher. java: 213)
At com. ibm. wsspi. bootstrap. WSLauncher. main (WSLauncher. java: 93)
At com. ibm. wsspi. bootstrap. WSLauncher. run (WSLauncher. java: 74)
At org. eclipse. core. internal. runtime. PlatformActivator $ 1.run( PlatformActivator. java: 78)
At org. eclipse. core. runtime. internal. adaptor. EclipseAppLauncher. runApplication (EclipseAppLauncher. java: 92)
At org. eclipse. core. runtime. internal. adaptor. EclipseAppLauncher. start (EclipseAppLauncher. java: 68)
At org. eclipse. core. runtime. adaptor. EclipseStarter. run (EclipseStarter. java: 400)
At org. eclipse. core. runtime. adaptor. EclipseStarter. run (EclipseStarter. java: 177)
At sun. reflect. NativeMethodAccessorImpl. invoke0 (Native Method)
At sun. reflect. NativeMethodAccessorImpl. invoke (NativeMethodAccessorImpl. java: 45)
At sun. reflect. DelegatingMethodAccessorImpl. invoke (DelegatingMethodAccessorImpl. java: 37)
At java. lang. reflect. Method. invoke (Method. java: 599)
At org. eclipse. core. launcher. Main. invokeFramework (Main. java: 340)
At org. eclipse. core. launcher. Main. basicexecute (Main. java: 282)
At org. eclipse. core. launcher. Main. run (Main. java: 981)
At com. ibm. wsspi. bootstrap. WSPreLauncher. launchEclipse (WSPreLauncher. java: 341)
At com. ibm. wsspi. bootstrap. WSPreLauncher. main (WSPreLauncher. java: 111)

[14-10-17 15: 29: 53: 296 CST] 00000000 AdminTool A ADMU4113E: Verify that the user name and password are correct. If you want to run the tool from the command line, pass the correct-username and-password. Alternatively, update the <conntype>. client. props file.
[14-10-17 15: 29: 53: 296 CST] 00000000 AdminTool A ADMU1211I: To obtain all traces of A fault, use the-trace option.
[14-10-17 15: 29: 53: 296 CST] 00000000 AdminTool A ADMU0211I: In file C: \ Program Files \ IBM \ WebSphere \ AppServer \ profiles \ invalid rv01 \ logs \ server1 \ stopServer. detailed error information is displayed in the log.

If this error message is returned by the Windows Server Manager, wasservice.exe transfers the wrong account or password when stopping the WAS operation.
SC qc "IBMWAS70Service-WIN-APKCNRO4348Node01"
[SC] QueryServiceConfig succeeded

SERVICE_NAME: IBMWAS70Service-WIN-APKCNRO4348Node01
TYPE: 10 WIN32_OWN_PROCESS
START_TYPE: 2 AUTO_START
ERROR_CONTROL: 1 NORMAL
BINARY_PATH_NAME: "C: \ Program Files \ IBM \ WebSphere \ AppServer \ bin \ wasse
Rvice.exe "" IBMWAS70Service-WIN-APKCNRO4348Node01"
LOAD_ORDER_GROUP:
TAG: 0
DISPLAY_NAME: IBM WebSphere Application Server V7.0-WIN-APKCNRO
4348Node01
DEPENDENCIES:
SERVICE_START_NAME: LocalSystem

Now that you have found the problem, you have to find a way to change the password, <profile_home> \ properties <conntype> modify <conntype> when you stop WAS, the SOAP connection mode is used by default. The error message reported by WAS can be verified.
At com. ibm. ws. management. connector. soap. SOAPConnectorClient. handleAdminFault (SOAPConnectorClient. java: 945)
Therefore, the attributes of soap. client. props are modified as follows:
Com. ibm. SOAP. loginUserid = username
Com. ibm. SOAP. loginPassword = password
After the password is changed, the plaintext storage may cause security risks. Therefore, use <profile_home> \ PropFilePasswordEncoder. bat to encrypt the password. Run the following command:
<Profile_home> \ PropFilePasswordEncoder. bat .. \ properties \ soap. client. props com. ibm. SOAP. loginPassword-noBackup
When the file is opened, the password is encrypted.
Com. ibm. SOAP. loginPassword = {xor} lz4ce-gwlts =
Therefore, when you call the <profile_home> \ Taobao help document on the command line, it is found that the password used to stop WAS is not referenced by <profile_home> \ properties \ soap. client. the password in the props file WAS specified before WAS installed. At this time, I suddenly remembered that the administrator password WAS modified once after WAS installed, use the command to modify the user name and password specified when WAS is stopped.
WASService.exe-add "WIN-APKCNRO4348Node01"-serverName server1-profilePath "C: \ Program Files \ IBM \ WebSphere \ AppServer \ profiles \ invalid rv01"-stopArgs "-username wasadmin-password"-encodeParams
This command should be noted that when the serviceName followed by the add parameter already exists, the update operation is executed, and the problem is solved here, it is also effective to stop and restart windows service management. The Final Cause analysis is that, after the wasings are installed, the administrator password is modified, and the password called by wasservice.exe is outdated, so the credential is invalid.

Windows 7 SP1 installation and update failed error code 80070003 urgent solution

The symptom of this problem is that windows prompts an update, but it cannot be updated at all times.

This code is generated to update temporary files on the computer: You need to delete the temporary files Windows uses to identify computer updates.

To delete a temporary file, stop the Windows Update Service, delete the temporary Update file, restart the Windows Update service, and then try again to check Windows updates.

The following describes the specific operations!

1. Stop the Windows Update Service

Log on as an administrator to perform these steps. Click Start, click Control Panel, system, and maintenance, and then click Administrative Tools to open administrative tools ". Double-click "service ". If the system prompts you to enter or confirm the administrator password, enter the password or provide confirmation. Right-click the Windows Update Service and click "stop ".

2. Delete temporary update files

C: \ Windows \ SoftwareDistribution \ DataStore delete all files in this folder. If the system prompts you to enter or confirm the administrator password, enter the password or provide confirmation. Click the back button. In the SoftwareDistribution folder, double-click the Download folder to open it and delete all the files in the folder. If the system prompts you to enter or confirm the administrator password, enter the password or provide confirmation.

3. Restart the Windows Update Service

You must log on as an administrator to perform this operation. Click Start, click Control Panel, system, and maintenance, and then click Administrative Tools to open administrative tools ". Double-click "service ". If the system prompts you to enter or confirm the administrator password, enter the password or provide confirmation. Right-click the Windows Update Service and click Start ".

It is best to restart the computer and enable Windows Update.

How can I enable a WINDOWS Background Service to automatically restart after it fails to run (Stops?

The simplest thing is to download a 360 security guard
"Advanced" on its interface --- system service status
You can see the name and function of each service.
Use it again