| Unable to initialize modem: Error 80000018 from lineGetID |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through May 12, 2004 ⬆ |
◄ ► |
| Author | Message | |||
| Stanley Unregistered guest |
How comes I always notice an error from nowsms's smsdebug.log? The error is "Unable to initialize modem: Error 80000018 from lineGetID". It appears every 1 or 2 days and apears for about 2-3 hours. This is very annoying because I have sms received every hour. I suspected that this should not be happened, since nowsms could be able to automatically recover from the status without any manual action after 2 to 3 hours. $--------------------------------------$ 09:10:59:452 [2] ThreadProcessModem: Before ModemAllocate - Unknown Modem 09:11:01:955 [2] ThreadProcessModem: After ModemAllocate - Unknown Modem - OK 09:11:01:955 [2] ThreadProcessModem: Re-initializing modem: Unknown Modem ... 09:11:20:082 [2] OpenDevice: Unable to initialize modem: Error 80000018 from lineGetID 09:11:20:082 [2] ThreadProcessModem: Before ModemRelease - Unknown Modem 09:11:20:082 [2] ThreadProcessModem: After ModemRelease - Unknown Modem $--------------------------------------$ Could you help me to solve it? Many thanks. | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 2213 Registered: 10-2002 |
Stanley, I'd like to see more complete logs from your system, if you could e-mail them to nowsms@now.co.uk. Although, that said, I'm not sure they will help me understand any better. This particular error is coming back from TAPI, which is the Windows Telephony API subsystem (which we use to initialise the modem when NowSMS is configured to use a named modem driver instead of a COM port). So its not really NowSMS that is automatically recovering after some time ... instead, the probably at the TAPI layer recovers after some time, and allows NowSMS to talk to the modem via TAPI again. Also, are you receiving MMS via GPRS on this modem as well? I'm guessing that you are. What I'm thinking is that something is going wrong relating to the termination of a GPRS session that is used for MMS sending or receiving. My thought is that the GPRS session is not terminating properly for some reason, and this prevents TAPI from being able to reinit the modem. Unfortunately, if this is the case, I'm not sure what the best thing is to do. The modem driver generally sends a command to terminate a GPRS session ... and even if that fails, it will drop the DTR signal at the end of the connection, which should cause the modem to drop the connection and return to command mode. Unfortunately, I'm not sure the best way to troubleshoot this. You might want to go into the Windows Control Panel ... Phone and Modem options ... select "Properties" for the modem ... and on the "Diagnostics" page, there should be an option "Append To Log". It would be interesting to see that log after this problem occurs. That might tell us if there is a problem releasing a GPRS connection right before the problem is triggered. -bn | |||
