Direkt zum Hauptbereich

This device is not working properly because Windows cannot load the drivers required for this device. (Code 31)

No solution yet. :-(

It started all when I installed Windows 7. To get online when travelling I installed a driver for a UMTS stick and it all worked fine, but suddenly the connection could not be established (anymore!).

I tried a thousand things, but I am still stuck with this error. When I plug in the UMTS stick I get an error when installing the driver  - something with modem always.

Then I got a new mobile phone - Samsung Galaxy S plus and when I plug it, I get the same error. :-(

Kies cannot connect. :-(

Now I unstalled the device (without deleting the software. Let's see what happens.

Then I unplugged the device and let Kies install some driver. It does not say what exactly.

After plugging in the phone it has the same error when installing the driver:

 

Eventlog says this: "The description for Event ID 1 from source Modem cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

\000000a4"

Update Jan 2012: I gave up and installed my whole Win 7 from scratch. Now it works again. I wonder what broke it and if it will happen again. :-(
Labels:

Kommentare

Kommentar veröffentlichen

Beliebte Posts aus diesem Blog

How to delete WebSEAL servers which have not been configured correctly.

Problem: The WebSEAL server list in the pdadmin: pdadmin> server list shows the server, but it does not exist anymore, i.e. because the host has been disassembled without unconfiguring the WebSEAL instance. Solution: 1.) Delete the instance in the LDAP under: SecAuthority=Default - cn=securitygroup - cn=webseal-servers - cn=secmgrd-servers 2.) Configure the instance again, which will lead to an error, because it seems to be installed already. Configuring WebSEAL instance 'DO-06'...HPDMG0453E A server with the same name already exists.DPWCF0473E The WebSEAL instance 'DO-06' failed to configure. 3.) Unconfigure the instance, which will show errors, but remove the instance totally. # amwebcfg -action unconfig -inst_name DO-06 -admin_id sec_master -admin_pwd ********* Unconfiguring WebSEAL instance 'DO-06'... 2008-10-28-15:30:10.158+01:00I----- 0x389D51F2 amwebcfg ERROR wcf Error WebCfgAdminApi.cpp 84 0x002198d0 DPWCF0498E The user 'DO-06-webseald/srv1252'
Kommentar veröffentlichen
Mehr anzeigen

GSK_KEYRING_OPEN_ERROR-Keyring file did not open

2011-01-18-10:06:22.760+01:00I----- 0x389D0389 webseald WARNING wca revpwd revpwdchk_gskit_sock.c 130 0x0403ab90 DPWCA0905W   Function call, gsk_environment_init, failed error: 000000ca GSK_KEYRING_OPEN_ERROR-Keyring file did not open. 2011-01-18-10:06:22.760+01:00I----- 0x13212064 webseald WARNING ias general pdauthn.cpp 1740 0x0403ab90 HPDIA0100E   An internal error has occurred. Function call, func, failed error: error code error text. Explanation: The specified GSKit function failed while setting up for SSL connections to junctions or from browsers. Or perhaps the initial handshake failed due to invalid certificates or the browser simply closed the connection abruptly. Action: Examine the error text for details. Typical problems might be that the PKCS#11 library is incorrectly specified, or the PKCS#11 token or token password is incorrect, or the PKCS#11 token is not set up. Name: revpwd_s_ssl_status_function_ failed Number: 0x389d0389 (949814153) Severity: W
Kommentar veröffentlichen
Mehr anzeigen

DPWWA1203E Permission denied // DPWAD0312E Object list failed: Forbidden

cmd> server task cnt-1a-webseald-hst7127 create -f -t tcp -h -v hst7105 -p 80 -w /ICB DPWWA1203E Permission denied pdadmin sec_master> object list /WebSEAL/hst7127-cnt-1a DPWAD0312E Object list failed: Forbidden The reason for this behaviour was that somehow my container /WebSEAL in the object space got the ACL default-root instead of default-webseal by the installation. pdadmin sec_master> object listandshow /WebSEAL Name: /WebSEAL/hst7127-cnt-1a Description: WebSEAL Server Object Type: 5 (Junction) Is Policy Attachable: Yes Extended Attributes: Attached ACL: Attached POP: Attached AuthzRule: Effective Extended Attributes: Effective ACL: default-root Effective POP: Effective AuthzRule: Name: /WebSEAL/hst7127-mas-01 Description: WebSEAL Server Object Type: 5 (Junction) Is Policy Attachable: Yes Extended Attributes: Attached ACL:
Kommentar veröffentlichen
Mehr anzeigen