Webcam initialization failed on Satellite L870-14V

Hello
when I want to use my webcam, I have a error message "webcam initialization failed.
Verify the operation of the camera, and then restart the application or restart the computer" namely that I'm restart the computer and it does not change the webcam is built into the computer.
+Message was edited: translated by Google translator+
null

Hi
i feel your pain. i have the same problem with my L875-10G. downloaded the drivers as suggestted by these guys as well but still have no luck. I don't even have people replying to my post
I have even gone for a full recovery thinking i have uninstalled it. But installing the web driver has no affect.
the camera is not even in the device manager.
if you managed to get it working i would really like to know how u did it

Similar Messages

  • Satellite L500D - Webcamera initialization failed

    Ok so I own this brand new Satellite L500D and as soon as I login in the web cam app pops up and says web camera initialization failed. Please check your camera device and restart application or computer.
    I press ok and the app closes down so I checked the device manager (took me a while my old laptop was xp this one is Windows 7) and there was no camera devices but an unkown device.
    No CDs came with my laptop for Windows or programs or drivers or anything and there no toshiba folder in the c directory. I even tried a like.. system restore but that didnt help. I really need some one to give me a hand here...
    Thanks.

    Hi Snider,
    I agree with the user above. You should try to reinstall the webcam driver firstly. This has also solved my problem with the webcam. :)
    Follow the link posted by matejko.
    Regarding your question about CDs: My Toshiba notebook does also came without disks because you have to create this disk yourself. Start the Toshiba recovery disk creator that creates a bootable medium for restoring factory settings. This disk contains an image of the Windows installation from Toshiba and is really easy to use! :)

  • Satellite L350-264: webcamera initialization failed

    I have just bought a new L350-264 (PSLD4E).
    The built in web cam worked fine for a few days but now when I turn the laptop on an error says "Web camera initialization failed.
    Please check your camera device and restart application or computer".
    No other information is provided.
    I have rebooted laptop and tried to open camera from the Toshiba Utilities menu but the same error is returned.
    Can anyone help?

    Hi
    What do you think about nee installation of webcam software?
    Have read about similar error messages here and mostly the user could solve this reinstalling the webcam software.
    The software can be downloaded from the Toshiba European driver page!!!

  • Web Camera initialization failed. Satellite L655

    i bought my laptop a month ago and got this message "web camera initialization failed. please check your camera device and restart application or computer"
    done reinstalling drivers
    done disabling and enabling webcam on BIOS
    my device manager doesnt detect any webcam, but it has a unknown device in the usb but theres nothing connected on my laptop when i checked on it it says "Windows has stopped this device because it has reported problems. (Code 43)"  

    Toshiba installed newer version of camera SW, one of possible reasons why it doesn't work properly, do full system recovery if after reinstalling device will still not work.

  • Re: Toshiba Satellite L650 - 12Z webcam initialization failed

    Hi, I need your help.
    My webcam wont work anymore. I uninstalled and installed the web camera application downloaded from the support website but didnt work. I did a fresh OS install but unfortunately it didnt work. I tried looking it up in the device manager but I didnt see any web camera.
    This is only like a month old, please help.. thx

    Hi buddy,
    Did you reinstall Windows using Toshiba recovery disk or a normal Microsoft disk?
    If you use Toshiba recovery disk for reinstalling, everything will be restored back to factory settings and should work properly because all drivers and tools will be installed automatically.
    If it doesnt work it seems to be a hardware malfunction and you should contact an authorized service provider in your country. The guys can order new spare parts and repair this under warranty.

  • Satellite L650 - Web Camera Initializations Failed

    Hello,
    I have a Satellite L650. I have had it for just under 6 months and the other day, I turned on the computer to find the web cam pop up message saying "Web Camera Initializations Failed etc..." I have also noticed that the in built microphone too isn't working anymore.
    I have uninstalled, and re installed the driver and it is still not working.
    I was wondering if there is anyone who can help or has had the same problem?
    Cheers,
    Dylan.

    Hi Dylan,
    Can you use the internal webcam with other applications like Skype?
    Have you installed the correct webcam driver for Satellite L650?
    What operating system you are using?
    If you have already reinstalled the webcam driver I would recommend using CCleaner tool. This is a very nice freeware tool that can check your registry for old registry keys and delete them. So its nice cleaning software to enhance the performance a little bit and fix problems. Just use Google to find this program.
    Check this!!!

  • Satellite L300 - T2FTP Windows sockets initialization failed

    After Login I get the following message:
    T2FTP Windows sockets initialization failed
    At the same time the system gives a message that it has found a new unknown hardware device and the driver should be installed.
    Before I did NOT add any new hardware device.
    Clicking the Start Button results only in a message: Windows Explorer does not react.
    It is impossible to call any other routine.
    Unfortunately I don't find my Recovery-CDROM.
    Is there any chance to save my system?
    Toshiba Satellite L300, Model PSLB8E
    Windows VISTA-32 bit

    Hi
    I think its operating system issue something, somewhere was going wrong
    I agree with Jeka. The Vista reinstallation would be the easiest and fastest way to get rid of this problem.
    If didnt get the recovery disk because the OS was preinstalled and there was an tool which allows you to create an own recovery disk.
    You should be able to recover the unit using HDD recovery
    Restart the notebook, press F8 and choose repair my computer.
    Then choose Toshiba HDD recovery.
    This would recover the OS again.

  • Satellite C650-1CR - webcam initialisation failed

    Hi all,
    I cannot get the integrated webcam to start.
    I have downloaded and installed the latest bios and webcam drivers from the toshiba website which promted the cam to start to initialise.
    Now i have an error which says "webcam initialisation failed, please check your device...."
    The problem is that there is no listing for the webcam on the device manager screen.
    I am at a loss as to how i can get the webcam to work, any suggestions?
    billy

    > The problem is that there is no listing for the webcam on the device manager screen.
    Usually the webcam should be listed in device manager under Imagine Devices
    In my case its USB Video Device this is the usb Chicony webcam.
    Do you have any unknown devices marked with yellow exclamation mark?
    If yes, then this is probably the cam
    As last option, you could try to recover the notebook using Toshiba Recovery disk which you have created... hopefully...

  • WEb camera initializtion failed in Satellite P750-114

    Dear All,
    I am facing a problem with the web camera in my Toshiba Satellite P750-114. The laptop is less than two months old and the web camera was working fine, then it suddenly stopped working. The error message is "Web camera initialization failed. Please check your camera device and restart application or computer". The Microphone stopped working as well, as it is related to the web camera device. The operating system is Windows 7 64bits. It seems that the operating system is not seeing that there is a webcam anymore. I tried the following things:
    1- I uninstalled the web camera driver, downloaded the most recent driver from Toshiba website (the link is http://uk.computers.toshiba-europe.com/innovation/jsp/supportMyProduct.do?service=UK) , and installed it, but it did not work.
    2- I restored the original setting for the laptop, but still the web camera is not working.
    Two ways I am using to test the web camera: the Skype and "Web Camera Application" from Start/Toshiba/Utilities
    Please if someone has any idea on how to resolve this problem, the laptop is band new and it is fantastic, but this problem is annoying. I searched the Internet for similar problems, some Toshiba models suffer from this problem but not P750-114,
    Please help
    Bashar

    Generally speaking, after recovery image installation all hardware components should be recognized and installed properly so with this factory settings everything should work as on the day after you purchased your notebook and started it for the first time.
    If the cam doesn't work with factory settings I can imagine there is some hardware problem.
    I recommend you to contact nearest Toshiba service provider and ask for help. They can check cam functionality using their diagnostic tools and exchange cam if necessary.
    Of course it will be covered by valid warranty.

  • NOT POSSIBLE TO START ESSBASE WHEN SSO INITIALIZATION FAILS

    Version is 11.1.1.3. My Essbase is not starting. Issues from the logs and what I have attempted are as follows. I have highlighted the relevant areas in bold.
    When Starting Essbase from products/Essbase/bin/start.bat:
    C:\Hyperion\products\Essbase\bin>start.bat
    C:\Hyperion\products\Essbase\bin>REM eis
    C:\Hyperion\products\Essbase\bin>net start "Hyperion Integration Services"
    The requested service has already been started.
    More help is available by typing NET HELPMSG 2182.
    C:\Hyperion\products\Essbase\bin>REM APS
    C:\Hyperion\products\Essbase\bin>call C:\Hyperion\products\Essbase\aps\bin\start.bat
    C:\Hyperion\products\Essbase\bin>REM aps
    C:\Hyperion\products\Essbase\bin>net start HyS9aps
    The requested service has already been started.
    More help is available by typing NET HELPMSG 2182.
    C:\Hyperion\products\Essbase\bin>REM EAS
    C:\Hyperion\products\Essbase\bin>call C:\Hyperion\products\Essbase\eas\bin\start.bat
    C:\Hyperion\products\Essbase\bin>REM eas
    C:\Hyperion\products\Essbase\bin>net start HyS9eas
    The requested service has already been started.
    More help is available by typing NET HELPMSG 2182.
    C:\Hyperion\products\Essbase\bin>REM EssbaseAgent
    C:\Hyperion\products\Essbase\bin>net start hypservice_1
    The service name is invalid.
    More help is available by typing NET HELPMSG 2185.
    C:\Hyperion\products\Essbase\bin>REM EssbaseStudio
    C:\Hyperion\products\Essbase\bin>C:\Hyperion\products\Essbase\EssbaseStudio\Server\startServer.bat
    C:\Hyperion\products\Essbase\bin>setlocal
    C:\Hyperion\products\Essbase\bin>set CONFIGTOOL_HOME="C:\Hyperion\common\config\9.5.0.0"
    C:\Hyperion\products\Essbase\bin>call ""C:\Hyperion\common\config\9.5.0.0"\setJavaRuntime.bat"
    Logging configuration file is not found. Expected filename is C:\Hyperion\products\Essbase\bin\.\server.properties
    Log file location is:
    C:\Hyperion\logs\esbstudio\server.log
    13:23:09 11/01/11 INFO Starting up
    13:23:09 11/01/11 INFO Oracle Essbase Studio Server. Version 11.1.1.3.00, Bui
    ld 090, June 25 2009
    13:23:16 11/01/11 (system) WARNING Failed to load driver for sap
    13:23:16 11/01/11 (system) SEVERE Cannot load Teradata connector
    13:23:16 11/01/11 (system) WARNING Failed to load driver for teradata
    13:23:16 11/01/11 (system) WARNING Failed to load driver for mysql
    13:23:16 11/01/11 (system) WARNING Failed to load driver for netezza
    Essbase.log:
    [Tue Oct 25 11:26:31 2011]Local/ESSBASE0///Error(1051223)
    Single Sign On function call [css_init] failed with error [CSS Error: CSS method invocation error: com.hyperion.css.CSSSystem.<init>]
    [Tue Oct 25 11:26:31 2011]Local/ESSBASE0///Info(1051198)
    Single Sign-On Initialization Failed !
    [Tue Oct 25 11:26:31 2011]Local/ESSBASE0///Info(1051232)
    Using English_UnitedStates.Latin1@Binary as the Essbase Locale
    [Tue Oct 25 11:26:31 2011]Local/ESSBASE0///Error(1051527)
    In Shared Services Security mode it is not possible to start Essbase when single sign on initialization fails.
    AND
    C:\Hyperion\logs\essbase\SharedServices_Security_Client.log com.hyperion.css.CSSSystem.<init>(Unknown Source)
    2011-10-25 11:26:11,039 INFO [main] Configure CSS with registry com.hyperion.css.CSSSystem.initCSSSystem(Unknown Source)
    2011-10-25 11:26:11,039 INFO [main] Initializing CSS from Registry. com.hyperion.css.common.configuration.CSSConfigurationManager.getConfiguration(Unknown Source)
    2011-10-25 11:26:11,085 INFO [main] Trying to get Registry Instance com.hyperion.css.registry.RegistryManager.<init>(Unknown Source)
    2011-10-25 11:26:31,023 ERROR [main] 20:1092:Failed to initialize EPM System registry. *[Root Cause: java.sql.SQLException: [Hyperion][SQLServer JDBC Driver]Error establishing socket to host and port: machinex:1433. Reason: Connection refused: connect ] com.hyperion.css.registry.RegistryManager.<init>(Unknown Source)*
    *2011-10-25 11:26:31,023 ERROR [main] Arguments: param1={}, param2=null, param3=C:\Hyperion\logs\essbase\,* com.hyperion.css.CSSSystem.initCSSSystem(Unknown Source)
    2011-10-25 11:26:31,023 INFO [main] CSS system intialization failed. : [21484 ms] com.hyperion.css.CSSSystem.initCSSSystem(Unknown Source)
    What I have attempted:
    - Attempted to connect to Shared Services, Workspace url's - YES
    - Checked openLDAP & my Database is running - YES
    - Added following to Configuration File :
    SharedServicesLocation machinex 28080
    AUTHENTICATIONMODULE CSS http://machinex:28080/interop/framework/getCSSConfigFile YES, but same error
    - Changed essbase.bak to essbase.sec YES but same error
    - netstat -an to check for 1423. Port 1423 is not listening, although ALL TCP Ports have been enabled. So YES but same error.
    - Read Knowledgebase article # 954322.1 - the suggested things in there don't seem to apply to my case, unless I am missing something.
    At this point does anybody have any suggestions ?

    An update: Just for kicks, I tried restarting Essbase using Start->Programs-EPMSystem->Essbase->EssbaseServer->Essbase.bat and apparently now Essbase is started.
    EAS, Studio and Planning however are down.
    Excerpt from the HyS9eas-sysout.log:
    [ERROR] RegistryUtils - SQL Exception when trying to create a new connection [Hyperion][SQLServer JDBC Driver]Error establishing socket to host and port: machinex:1433. Reason: Connection refused: connect
    * CRITICAL ERROR: Common Security Services initialization failed. Please *
    * make sure that a valid entry is provided for SECURITY_CONFIGURATION in *
    * OlapAdmin.properties. This is required if Shared Services is enabled. *
    * Please restart the server after the changes. *
    Stopping DAO factory!
    HBR Configuration has not been initialized. Make sure you have logged in sucessfully and there are no exceptions in the HBR log file.
    java.lang.ExceptionInInitializerError
    .... bunch of java code.
    This is really strange. There is NOTHING that I changed, started or stopped which could have caused Essbase to start magically all of a sudden.
    Any insights into the cause of all this ?

  • Error -32810 occurred at The FieldPoint server initialization failed. Possible causes: 1. Missing or corrupt configuration file; 2. Failed to create callbacks. : FP Open.vi

    I have two cFP-2120 RT controller. They both have NI-Serial RT2.5.6, DataSocket for LV RT4.2, NI-VISA 3.6, FP Drivers 5.1.0, FP VI Manager 3.1.0 LV RT 7.1.1 installed. But one same vi can run on one controller but not another.
    the error message got when it runs on another controller is "Error -32810 occurred at  The FieldPoint server initialization failed. Possible causes: 1. Missing or corrupt configuration file; 2. Failed to create callbacks. : FP Open.vi"
    I wonder by what it is caused?
    Thanks

    Hi Matthew,
    As mentioned previously, this KnowledgeBase article may be of some help. Also, if your code is being run on an embedded controller and then a network controller (not embedded), you will need to run the program differently. On the embedded controller, you should deploy your VI in a Project Explorer or programmatically (as described here.) However, you do not need to deploy the program to a network controller, but simply run the VI.
    I would also suggest creating a new .IAK file. Do you still see the same error? Also, double-check that the software installed on the controller matches the software installed on the host PC. If you have any file paths associated with one FieldPoint controller, ensure that you are changing them to match the second controller.
    Please keep us posted on your troubleshooting steps. Have a great day!
    Amanda Howard
    Americas Services and Support Recruiting Manager
    National Instruments

  • Window server 2008 r2 error show "stop :- c00002e3 security account manager initialization failed because of the for A DIVICE ATTACHED to the system is not funcation"

    Hi All
    Please help
    my server not working showing display error window server 2008 r2  error show "stop :- c00002e3 security account manager initialization failed because of the for A DIVICE ATTACHED to the system is not funcation"
    Please help me how to resolve this issue ???
    thnaks !!!

    Hi,
    If there is any external device plug into your computer, please unplug it and restart the Server.
    You can also test the issue in Safe mode.
    If it can boot into Safe mode, please update any driver has yellow warning on it, also check if the dump file is existing under %SystemRoot%\, if so, please help to post back for our research.
    Kate Li
    TechNet Community Support

  • File Adapter: Initialization error: Conversion initialization failed

    Hi all,
    I'm trying to establish a file adapter (FTP, File Content Conversion).
    In the adapter monitor I' ve got the following error:
    Sender Adapter v1325 for Party '', Service 'BS_ACN_PCS_A':
    Configured at 14:49:34 2005-08-29
    Initialization error: Conversion initialization failed with java.lang.Exception: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found:
    Format error in 'xml.recordset' argument: incomplete structure (name,number) pair
    My content conversion parameters are:
    BP_BusinessPartnerMasterData_IncomingData.fieldFixedLengths:
    20,50,50,1,10,50,10,50,5,20,20,15,15
    BP_BusinessPartnerMasterData_IncomingData.fieldNames: Number,Name2,Name1,Gender,Birthdate,City,Postcode,Street,
    HouseNo,PhoneNumber,Fax,BankId,BankAccount
    BP_BusinessPartnerMasterData_IncomingData.fieldContentFormating:
    trim
    BP_BusinessPartnerMasterData_IncomingData.keyFieldInStructure:
    ignore
    What could be the error or where I have to look for it?
    Thanks,
    Fabian

    Yes,
    Recordset name: BP_BusinessPartnerMasterData_IncomingData
    Recordset structure: BP_BusinessPartnerMasterData_IncomingData
    The corresponding Message Type:
    <?xml version="1.0" encoding="ISO-8859-1"?>
    <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://pcs.acn.com/basicdata" targetNamespace="http://pcs.acn.com/basicdata">
         <xsd:element name="BP_MasterDataIncomingFil" type="BP_BusinessPartnerMasterData_IncomingData" />
         <xsd:complexType name="BP_BusinessPartnerMasterData_IncomingData">
              <xsd:annotation>
                   <xsd:appinfo source="http://sap.com/xi/TextID">
                   f323a4b018a911da9fd9000bcd69ce64
                   </xsd:appinfo>
              </xsd:annotation>
              <xsd:sequence>
                   <xsd:element name="Number">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             7679e8500fe111da89f2d1210a87220d
                             </xsd:appinfo>
                             <xsd:documentation xml:lang="EN">
                             Id from Sender for BP
                             </xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="20" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="Name2">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             7679e8510fe111dacfd7d1210a87220d
                             </xsd:appinfo>
                             <xsd:documentation xml:lang="EN">
                             Last name or Company name
                             </xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="50" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="Name1">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             7679e8520fe111da94bad1210a87220d
                             </xsd:appinfo>
                             <xsd:documentation xml:lang="EN">
                             First name or Company name 2
                             </xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="50" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="Gender">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             7679e8530fe111da99add1210a87220d
                             </xsd:appinfo>
                             <xsd:documentation xml:lang="EN">
                             m or f or blank
                             </xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="1" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="Birthdate">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             7679e8540fe111dab156d1210a87220d
                             </xsd:appinfo>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="10" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="City">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             7679e8550fe111daa58cd1210a87220d
                             </xsd:appinfo>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="50" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="Postcode">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             7679e8560fe111dac0c2d1210a87220d
                             </xsd:appinfo>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="10" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="Street">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             7679e8570fe111dabbd3d1210a87220d
                             </xsd:appinfo>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="50" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="HouseNo">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             7679e8580fe111dab63fd1210a87220d
                             </xsd:appinfo>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="5" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="PhoneNumber">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             7679e8590fe111dac782d1210a87220d
                             </xsd:appinfo>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="20" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="Fax">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             7679e85a0fe111daa9ebd1210a87220d
                             </xsd:appinfo>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="20" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="BankId">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             7679e85b0fe111dace1ed1210a87220d
                             </xsd:appinfo>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="15" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="BankAccount">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             7679e85c0fe111da8801d1210a87220d
                             </xsd:appinfo>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="15" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
              </xsd:sequence>
         </xsd:complexType>
    </xsd:schema>

  • Java APM Agent initialization failed: SEAgent.config.xml does not have a valid event sender configured

    Today I tried to configure JAVA APM on a CentOS 6.4 server with tomcat6 installed through the normal RPM package. Adding this server to SCOM was no problem and it shows itself as a 'Deep Monitored Configuration'. The last part of enabling
    JAVA APM fails. I have followed the following process:
    1. Imported the JAVA APM MP's
    2. Extracted the JAVA APM Files
    3. Copied those files to my CentOS server
    4. Added the JAVA_OPTS to my tomcat configuration file
    5. Restarted Tomcat
    When I look for the log file which needs to be created through the installation of the APM agent it cannot be find. When I look into my Catalina.out file I see the following errors:
    Mar 05, 2014 7:05:16 PM com.microsoft.ManagementServices.APMAgent.Log.SystemLogger error
    SEVERE: Java APM Agent initialization failed: SEAgent.config.xml does not have a valid event sender configured
    com.microsoft.ManagementServices.APMAgent.Exception.ApmException: SEAgent.config.xml does not have a valid event sender configured
            at com.microsoft.ManagementServices.APMAgent.AgentThreadManager.<init>(Unknown Source)
            at com.microsoft.ManagementServices.APMAgent.AgentThreadManager.<init>(Unknown Source)
            at com.microsoft.ManagementServices.APMAgent.Agent.Monitor.AgentContext.<init>(Unknown Source)
            at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
            at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
            at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
            at java.lang.reflect.Constructor.newInstance(Constructor.java:525)
            at com.microsoft.ManagementServices.APMAgent.Agent.Startup.AgentContextLoader.loadContext(Unknown Source)
            at com.microsoft.ManagementServices.APMAgent.Agent.Startup.Agent.premain(Unknown Source)
            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
            at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
            at java.lang.reflect.Method.invoke(Method.java:601)
            at sun.instrument.InstrumentationImpl.loadClassAndStartAgent(InstrumentationImpl.java:382)
            at sun.instrument.InstrumentationImpl.loadClassAndCallPremain(InstrumentationImpl.java:397)
    Caused by: java.lang.reflect.InvocationTargetException
            at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
            at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
            at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
            at java.lang.reflect.Constructor.newInstance(Constructor.java:525)
            ... 15 more
    Caused by: com.microsoft.ManagementServices.APMAgent.Exception.ApmException: Error registering MBean: com.microsoft.ManagementServices.APMAgent:type=COUNTER
            at com.microsoft.ManagementServices.APMAgent.EventSender.MBeanEventLog.registerMetricMBeans(Unknown Source)
            at com.microsoft.ManagementServices.APMAgent.EventSender.MBeanEventLog.<init>(Unknown Source)
            at com.microsoft.ManagementServices.APMAgent.EventSender.MBeanEventLog.<init>(Unknown Source)
            at com.microsoft.ManagementServices.APMAgent.AgentThreadManager.<init>(Unknown Source)
            at com.microsoft.ManagementServices.APMAgent.AgentThreadManager.<init>(Unknown Source)
            at com.microsoft.ManagementServices.APMAgent.Agent.Monitor.AgentContext.<init>(Unknown Source)
            at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
            at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
            at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
            at java.lang.reflect.Constructor.newInstance(Constructor.java:525)
            at com.microsoft.ManagementServices.APMAgent.Agent.Startup.AgentContextLoader.loadContext(Unknown Source)
            at com.microsoft.ManagementServices.APMAgent.Agent.Startup.Agent.premain(Unknown Source)
            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
            at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
            at java.lang.reflect.Method.invoke(Method.java:601)
            at sun.instrument.InstrumentationImpl.loadClassAndStartAgent(InstrumentationImpl.java:382)
            at sun.instrument.InstrumentationImpl.loadClassAndCallPremain(InstrumentationImpl.java:397)
    Caused by: java.lang.reflect.InvocationTargetException
            at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
            at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
            at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
            at java.lang.reflect.Constructor.newInstance(Constructor.java:525)
            ... 15 more
    Caused by: com.microsoft.ManagementServices.APMAgent.Exception.ApmException: Error registering MBean: com.microsoft.ManagementServices.APMAgent:type=COUNTER
            at com.microsoft.ManagementServices.APMAgent.EventSender.MBeanEventLog.registerMetricMBeans(Unknown Source)
            at com.microsoft.ManagementServices.APMAgent.EventSender.MBeanEventLog.<init>(Unknown Source)
            at com.microsoft.ManagementServices.APMAgent.EventSender.MBeanEventLog.<init>(Unknown Source)
            ... 19 more
    Mar 05, 2014 7:05:16 PM com.microsoft.ManagementServices.APMAgent.Log.SystemLogger info
    INFO: Java APM Agent loading failed (Build: 1.10.100.15, Label: NotFromLabel, BuildDate: 20131112)
    java.lang.reflect.InvocationTargetException
            at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
            at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
            at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
            at java.lang.reflect.Constructor.newInstance(Constructor.java:525)
            at com.microsoft.ManagementServices.APMAgent.Agent.Startup.AgentContextLoader.loadContext(Unknown Source)
            at com.microsoft.ManagementServices.APMAgent.Agent.Startup.Agent.premain(Unknown Source)
            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
            at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
            at java.lang.reflect.Method.invoke(Method.java:601)
            at sun.instrument.InstrumentationImpl.loadClassAndStartAgent(InstrumentationImpl.java:382)
            at sun.instrument.InstrumentationImpl.loadClassAndCallPremain(InstrumentationImpl.java:397)
    Caused by: java.lang.InstantiationException: Monitor initialization failed: SEAgent.config.xml does not have a valid event sender configured
            at com.microsoft.ManagementServices.APMAgent.Agent.Monitor.AgentContext.<init>(Unknown Source)
            ... 12 more
    Does anyone have seen this error before? Can someone help me with this one?
    Thnx,

    I'm running tomcat on a CentOS release 6.4 (Final) server. I installed Tomcat 6 through an RPM from the CentOS sources. I have installed Apache Tomcat/6.0.24 wit JVM version 1.7.0_09-icedtea-mockbuild_2013_01_16_18_52-b00, the JVM Vendor is Oracle Corporation.
    My tomcat configuration needs to be done in '/etc/tomcat6/tomcat6.conf'
    I installed the APM Agent in the path '/opt/apm/' with the rights  40755 (root/root). The files have the following rights:
    -rw-rw-r-- 1 root tomcat  32046 Mar  3 15:38 apm_facade.jar
    -rw-rw-r-- 1 root tomcat 244819 Mar  3 15:38 apm_monitor.jar
    -rw-rw-r-- 1 root tomcat  38110 Mar  3 15:38 apm_producers.jar
    -rw-rw-r-- 1 root tomcat 207006 Mar  3 15:38 asm-all-3.3.1.jar
    -rw-rw-r-- 1 root tomcat   4157 Mar  3 15:38 ASM_Third_Party_Notices.txt
    -rw-rw-r-- 1 root tomcat 241368 Mar  3 15:38 DispatcherStub.dll
    -rw-rw-r-- 1 root tomcat  36880 Mar  3 15:38 pmonitor.config.xml
    -rw-rw-r-- 1 root tomcat   2625 Mar  3 15:38 SEAgent.config.xml
    -rw-rw-r-- 1 root tomcat    830 Mar  5 15:19 Starter.properties
    The above rights are equal to the /etc/tomcat6 directory with the tomcat configuration files.
    In the tomcat6.conf I have added the following entries:
    #Microsoft SCOM APM
    JAVA_OPTS="${JAVA_OPTS} -Djava.library.path=/opt/apm"
    JAVA_OPTS="${JAVA_OPTS} -javaagent:/opt/apm/apm_facade.jar -Xbootclasspath/p:/opt/apm/apm_producers.jar -Xbootclasspath/p:/opt/apm/apm_facade.jar"
    When I look into the running tomcat process I see the following:
    tomcat   17401     1  0 Mar05 ?        00:00:39 /usr/lib/jvm/jre/bin/java -Djava.library.path=/opt/apm -javaagent:/opt/apm/apm_facade.jar -Xbootclasspath/p:/opt/apm/apm_producers.jar -Xbootclasspath/p:/opt/apm/apm_facade.jar
    -Djavax.sql.DataSource.Factory=org.apache.commons.dbcp.BasicDataSourceFactory -Djava.library.path=/opt/apm -javaagent:/opt/apm/apm_facade.jar -Xbootclasspath/p:/opt/apm/apm_producers.jar -Xbootclasspath/p:/opt/apm/apm_facade.jar -Djavax.sql.DataSource.Factory=org.apache.commons.dbcp.BasicDataSourceFactory
    -classpath :/usr/share/tomcat6/bin/bootstrap.jar:/usr/share/tomcat6/bin/tomcat-juli.jar:/usr/share/java/commons-daemon.jar -Dcatalina.base=/usr/share/tomcat6 -Dcatalina.home=/usr/share/tomcat6 -Djava.endorsed.dirs= -Djava.io.tmpdir=/var/cache/tomcat6/temp
    -Djava.util.logging.config.file=/usr/share/tomcat6/conf/logging.properties -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager org.apache.catalina.startup.Bootstrap start
    My Starter.Properties looks like this:
    # Jars to load by inner classloader.
    # Use semicolons to separate the JAR entries
    ClassPath=apm_monitor.jar;asm-all-3.3.1.jar;apm_producers.jar
    # Path to pmonitor.config
    MonitorConfigFileName=pmonitor.config.xml
    # Path to SEAgent.config
    AgentConfigFileName=SEAgent.config.xml
    # Log file name
    # Example for full-path location:
    #                  LogFileName=c:\\tracelog\\apm-java-agent.log
    # Example for relative path (to agent jar files):
    #                  LogFileName=apm-java-agent.log
    LogFileName=apm-java-agent.log
    # Log level (SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST)
    # A level of FINER or FINEST may expose Personally identifiable
    # information (PII) in the log file.  The levels below INFO are
    # intended for debugging and diagnostic use only.
    LogLevel=FINEST
    The 'apm-java-agent.log' is not created on the system. The only logging is done in the catalina.out. When restarting tomcat I see the following entries in te log file:
    INFO: Initializing Java APM Agent (Build: 1.10.100.15, Label: NotFromLabel, BuildDate: 20131112)
    Mar 06, 2014 9:35:21 AM com.microsoft.ManagementServices.APMAgent.Log.SystemLogger info
    INFO: Java APM Agent loading succeeded (Build: 1.10.100.15, Label: NotFromLabel, BuildDate: 20131112)
    Mar 06, 2014 9:35:21 AM com.microsoft.ManagementServices.APMAgent.Log.SystemLogger info
    INFO: Initializing Java APM Agent (Build: 1.10.100.15, Label: NotFromLabel, BuildDate: 20131112)
    Mar 06, 2014 9:35:21 AM com.microsoft.ManagementServices.APMAgent.Log.SystemLogger warning
    WARNING: Failed registering the COUNTER MBean
    Mar 06, 2014 9:35:21 AM com.microsoft.ManagementServices.APMAgent.Log.SystemLogger error
    SEVERE: Java APM Agent initialization failed: SEAgent.config.xml does not have a valid event sender configured
    Mar 06, 2014 9:35:21 AM com.microsoft.ManagementServices.APMAgent.Log.SystemLogger info
    INFO: Java APM Agent loading failed (Build: 1.10.100.15, Label: NotFromLabel, BuildDate: 20131112)
    Hope this gives your some more background around my problem, I double checked the permissions..

  • J2EE Engine start error: Database initialization failed!

    My J2EE engine now fails to start - jcontrol stays yellow.  I've followed Troubleshooting pages from help.sap.com Admin manual topic "starting J2EE Engine".
    Background:
    I was running through JDI Scenario 2+ on a fresh installed WebAS 6.40 at SP9.  Using NWDevStudio2.09, I attempted to load a DC, but servers stopped responding.  So I downed everything (in MMC) including offlining the DB, then put DB back online and restart the J2E engine, and now jcontrol stays yellow. 
    I find this in the file log_bootstrap_ID0014430.0.log:
    Apr 7, 2005 3:10:23 PM  ] Bootstrap MODE:
    [Apr 7, 2005 3:10:23 PM  ] <INSTANCE GLOBALS>
    [Apr 7, 2005 3:10:23 PM  ]  determined by parameter [ID0014430].
    [Apr 7, 2005 3:10:23 PM  ] -
    [Apr 7, 2005 3:10:26 PM  ] Exception occured:
    com.sap.engine.bootstrap.SynchronizationException: Database initialization failed! Check database properties!
         at com.sap.engine.bootstrap.Bootstrap.initDatabaseConnection(Bootstrap.java:422)
         at com.sap.engine.bootstrap.Bootstrap.<init>(Bootstrap.java:144)
         at com.sap.engine.bootstrap.Bootstrap.main(Bootstrap.java:813)
    .........a few lines cut out here..........
         at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
    ==[ Caused by: ]==----
    com.sap.engine.frame.core.configuration.ConfigurationException: Error while connecting to DB.
         at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.createConnection(DBConnectionPool.java:344)
    ............ a few lines cut out here..........
         at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
    Caused by: com.sap.dbtech.jdbc.exceptions.JDBCDriverException: SAP DBTech JDBC: Cannot connect to jdbc:sapdb://PHI21811/J2E [Cannot connect to host PHI21811 [Connection refused: connect], -813.].
         at com.sap.dbtech.jdbc.DriverSapDB.connect(DriverSapDB.java:183)
         at com.sap.sql.jdbc.NativeConnectionFactory.createNativeConnection(NativeConnectionFactory.java:219)
         at com.sap.sql.connect.OpenSQLDataSourceImpl.createPooledConnection(OpenSQLDataSourceImpl.java:570)
         at com.sap.sql.connect.OpenSQLDataSourceImpl.getPooledConnection(OpenSQLDataSourceImpl.java:263)
         at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.createConnection(DBConnectionPool.java:294)
         ... 14 more
    [Apr 7, 2005 3:10:26 PM  ] [Bootstrap module]> Problem occured while performing synchronization.
    [Apr 7, 2005 3:22:24 PM  ] -
    ANYONE HAVE ANY SUGGESTIONS?????

    Using the Database Administration section of the help.sap.com library, I found the location of SAPDB/MySQL log files.  They are in C:\sapdb\data\wrk\J2E.  In 'knldiag' I found entries complaining of Log files being full and tasks put in suspension.
    So I figured out to do a full back up of the DB and/or backup the log files.  The log file bar (in MMC) still showed 100% full, but I figured out to refresh the view and voila it was empty (so one of the backups emptied it, not sure which one).
    After that the DB comes up fine and now my J2E WebAS goes all green.
    Message was edited by: Michael W Rains

Maybe you are looking for

  • Problem configurin​g WSN network in MAX

    HI, I am facing this problem suddenly in using my NI 9792 gateway .The module is getting detected in MAX  It is that I am not able to find the Node option under devices and interfaces of the gateway in MAX. I am using LV2010 and NI WSN 1.2. Correspo

  • Networking G3 to Mac Mini

    Hi Guys, I have an old G3 Beige and a Mac Mini G4(non-intel), and ,basically, I would like to know if it is possible to link the two via ethernet cable so that the G3 could be used as an extra storage device for the Mini. The mini is slowly running o

  • BlueTooth connects via HotSynch, not other means PALM TX

    I am at my wit's end here. Really. I'm about to toss my Palm, and I'm hoping someone can help me out. Here's my setup: 1. PALM T|X - less than a month old. 2. Dell Inspiron 6000 laptop, running Windows XP Home SP2, 2gb of memory, Centrino technology.

  • Critical Weblogic server error

    Hello, I use Weblogic server to run my application. I get the below error very rarely. After restarting the server, the application works fine, but I would like to find the reason. I have pasted the errors displayed in browser and log files. Can any

  • Adding New Fields to Customer Complaint Transaction

    after creating the fields in the wizard of transaction EEWB , its showing the following error "System Type OLTP with Role DEV is not specified correctly" please guide me