ServiceLayer - Could not start service

Hello,
I've just bought Nokia N95 8GB and wanted to install Nokia PC Suite. When installing PC Connectivity Solution there was a window message with title ServiceLayer and text "Could not start service". Afterwards, installation continued and finished "succesfully". Unfortunately I have problem that was posted a few times. I can't connect phone to PC Suite. I tried to Repair PC Connectivity solution, uninstall this and Cable driver and repair Nokia PC Suite, uninstall everything and use later Nokia cleaner etc. Nothing worked. When I go to PC Connectivity Solution and run manually ServiceLayer.exe I get the same message, that "Could not start service". What should I do? Please help me. I do not want to format my HDD and install Windows from the beginning. I use WinXP SP2.

Hi,
I've found the cause of the problem. It was firewall - Agnitum Outpost Personal Firewall Pro. I had old version and after installing new version the message dissapeared. As You can see below - one of issues solved was the problem "Outpost Firewall could block installation of services".
"Outpost Firewall Pro 2008 (build 6.0.2172.214.422.270)
Release date: November 14, 2007
The following issues are resolved (only significant ones are listed):
* Outpost monitor and Outpost Feedback were not registered in startup entries
* Outpost Firewall could block installation of services
* Information about crashes could not be sent to Agnitum
* Rules autocreation did not work on 64-bit systems for applications from ProgramFiles (x86) and SysWOW64 folders
* Most commonly reported crashes (including crash on content filtering)
* Error 14001 during installation
* Rules were applied incorrectly in some cases
* Address macros could be incorrectly resolved in rules
* Leaktests SPT 15 and SPT 16 were failed on Vista64
* Error while importing LAN settings from Outpost Firewall 4.0
* Web pages content could be blocked/corrupted (GZIP decoding issue)
* Outpost Firewall now cannot be installed over Outpost Security Suite"
But now I have different problem - I can't download update of PC Suite. The download starts and it stops when the progress bar is in its way. Sometimes it goes to the end but the installation doesn't start. What could be the problem?

Similar Messages

  • Error: Could not start Service[keystone]: Execution of '/sbin/service openstack-keystone start' returned 1: Starting keystone: [FAILED]

    I'm using Oracle Linux 6u6. While I'm installing openstack ( 2 node set up) using packstack, I'm getting this error:
    Applying 10.245.33.37_cinder.pp
    10.245.33.37_keystone.pp:                         [ ERROR ]
    Applying Puppet manifests                         [ ERROR ]
    ERROR : Error appeared during Puppet run: 10.245.33.37_keystone.pp
    Error: Could not start Service[keystone]: Execution of '/sbin/service openstack-keystone start' returned 1: Starting keystone: [FAILED]
    You will find full trace in log /var/tmp/packstack/20150327-100335-ltC8Ic/manifests/10.245.33.37_keystone.pp.log
    Please check log file /var/tmp/packstack/20150327-100335-ltC8Ic/openstack-setup.log for more information
    Additional information:
    * A new answerfile was created in: /root/packstack-answers-20150327-100336.txt
    * Time synchronization installation was skipped. Please note that unsynchronized time on server instances might be problem for some OpenStack components.
    * Did not create a cinder volume group, one already existed
    * File /root/keystonerc_admin has been created on OpenStack client host 10.245.33.37. To use the command line tools you need to source the file.
    * To access the OpenStack Dashboard browse to http://10.245.33.37/dashboard .
    Please, find your login credentials stored in the keystonerc_admin in your home directory.
    Packages:
    [root@slcai461 ~]# rpm -qa|grep keystone
    python-keystoneclient-0.9.0-5.el6.noarch
    python-keystone-2014.1.3-2.el6.noarch
    openstack-keystone-2014.1.3-2.el6.noarch
    [root@slcai461 ~]# rpm -qa|grep packstack
    openstack-packstack-puppet-2014.1.1-0.12.dev1068.0.4.el6.noarch
    openstack-packstack-2014.1.1-0.12.dev1068.0.4.el6.noarch
    Log :
    [root@slcai461 ~]# cat /var/tmp/packstack/20150327-100335-ltC8Ic/manifests/10.245.33.37_keystone.pp.log
    Warning: Config file /etc/puppet/hiera.yaml not found, using Hiera defaults
    Warning: Scope(Class[Keystone]): The sql_connection parameter is deprecated, use database_connection instead.
    Warning: Scope(Class[Keystone]): token_format parameter is deprecated. Use token_provider instead.
    Warning: Scope(Class[Keystone::Endpoint]): The public_address parameter is deprecated, use public_url instead.
    Warning: Scope(Class[Keystone::Endpoint]): The internal_address parameter is deprecated, use internal_url instead.
    Warning: Scope(Class[Keystone::Endpoint]): The admin_address parameter is deprecated, use admin_url instead.
    Warning: Scope(Class[Nova::Keystone::Auth]): The cinder parameter is deprecated and has no effect.
    Notice: Compiled catalog for slcai461.us.oracle.com in environment production in 1.60 seconds
    Warning: The package type's allow_virtual parameter will be changing its default value from false to true in a future release. If you do not want to allow virtual packages, please explicitly set allow_virtual to false.
       (at /usr/lib/ruby/site_ruby/1.8/puppet/type.rb:816:in `set_default')
    Notice: /Stage[main]/Keystone/Keystone_config[DEFAULT/admin_token]/value: value changed '[old secret redacted]' to '[new secret redacted]'
    Notice: /Stage[main]/Keystone/Keystone_config[database/connection]/value: value changed '[old secret redacted]' to '[new secret redacted]'
    Notice: /Stage[main]/Keystone::Db::Sync/Exec[keystone-manage db_sync]: Triggered 'refresh' from 3 events
    Notice: /Stage[main]/Keystone/Exec[keystone-manage pki_setup]: Triggered 'refresh' from 2 events
    Error: Could not start Service[keystone]: Execution of '/sbin/service openstack-keystone start' returned 1: Starting keystone: [FAILED]
    Wrapped exception:
    Execution of '/sbin/service openstack-keystone start' returned 1: Starting keystone: [FAILED]
    Error: /Stage[main]/Keystone::Service/Service[keystone]/ensure: change from stopped to running failed: Could not start Service[keystone]: Execution of '/sbin/service openstack-keystone start' returned 1: Starting keystone: [FAILED]
    Notice: /Stage[main]/Keystone::Service/Service[keystone]: Triggered 'refresh' from 5 events
    Notice: /Stage[main]/Neutron::Keystone::Auth/Keystone_service[neutron]: Dependency Service[keystone] has failures: true
    Warning: /Stage[main]/Neutron::Keystone::Auth/Keystone_service[neutron]: Skipping because of failed dependencies
    Notice: /Stage[main]/Keystone::Roles::Admin/Keystone_tenant[admin]: Dependency Service[keystone] has failures: true
    Warning: /Stage[main]/Keystone::Roles::Admin/Keystone_tenant[admin]: Skipping because of failed dependencies
    Notice: /Stage[main]/Nova::Keystone::Auth/Keystone_service[nova_ec2]: Dependency Service[keystone] has failures: true
    Warning: /Stage[main]/Nova::Keystone::Auth/Keystone_service[nova_ec2]: Skipping because of failed dependencies
    Notice: /Stage[main]/Cinder::Keystone::Auth/Keystone_service[cinderv2]: Dependency Service[keystone] has failures: true
    Warning: /Stage[main]/Cinder::Keystone::Auth/Keystone_service[cinderv2]: Skipping because of failed dependencies
    Notice: /Stage[main]/Nova::Keystone::Auth/Keystone_service[novav3]: Dependency Service[keystone] has failures: true
    Warning: /Stage[main]/Nova::Keystone::Auth/Keystone_service[novav3]: Skipping because of failed dependencies
    Notice: /Stage[main]/Keystone::Roles::Admin/Keystone_tenant[services]: Dependency Service[keystone] has failures: true
    Warning: /Stage[main]/Keystone::Roles::Admin/Keystone_tenant[services]: Skipping because of failed dependencies
    Notice: /Stage[main]/Neutron::Keystone::Auth/Keystone_user[neutron]: Dependency Service[keystone] has failures: true
    Warning: /Stage[main]/Neutron::Keystone::Auth/Keystone_user[neutron]: Skipping because of failed dependencies
    Notice: /Stage[main]/Nova::Keystone::Auth/Keystone_user[nova]: Dependency Service[keystone] has failures: true
    Warning: /Stage[main]/Nova::Keystone::Auth/Keystone_user[nova]: Skipping because of failed dependencies
    Notice: /Stage[main]/Glance::Keystone::Auth/Keystone_user[glance]: Dependency Service[keystone] has failures: true
    Warning: /Stage[main]/Glance::Keystone::Auth/Keystone_user[glance]: Skipping because of failed dependencies
    Notice: /Stage[main]/Keystone::Roles::Admin/Keystone_role[admin]: Dependency Service[keystone] has failures: true
    Warning: /Stage[main]/Keystone::Roles::Admin/Keystone_role[admin]: Skipping because of failed dependencies
    Notice: /Stage[main]/Glance::Keystone::Auth/Keystone_user_role[glance@services]: Dependency Service[keystone] has failures: true
    Warning: /Stage[main]/Glance::Keystone::Auth/Keystone_user_role[glance@services]: Skipping because of failed dependencies
    Notice: /Stage[main]/Keystone::Endpoint/Keystone_service[keystone]: Dependency Service[keystone] has failures: true
    Warning: /Stage[main]/Keystone::Endpoint/Keystone_service[keystone]: Skipping because of failed dependencies
    Error: Could not prefetch keystone_endpoint provider 'keystone': Execution of '/usr/bin/keystone --os-endpoint http://127.0.0.1:35357/v2.0/ endpoint-list' returned 1: An unexpected error prevented the server from fulfilling your request. (HTTP 500)
    Notice: /Stage[main]/Keystone::Endpoint/Keystone_endpoint[RegionOne/keystone]: Dependency Service[keystone] has failures: true
    Warning: /Stage[main]/Keystone::Endpoint/Keystone_endpoint[RegionOne/keystone]: Skipping because of failed dependencies
    Notice: /Stage[main]/Main/Keystone_service[cinder_v2]: Dependency Service[keystone] has failures: true
    Warning: /Stage[main]/Main/Keystone_service[cinder_v2]: Skipping because of failed dependencies
    Notice: /Stage[main]/Main/Keystone_endpoint[RegionOne/cinder_v2]: Dependency Service[keystone] has failures: true
    Warning: /Stage[main]/Main/Keystone_endpoint[RegionOne/cinder_v2]: Skipping because of failed dependencies
    Notice: /Stage[main]/Nova::Keystone::Auth/Keystone_endpoint[RegionOne/novav3]: Dependency Service[keystone] has failures: true
    Warning: /Stage[main]/Nova::Keystone::Auth/Keystone_endpoint[RegionOne/novav3]: Skipping because of failed dependencies
    Notice: /Stage[main]/Cinder::Keystone::Auth/Keystone_service[cinder]: Dependency Service[keystone] has failures: true
    Warning: /Stage[main]/Cinder::Keystone::Auth/Keystone_service[cinder]: Skipping because of failed dependencies
    Notice: /Stage[main]/Cinder::Keystone::Auth/Keystone_endpoint[RegionOne/cinder]: Dependency Service[keystone] has failures: true
    Warning: /Stage[main]/Cinder::Keystone::Auth/Keystone_endpoint[RegionOne/cinder]: Skipping because of failed dependencies
    Notice: /Stage[main]/Glance::Keystone::Auth/Keystone_service[glance]: Dependency Service[keystone] has failures: true
    Warning: /Stage[main]/Glance::Keystone::Auth/Keystone_service[glance]: Skipping because of failed dependencies
    Notice: /Stage[main]/Glance::Keystone::Auth/Keystone_endpoint[RegionOne/glance]: Dependency Service[keystone] has failures: true
    Warning: /Stage[main]/Glance::Keystone::Auth/Keystone_endpoint[RegionOne/glance]: Skipping because of failed dependencies
    Notice: /Stage[main]/Nova::Keystone::Auth/Keystone_user_role[nova@services]: Dependency Service[keystone] has failures: true
    Warning: /Stage[main]/Nova::Keystone::Auth/Keystone_user_role[nova@services]: Skipping because of failed dependencies
    Notice: /Stage[main]/Keystone::Roles::Admin/Keystone_user[admin]: Dependency Service[keystone] has failures: true
    Warning: /Stage[main]/Keystone::Roles::Admin/Keystone_user[admin]: Skipping because of failed dependencies
    Notice: /Stage[main]/Keystone::Roles::Admin/Keystone_user_role[admin@admin]: Dependency Service[keystone] has failures: true
    Warning: /Stage[main]/Keystone::Roles::Admin/Keystone_user_role[admin@admin]: Skipping because of failed dependencies
    Notice: /Stage[main]/Cinder::Keystone::Auth/Keystone_user[cinder]: Dependency Service[keystone] has failures: true
    Warning: /Stage[main]/Cinder::Keystone::Auth/Keystone_user[cinder]: Skipping because of failed dependencies
    Notice: /Stage[main]/Nova::Keystone::Auth/Keystone_endpoint[RegionOne/nova_ec2]: Dependency Service[keystone] has failures: true
    Warning: /Stage[main]/Nova::Keystone::Auth/Keystone_endpoint[RegionOne/nova_ec2]: Skipping because of failed dependencies
    Notice: /Stage[main]/Cinder::Keystone::Auth/Keystone_endpoint[RegionOne/cinderv2]: Dependency Service[keystone] has failures: true
    Warning: /Stage[main]/Cinder::Keystone::Auth/Keystone_endpoint[RegionOne/cinderv2]: Skipping because of failed dependencies
    Notice: /Stage[main]/Nova::Keystone::Auth/Keystone_service[nova]: Dependency Service[keystone] has failures: true
    Warning: /Stage[main]/Nova::Keystone::Auth/Keystone_service[nova]: Skipping because of failed dependencies
    Notice: /Stage[main]/Nova::Keystone::Auth/Keystone_endpoint[RegionOne/nova]: Dependency Service[keystone] has failures: true
    Warning: /Stage[main]/Nova::Keystone::Auth/Keystone_endpoint[RegionOne/nova]: Skipping because of failed dependencies
    Notice: /Stage[main]/Neutron::Keystone::Auth/Keystone_user_role[neutron@services]: Dependency Service[keystone] has failures: true
    Warning: /Stage[main]/Neutron::Keystone::Auth/Keystone_user_role[neutron@services]: Skipping because of failed dependencies
    Notice: /Stage[main]/Neutron::Keystone::Auth/Keystone_endpoint[RegionOne/neutron]: Dependency Service[keystone] has failures: true
    Warning: /Stage[main]/Neutron::Keystone::Auth/Keystone_endpoint[RegionOne/neutron]: Skipping because of failed dependencies
    Notice: /Stage[main]/Cinder::Keystone::Auth/Keystone_user_role[cinder@services]: Dependency Service[keystone] has failures: true
    Warning: /Stage[main]/Cinder::Keystone::Auth/Keystone_user_role[cinder@services]: Skipping because of failed dependencies
    Notice: Finished catalog run in 3.10 seconds
    Please let me know how to fix this.

    This problem connected with proxy-setings.
    As the first steps you should try:
           1.  export system env variable:
    http_proxy=http://www-proxy.ru.oracle.com:80
    https_proxy=https://www-proxy.ru.oracle.com:80
    no_proxy=127.0.0.1,localhost
    and you can also export
        export OS_TENANT_NAME=admin
        export OS_USERNAME=admin
        export OS_PASSWORD=root
        export OS_AUTH_URL=http://<conntroller_IP>:5000/v2.0/
    2. and than restart mysqld, if it is running, stop iptables and repeat installation process from beginning with the currently generated answer file
    if we are exporting variable OS_PASSWORD, its value should be the same as value for CONFIG_KEYSTONE_ADMIN_PW in the currently generated answer file.
    This OS_PASSWORD will be written by packstack in the /root/keystonerc_admin file and will be used as admin's password for login to  Openstack dashboard.

  • *** WARNING: Could not start service 80 for protocol HTTP on host MyFQDN

    Hi,
    I m configuring an external Sap webdispatcher to point to an ICF service
    I need to install it on Windows Web server where others web sites are running.
    I configured a specific ip for that on the Web servers and enter the DNS name in our domain.
    On the the pfl file I define :
    SAPLOCALHOSTFULL=<MyFQDN>
    icm/host_name_full =<MyFQDN>
    and specify icm/server_port_0 = PROT=HTTP,PORT=80
    Each time I m starting it I received *** WARNING: Could not start service 80 for protocol HTTP on host <MyFQDN> .........
    If I m using another port (Ex:86)no problem with my FQDN.But if I m doing servername:86 it s working also.
    It s seems that the webdispatcher don t care about my FQDN.
    How can I have the WEBDISPATCHER pointing to this specific FQDN and not all ?
    Thanks,

    Hi Damien,
    You problem is perfectly logical : It's not possible to have 2 programs (IIS and web dispatcher) listening together on the same 80 HTTP port.
    There is no configuration that I know on the web dispatcher to tell him to listen only on one IP address.
    Summary : what you want to do is not possible.
    I had a similar request and I did the following.
    I use a Linux box with an Apache reverse proxy to select to distribute the HTTP requests on different web dispatchers. The rules depends from the called URLs.
    Regards,
    Olivier

  • Could not start Service Broker for database id

    I am getting this message in the SQL Server error log:
    Could not start Service Broker for database id: 10. A problem is preventing SQL Server from starting Service Broker. Check the SQL Server error log for additional messages.
    It appears even when the broker is disabled on the database.  How can I eliminate this error?
    Thanks!

    In that case you're gonna have to contact Microsoft support, perhaps provide a copy of the database.
    Typical reason why a broker cannot be started is that another database with the same service_broker_guid already exists in the instance (result of a file copy/attach or a double restore). However, in that case a message is given that states the reason.

  • Could not start Service Broker for database

    Problem:
    Could not start Service Broker for database id: 9. A problem is preventing SQL Server from starting Service Broker. Check the SQL Server error log for additional messages.
    The windows and application logs do not give me any for information. I have checked the database instance and found that Database ID 9 does not exist in the sys.databases table. Could this be the reason?
    How do I resolve it so that SQL Server does not try and start Service broker for a database ID that does not exist?
    Any help will be greatly appreciated.
    Thanks.

    Hello Affy
    Solution/Fix: To avoid this alert, I have set the "Enable Disaster Recovery File Updates" parameter to 0 in the regedit at the below location.
    MY Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\Backup Exec For Windows\Backup Exec\Engine\SQL Server
    For furher details you can refer my blog.
    Regards,
    Naveen Kumar Thandra

  • DQE Service could not started.

    Hi All,
    I installed WAS 6.40 SP7 and then EP6 SP6 on Windows Platform. Installation was successfull.
    But when I tried to create Database iViews, its not opening the tables for the configured DB. Then i tried to open in Portal content page...
    System Administratation ---> Distributed Query Engine
    here when i open
    * Configuration -> No content is displayed.
    Session Manager -> DQE not installed(this messge is displayed)
    MetaData Loader -> Portal Runtime Error
    An exception occurred while processing a request for :
    iView : pcd:portal_content/administrator/super_admin/super_admin_role/com.sap.portal.system_administration/com.sap.portal.distributed_query_engine/com.sap.portal.metadata_loader
    Component Name : com.sap.portal.dqe.admintool.metadataloader.DQEMetadataLoader
    The exception was logged. Inform your system administrator..
    Exception id: 10:57_08/11/04_0002_9138850
    See the details for the exception ID in the log file.
    When i check the defalutTrace*.trc, the following message is printed...
    #1.5#00508BE9307C00170000006000000DA40003E86216ECCFF0#1099932919156#com.sap.engine.core.service630.container.ServiceRunner##com.sap.engine.core.service630.container.ServiceRunner#######SAPEngine_System_Thread[impl:5]_49##0#0#Error#1#/System/Server#Plain###Service DQE error. Nested exception is: com.sap.engine.frame.ServiceException: <Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='Could not start DQE service, reason: Could not initialize RuntimeStateAdminAPIImpl.', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key Could not start DQE service, reason: Could not initialize RuntimeStateAdminAPIImpl.
    at com.metamatrix.sap.service.MetaMatrixServiceFrame.start(MetaMatrixServiceFrame.java:144)
    at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:201)
    at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:142)
    at com.sap.engine.frame.core.thread.Task.run(Task.java:60)
    at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:73)
    at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:134)
    I fallowed the same instructions given in the installation guide, and insalled in two different machines,in both places I got same problem.
    Can any body tell me solution for this problem.
    When installing EP6SP3 I have choosen Portal Platform option(where we have DQE schema installation and Portal Platform option) and then updated to EP6SP6.Is it rigt?
    From SDN site I got WAS with SP7 and EP with SP6 , if any new stable versions available please let me know from where I can get them.
    Regards
    Abhilash

    Hello.
    I have the same problem and when I go into Visual Admin and try to start DQE manually I receive the following error:  Any help would be greatly appreciated.
    Start service DQE
    java.rmi.RemoteException: Could not start service DQE on cluster ID 6654350; nested exception is:
         com.sap.engine.frame.ServiceException: <Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='Service DQE error. Nested exception is: com.sap.engine.frame.ServiceException: <Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='Could not start DQE service, reason: Could not initialize RuntimeStateAdminAPIImpl.', Arguments: []--> : Can't find resource for bundle java.util.PropertyResourceBundle, key Could not start DQE service, reason: Could not initialize RuntimeStateAdminAPIImpl.
         at com.metamatrix.sap.service.MetaMatrixServiceFrame.start(MetaMatrixServiceFrame.java:144)
         at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:201)
         at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:142)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:60)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:73)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:145)
    ', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key Service DQE error. Nested exception is: com.sap.engine.frame.ServiceException: <Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='Could not start DQE service, reason: Could not initialize RuntimeStateAdminAPIImpl.', Arguments: []--> : Can't find resource for bundle java.util.PropertyResourceBundle, key Could not start DQE service, reason: Could not initialize RuntimeStateAdminAPIImpl.
         at com.metamatrix.sap.service.MetaMatrixServiceFrame.start(MetaMatrixServiceFrame.java:144)
         at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:201)
         at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:142)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:60)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:73)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:145)

  • Windows could not start the FLEXnet Licensing Service service on Local Computer Error 1068: The dependency service or group failed to start.

    Today I installed Adobe Director 11.5. I received a couple of errors in the FLEXnet Licensing Service. It looks It could not start. I tried to download the Licence fix what I found on Google but that doesn't work, so I checked the 'Service' at service (windows).
    It's status is empty. When I double click on the FLEXnet Licensing Service, clicked on start at the opened window and an error is coming: 
    Windows could not start the FLEXnet Licensing Service service on Local Computer
    Error 1068: The dependency service or group failed to start.
    I don't understand what it says with this message, only that it is impossible to start. However, that is not what I am trying of course, I want to start the FLEXnet Licensing Service, service. 
    Re-installing of the software, doesn't make any change. How can I start it so Director is also working?

    Hi Don1233,
    Please consider seek help at the software vendor side.
    For the services didn't start, follow the suggestions posted by Elton in the thread below:
    https://social.technet.microsoft.com/Forums/en-US/e35da253-f0df-41d1-8df2-b73fa54742a0/windows-could-not-start-the-flexnet-licensing-service-service-on-local-computer-error-1068-the?forum=w7itproinstall
    Best regards
    Michael Shao
    TechNet Community Support

  • Wndows could not start the SQL Server (MSSQLSERVER) service on Local computer

    I have 2 instance of SQL Server in same server. A is installed first and B next.
    Somehow A cannot start at all when I try to start from Windows Services.
    B can be started normally.
    A worked normally week ago. There has been only one thing what I may have to server since that.
    I have installed MondoDB. Currently MondoDB it is stopped. 
    windows could not start the SQL Server (MSSQLSERVER) service on Local computer
    Error 31: A device attached to the system is not functioning.
    Kenny_I

    I don't see anything special in event logs.
    Data file of both SQL Server instance are located on same C drive of same server.
    Kenny_I
    Hello Kenny,
    The main issue is not related to SQL server .SQL is at receiving end its hardware or the cables ( not sure which one) are the one causing issue.
    I serached
    http://social.msdn.microsoft.com/Forums/windowsdesktop/en-US/111da2ae-0a86-41a5-ba03-7d1c0cc91ea9/windows-error-code-31a-device-attached-to-the-system-is-not-functioning-properly?forum=wdk
    http://www.chicagotech.net/netforums/viewtopic.php?f=1&t=6467
    Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

  • "Windows could not start the offline files service on local computer. Error 3: The system cannot find the path specified"

    Using Windows 8.1 Pro on Toshiba Satellite i7 Laptop with 8Gb Ram
    After upgrade from Windows 8 Pro to 8.1 Pro, the Offline Files/CSC service refuses to start and gives the error message:
    "Windows could not start the offline files service on local computer. Error 3: The system cannot find the path specified"
    Before the upgrade, offline files worked fine... how do I re-enable offline files?

      I had a similar issue -  couldn't make any files available offline.
    I found that the offline folder service would not start
    This was because the CSC permission were totally screwed.  I had to take ownership of each folder and file, one by one, then grant everyone full access.
    then delete the full contents of the CSC folder
    format the CSC database using the registry fix then reboot
    in control panel, disable the offline files,  reboot, then re-enable.  and now its working :)
    2hrs to resolve this, with grateful thanks to this thread and some others.
    damn windows8

  • Could not start SQL services (Plz help me)

    I logged in windows with an administrator account, but I could not start sql services. Here is the newest log file, please help me to fix it. Thank in advanced.
    2014-10-02 16:17:49.06 Server      Microsoft SQL Server 2005 - 9.00.1399.06 (Intel X86) 
    Oct 14 2005 00:33:37 
    Copyright (c) 1988-2005 Microsoft Corporation
    Developer Edition on Windows NT 5.1 (Build 2600: Service Pack 3)
    2014-10-02 16:17:49.06 Server      (c) 2005 Microsoft Corporation.
    2014-10-02 16:17:49.06 Server      All rights reserved.
    2014-10-02 16:17:49.06 Server      Server process ID is 3888.
    2014-10-02 16:17:49.06 Server      Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
    2014-10-02 16:17:49.06 Server      This instance of SQL Server last reported using a process ID of 1104 at 10/2/2014 4:07:13 PM (local) 10/2/2014 9:07:13 AM (UTC). This is an informational message only; no user action is required.
    2014-10-02 16:17:49.06 Server      Registry startup parameters:
    2014-10-02 16:17:49.06 Server      
    -d C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
    2014-10-02 16:17:49.06 Server      
    -e C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
    2014-10-02 16:17:49.06 Server      
    -l C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
    2014-10-02 16:17:49.07 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
    2014-10-02 16:17:49.07 Server      Detected 2 CPUs. This is an informational message; no user action is required.
    2014-10-02 16:17:49.71 Server      Using dynamic lock allocation.  Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node.  This is an informational message only.  No user action is required.
    --The Anh--

    Hello,
    Can you tell us the status of the issue ? If you have found answer please post here so that it can help other members when needed. If You found answer in this thread please mark answer to the post and close the thread
    Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
    My Technet Articles

  • Could not start the oracle service on local computer

    Could not start the oracle service on local computer, did not return an error blah, blah.
    I am running Oracle 9i r2 Windows, and have choosen to start my instances manually. When i start them up I get the above error message. But if I am a little patient the services do start up and all is fine, so far as i can see anyway.
    I am curious to know why does this error message arise.
    Thanks in anticipation
    Fergus

    To start the database in windows you have to start first the OracleService<SID> service.
    These are the steps that you have to do at the command line:
    NET START OracleService<SID>
    SET ORACLE_SID=<database sid>
    sqlplus /nolog
    conn sys/password as sysdba
    startupJoel Pérez
    http://otn.oracle.com/experts

  • SCOM 2012 Data Access Service could not start

    Hello,
    I have 3 SCOM 2012 servers. I got the error that the All Managament Server Pool is not available. Google search give me a lot of posts to add folder PoolManager at HKLM\System\CurrontControlSet\services\HealthService\Parameters with the DWORD keys PoolLeaseRequestPeriodSeconds
    600 and PoolNetworkLatencySeconds 120. After restarting last SCOM server the Data Access Service could not run "Windows could not start the System Center Data Access Service. Error 1053: The service did not respond to the start or control request in a
    timely fashion"
    At Operations Manager Eventlog I see an error: "OpsMgr Management Configuration Service failed to communicate with System Center Data Access Service due the following exception: System.Runtime.Remoting.RemotingException: Unable to get ISdkService interface.
    Please make sure local Sdk Service is running."
    At System Eventlog I see an error: "A timeout was reached (30000 milliseconds) while waiting for the System Center Data Access Service service to connect."
    Why did it run on the both other servers and failes on the third one? What can I check?
    Regards, Doreen

    Hi,
    According to my understanding, after editing the registry key value, two of three management servers work fine now, and the issue only occur to the third one. Whether all those servers are running with Windows server 2012?
    I would like to suggest you re-check the service account for the data access service, maybe we can re-enter the account credential. Those three servers may use the same account for the service, make sure the account is not disabled and you enter in the right
    password for it.
    Here is a similar thread, please go through it for more details:
    http://social.technet.microsoft.com/Forums/en-US/f2281934-513d-4b60-bb4b-34ae8a892ace/failed-to-open-the-console-and-system-center-data-access-service-wont-start-scom-2012?forum=operationsmanagergeneral
    In addition, please also restart the third server and check the result, and I know that there is a similar error message in SCOM 2007:
    http://blogs.technet.com/b/csstwplatform/archive/2012/01/02/scom-2007-r2-unable-to-open-the-scom-console-after-server-reboot-the-sdk-service-is-stopped.aspx
    Regards,
    Yan Li
    Regards, Yan Li

  • Windows could not start the distributed transaction coordinator service on local computer

    Dear All,
    I'm having an issue starting the DTC service in windows 7 OS. I always got the error message below when im trying to start it.
    "Windows could not start the distributed transaction coordinator service on local computer"
    Thanks,
    Melvin

    Hi Melvin,
    Please try the following methods to solve this issue:
    Method 1: Re-create the MS DTC log, and then restart the service.
    Click
    Start, type cmd in the search box, and then press
    Enter.
    Type the command
    msdtc -resetlog at the command prompt, and then press
    Enter.
    Warning: The msdtc -resetlog command can cause data corruption if it is used incorrectly. Make sure that you do not have any pending transactions when you run this
    command.
    Type the command net start msdtc, and then press
    Enter.
    Method 2: Set the logon account permissions for the MS DTC service
    If Method 1 does not resolve the problem, set the logon account for the MS DTC service to have read and write permissions for the Msdtc.log file. Please follow the steps below:
    Click
    Start, type cmd in the search box, and then press
    Enter.
    Type the command
    control admintools at the command prompt, and then press
    Enter.
    Double-click
    Services.
    In the Services pane, locate
    Distributed Transaction Coordinator.
    In the
    Log On As column, note the account name.  Note: The default logon account for the MS DTC service is the NETWORK SERVICE account.
    Start Windows Explorer, and
    then open the %windir%\System32\Msdtc folder.
    Right-click the
    Msdtc.log file, and then click Properties.
    Click the
    Security tab.
    Click the logon account name that you noted
    in step 5. For example, click the NETWORK SERVICE account name.
    In the
    Permissions pane, click to select the Allow check box for the following permissions: ◦Read & Execute  
    ◦Read    ◦Write
    Click
    OK.
    Click
    Yes to accept the security warning.
    In the
    Services pane, right-click Distributed Transaction Coordinator, and then click
    Start.
    Method 3: Assign permissions to the NETWORK service to traverse the directory tree
    Determine whether the NETWORK service has permissions to traverse through the folder. To do this, follow these steps.
    Note: By default, the "Everyone" group has these permissions. For more information, go to the following Microsoft TechNet website:
    Bypass traverse checking
    Click
    Start, type secpol.msc in the search box, and then press
    Enter.     
    Browse through the following computer configuration: 
            \Windows Settings\Security Settings\Local Policies\User Rights Assignment 
    Check for "Bypass traverse checking," and then add the "Everyone" group. 
    Update the Group Policy settings on the computer. To do this, click
    Start, type gpupdate in the search box, and then press
    Enter.
    In the
    Services pane, right-click Distributed Transaction Coordinator, and then click
    Start.
    Regards,
    Lany Zhang

  • Windows could not start the Network Location Awareness service on Local computer

    i have a dell inspiron 1501 laptop running windows vista home premium media center edition. i have recently been getting an error when trying to view networked computer saying  "connection status: unknown" and "the dependency service or group failed to start". i started by disabling and re-enabling the driver and that did not help. i then brought up the services.msc thing and started looking at the networking services. i noticed that the Network Location Awareness service was not started so i tried to start it. i got a popup message saying "Windows could not start the Netwrok Location Awareness service on Local Computer. Error 0xc000096: 0xc0000096".
    i also get an error popup when i try to start the Network List service saying "Windows could not start the Network List Service service on Local Computer. Error 1068: The dependency service or group failed to start".
    what might i have done to make this happen and what can i do to try to fix it?
    haus

    Hi,
    Thank you for the post.
    I fully understand the inconvenience the issue has been caused and the current situation can be frustrating. Please try the following steps for troubleshooting.
    1.    Please start the computer in Safe Mode with Network and check the result. If the issue disappears, please perform a clean boot.
    For the detailed steps, please refer to the step 1 and 2 in the KB article 936214 (http://support.microsoft.com/kb/936214).
    2.    If the issue persists, please check the system file by using the command SFC /scannow.
    For more information, please refer to the KB article 929833 (http://support.microsoft.com/kb/929833).
    If the above suggestions do not resolve the issue that service fails to start up, please understand that debug and dump analysis may be required for further troubleshooting. Also, in most cases, it is necessary to check the source codes. However, debugging is out of our forum’s support boundary. A support call to our product service team is needed for the debugging service. In this case, I’d like to suggest contacting Microsoft Customer Support Service (CSS) for assistance so that this issue can be resolved efficiently.
    To obtain the phone numbers for specific technology request, please check the website listed below:
    http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHONENUMBERS
    Thank you for your understanding.
    Sincerely,
    Joson Zhou
    Microsoft Online Community Support

  • Windows could not start the DHCP Client service on Local Computer, Error 2

    Hi everyone,
    I assign IP addresses via my router but today installed OpenVPN and it depends on the DHCP Client service. I checked in services and found it wasn't running. If I try starting it I get this message "Windows could not start the DHCP Client
    service on Local Computer." "Error 2: The system cannot find the file specified.".
    There's plenty of info out there about this issue but nothing seems to fix it for me. I've tried the following as an administrator,
    "sfc /scannow" - It reported and error which it fixed but after a restart the problem persists.
    "NET  LOCALGROUP   administrators  "NT Authority\Local Service"   /add"
    "netsh winsock reset catalog"
    I also checked that all dependencies of the DHCP Client service are working. I used "CMD /K
    SC QC DHCP" to check the dependencies and compared them to an identical computer and they are. Hope someone can help. Thanks in advance.

    Hi,
    Did you mean after the restart the sfc /scannow command still could find the corrupted files?
    Have you check this these related registry entries permission for your account?
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Dhcp
    permission needed: Query value, Create value, Enumerate Subkeys, Notify, Read Control
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Dhcp\Configurations
    permission needed: Full Control, Read
    for more information, read this article:
    Some services do not start in Windows Vista and Windows 7
    https://support.microsoft.com/kb/943996?wa=wsignin1.0
    If the issue still cannot be resolved, I would like to suggest you use the recovery media to repair your computer.
    Karen Hu
    TechNet Community Support

Maybe you are looking for