Tag Archives: service

Use sc command under CMD, report openservice failed 1060 error

Use sc command under CMD to delete the tomcat service and report openservice failed 1060 error
Reason: The status of the Tomcat service in the service is disabled. If the status is changed to automatic, sc DELETE Tomcat can be used
Note: Although the service name is Apache Tomcat, you do not need to add Apache when removing the Tomcat service
Conclusion:
There are two ways to delete Windows services:
Option 1: start — run — cmd.exe with the Windows command
, then type sc to see it. The method is simple:
sc delete “Service name” (if there is a space in the Service name, you need to put quotes around it)
as above: sc delete Service

open the registry editor and find the following key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services generally the service will display a key with the same name here, just delete the key directly.

Macfee can not be upgraded, the prompt returns an error

Macfee can not be upgraded, the error is returned, uninstall and reinstall, the upgrade prompt becomes “Initialization of the general update program subsystem failed, make sure the McAfee Franework service is running. “. Going into the Service Console to manually start McAfee’s Common Frame service, the service cannot be started.

Official error message:

Corporate KnowledgeBase
ERROR: McAfee Common Framework returns error ffff95b @ 2 (issue: FrameworkManifest.xml corrupt)

Enterprise Knowledge Base ID: KB54520
Published: August 8, 2008

environment
McAfee Common Management Agent 3.60
McAfee VirusScan Enterprise 8.5i
McAfee VirusScan Enterprise 8.0i
McAfee VirusScan Enterprise 8.0i
The following error occurs after starting AutoUpdate:
McAfee Common Framework returns error ffff95b @ 2.(FrameworkManifest.xml corrupt).
Public Updater Subsystem Initialization Failure

Confirm that McAfee Framework services are running
Problem 2
Subsequent errors when trying to start the McAfee Framework service:
Unable to start McAfee Framework service on local computer

<p The system could not find the specified file.
Question No. 3

The following update method will cause an automatic error:
Right-click the McShield icon in the system tray and select Update Now
Right click on McCafe’s automation console and click on Start.

Create a new scheduled task to edit an existing property Automated tasks

Cause FrameworkManifest.xml has become corrupted.
Solution 1
McAfee Agent 4.0

McAfee Agent 4.0 design changes will prevent corruption of the FrameworkManifest.xml file.
Retrieved from www.mcafee.com网站下载McAfee代理, see KB54808. </ p>

Solution 2

General Management Agent

Solution 1 – Get frameworkmanife.xml from another computer:
Find another Virus Scanning Enterprise (VSE) computer where the update job is error-free. Copy FrameworkManifest.xml from the following path:

For VSE 8.5i (running on Windows Vista)
x:/Program Data/McAfee/Common Framework

x:/Documents and Settings/All Users/Application Data/McAfee/Generic Framework</font bb1 For VSE 8.5i (runs on Windows XP and earlier)
x:/documents and settings/all users/application data/McAfee/generic framework</font

Paste the file into a portable media or network share file that can be accessed by two computers.
Click Start, Run, type Service. , and click OK.
Right-click the McAfee Framework Service and select Stop.
Copy FrameworkManifest.xml to the public framework directory.
Right-click McAfee Framework Service and select Start.
Update the product. </ font> </ p>

Solution 2 – Delete FrameworkManifest.xml and reinstall the Common Management Agent (CMA)
It is necessary to remove FrameworkManifest.xml, as it may not be removed or replaced when uninstalling/reinstalling. </ font> </ p>

Step 1 – Allow to modify VSE files and settings (only VirusScan Enterprise 8.5i and above) </p

Click on Start, Programs, McAfee, VirusScan Console.
Right-click on Access Protection and select Properties.
Select Common Criteria Protection.
Select “Prevent modification of McAfee files and settings” and disable this option.
Click OK.

Step 2 – Delete FrameworkManifest.xml and reinstall CMA:
Remove FrameworkManifest.xml from the following path:

For VSE 8.5i (running on Windows Vista)
x:/Program Data/McAfee/Common Framework

x:/Documents and Settings/All Users/Application Data/McAfee/General Framework font bb1 For VSE 8.5i (runs on Windows XP and earlier)
x:/documents and settings/all users/application data/McAfee/generic frameworkfont

Font Restart your computer.
Reinstall the Common Management Agent (CMA)/ePO agent.
Note: The CMA can be downloaded from the McAfee download site. See KB54808.
Previous Document ID
5432392
Please take a moment to fill out this form to help us serve you better.

The original introductory page for the official font workaround is
https://kc.mcafee.com/corporate/index?page=content& id = KB54520

Translated with www.DeepL.com/Translator (free version)

Caused by: org.apache.catalina.LifecycleException: A child container failed during start

a project I did before was given to a college student as the graduation device. When running on her computer, I reported the following error message. The following is the complete error message:

tomcat starts the following error:

十月 04, 2018 10:14:45 下午 org.apache.catalina.core.AprLifecycleListener init
信息: The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: C:\Program Files\Java123\jdk1.8.0_31\bin;C:\WINDOWS\Sun\Java\bin;C:\WINDOWS\system32;C:\WINDOWS;C:/Program Files/Java123/bin/server;C:/Program Files/Java123/bin;C:/Program Files/Java123/lib/amd64;C:\ProgramData\Oracle\Java\javapath;C:\乱七八糟的东西\好好学习天天向上\GIS开发与编程\2\supermap-iobjectsdotnet-9.0.0-15321-63946-win-zip-chs\Bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\Program Files\Microsoft SQL Server\110\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\110\Tools\Binn\;C:\Program Files\Microsoft SQL Server\110\Tools\Binn\;C:\Program Files (x86)\Microsoft SQL Server\110\Tools\Binn\ManagementStudio\;C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\PrivateAssemblies\;C:\Program Files (x86)\Microsoft SQL Server\110\DTS\Binn\;C:\WINDOWS\system32\config\systemprofile\.dnx\bin;C:\Program Files\Microsoft DNX\Dnvm\;C:\Program Files\Java\jdk1.7.0_79\bin;C:\Program Files\Java\jdk1.7.0_79\jre\bin;C:\Program Files (x86)\Common Files\Autodesk Shared\;C:\Program Files\MySQL\MySQL Utilities 1.6\;C:\WINDOWS\System32\OpenSSH\;C:\Program Files\Java123\jdk1.8.0_31\bin;C:\Program Files\Java\jdk1.7.0_79\jre\bin;C:\Program Files (x86)\Microsoft Visual Studio\Common\Tools\WinNT;C:\Program Files (x86)\Microsoft Visual Studio\Common\MSDev98\Bin;C:\Program Files (x86)\Microsoft Visual Studio\Common\Tools;C:\Program Files (x86)\Microsoft Visual Studio\VC98\bin;%USERPROFILE%\AppData\Local\Microsoft\WindowsApps;;C:\Users\30801\Desktop\eclipse;;.
十月 04, 2018 10:14:45 下午 org.apache.tomcat.util.digester.SetPropertiesRule begin
警告: [SetPropertiesRule]{Server/Service/Engine/Host/Context} Setting property 'source' to 'org.eclipse.jst.jee.server:cunity' did not find a matching property.
十月 04, 2018 10:14:46 下午 org.apache.coyote.AbstractProtocol init
信息: Initializing ProtocolHandler ["http-bio-8080"]
十月 04, 2018 10:14:46 下午 org.apache.coyote.AbstractProtocol init
信息: Initializing ProtocolHandler ["ajp-bio-8009"]
十月 04, 2018 10:14:46 下午 org.apache.catalina.startup.Catalina load
信息: Initialization processed in 1126 ms
十月 04, 2018 10:14:46 下午 org.apache.catalina.core.StandardService startInternal
信息: Starting service Catalina
十月 04, 2018 10:14:46 下午 org.apache.catalina.core.StandardEngine startInternal
信息: Starting Servlet Engine: Apache Tomcat/7.0.27
十月 04, 2018 10:14:46 下午 org.apache.catalina.util.SessionIdGenerator createSecureRandom
信息: Creation of SecureRandom instance for session ID generation using [SHA1PRNG] took [229] milliseconds.
十月 04, 2018 10:14:49 下午 org.apache.catalina.core.ContainerBase startInternal
严重: A child container failed during start
java.util.concurrent.ExecutionException: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/cunity]]
	at java.util.concurrent.FutureTask.report(FutureTask.java:122)
	at java.util.concurrent.FutureTask.get(FutureTask.java:192)
	at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:1128)
	at org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:782)
	at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
	at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1566)
	at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1556)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)
Caused by: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/cunity]]
	at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154)
	... 6 more
Caused by: org.apache.tomcat.util.bcel.classfile.ClassFormatException: Invalid byte tag in constant pool: 15
	at org.apache.tomcat.util.bcel.classfile.Constant.readConstant(Constant.java:131)
	at org.apache.tomcat.util.bcel.classfile.ConstantPool.<init>(ConstantPool.java:60)
	at org.apache.tomcat.util.bcel.classfile.ClassParser.readConstantPool(ClassParser.java:209)
	at org.apache.tomcat.util.bcel.classfile.ClassParser.parse(ClassParser.java:119)
	at org.apache.catalina.startup.ContextConfig.processAnnotationsStream(ContextConfig.java:2032)
	at org.apache.catalina.startup.ContextConfig.processAnnotationsJar(ContextConfig.java:1923)
	at org.apache.catalina.startup.ContextConfig.processAnnotationsUrl(ContextConfig.java:1891)
	at org.apache.catalina.startup.ContextConfig.processAnnotations(ContextConfig.java:1877)
	at org.apache.catalina.startup.ContextConfig.webConfig(ContextConfig.java:1270)
	at org.apache.catalina.startup.ContextConfig.configureStart(ContextConfig.java:855)
	at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:345)
	at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
	at org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90)
	at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5161)
	at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
	... 6 more

十月 04, 2018 10:14:49 下午 org.apache.catalina.core.ContainerBase startInternal
严重: A child container failed during start
java.util.concurrent.ExecutionException: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost]]
	at java.util.concurrent.FutureTask.report(FutureTask.java:122)
	at java.util.concurrent.FutureTask.get(FutureTask.java:192)
	at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:1128)
	at org.apache.catalina.core.StandardEngine.startInternal(StandardEngine.java:302)
	at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
	at org.apache.catalina.core.StandardService.startInternal(StandardService.java:443)
	at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
	at org.apache.catalina.core.StandardServer.startInternal(StandardServer.java:732)
	at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
	at org.apache.catalina.startup.Catalina.start(Catalina.java:675)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:483)
	at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:322)
	at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:450)
Caused by: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost]]
	at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154)
	at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1566)
	at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1556)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)
Caused by: org.apache.catalina.LifecycleException: A child container failed during start
	at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:1136)
	at org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:782)
	at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
	... 6 more

十月 04, 2018 10:14:49 下午 org.apache.catalina.startup.Catalina start
严重: Catalina.start: 
org.apache.catalina.LifecycleException: Failed to start component [StandardServer[8005]]
	at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154)
	at org.apache.catalina.startup.Catalina.start(Catalina.java:675)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:483)
	at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:322)
	at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:450)
Caused by: org.apache.catalina.LifecycleException: Failed to start component [StandardService[Catalina]]
	at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154)
	at org.apache.catalina.core.StandardServer.startInternal(StandardServer.java:732)
	at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
	... 7 more
Caused by: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina]]
	at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154)
	at org.apache.catalina.core.StandardService.startInternal(StandardService.java:443)
	at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
	... 9 more
Caused by: org.apache.catalina.LifecycleException: A child container failed during start
	at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:1136)
	at org.apache.catalina.core.StandardEngine.startInternal(StandardEngine.java:302)
	at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
	... 11 more

十月 04, 2018 10:14:49 下午 org.apache.catalina.startup.Catalina start
信息: Server startup in 3828 ms

for this reason, I searched for this mistake for a whole day, also went to the Internet to look for, saw a lot of solutions on the Internet, I also summed up the following points:

1. Cache is not cleaned up by tomcat.

2. Log4j.jar package not imported.

3. Configuration in web.xml < servlet-mapping> “, not “/”.

4. No servlet-api.jar imported.

5. The version of the package is inconsistent.

none of that.

solution is: tomcat under the lib all jar is wrong, why, you follow my train of thought: click these to go to see the source code.

look at the head, is there something that says catalina.jar, right at the top of the source code. Then click in these, keep looking for, find the lib under Tomcat, you will find that you just saw the source code on the head of the jar package, is the lib under Tomcat these jar packages.

yes, that’s all make of ghost, I’ll have (tomcat7) : https://download.csdn.net/download/qq_41879385/10701965, only need to future generations in the paste, again running tomcat, to regroup, of course, you can run a success, I am looking for a day of error, so settled.