B
Bruno Willi
Our application dials into multiple ras-servers for collecting
decentralized data to store them central.
The system should run 24-7 and the dial-in process works autonomatically.
Basically this works fine, but for some reason sometimes the
RasDial-Api-Funktion fires an asynchronous delegate with the error code
676 (LINE_BUSY). From now on, no further connection can be established,
not automatically nor manually with a dial-up-connetion (they always
produce error 676)
When our application is stopped, the manual dial-up-connection works again.
When looking at the modem-log-file I can see, that the ATDT-command
isn't sent to the modem anymore. The log looks ok for me (with Port
open, init-strings, responses from modem and so on...) until the message
"TSP(0000) Stopping monitoring". After that, the unimodem-drivers seem
to be loaded again (c:\winnt\system32\unimod*.drv plus
version-informations are logged) for the next call.
Does someone know, what causes this error 676 - the line can't be busy,
because the dial-command does not even reach the modem as stated above.
And when our application is closed, the manual dial-up works fine.
The order is basically as follows:
1. RasDial
2. When OnConnect event fired, a Http-Request is made
3a. When data retrieved, the connection is closed by RasHangup
3b. When an error event occured (..like 676), the RasHangup-function is
called.
System: W2K SP4
Modem: Devolo Microlink 56k PCI
Environment: C# with .NET
We wrap the Windows RAS Api with a .NET class.
I would appreciate any hint or help for that problem!
Bruno
decentralized data to store them central.
The system should run 24-7 and the dial-in process works autonomatically.
Basically this works fine, but for some reason sometimes the
RasDial-Api-Funktion fires an asynchronous delegate with the error code
676 (LINE_BUSY). From now on, no further connection can be established,
not automatically nor manually with a dial-up-connetion (they always
produce error 676)
When our application is stopped, the manual dial-up-connection works again.
When looking at the modem-log-file I can see, that the ATDT-command
isn't sent to the modem anymore. The log looks ok for me (with Port
open, init-strings, responses from modem and so on...) until the message
"TSP(0000) Stopping monitoring". After that, the unimodem-drivers seem
to be loaded again (c:\winnt\system32\unimod*.drv plus
version-informations are logged) for the next call.
Does someone know, what causes this error 676 - the line can't be busy,
because the dial-command does not even reach the modem as stated above.
And when our application is closed, the manual dial-up works fine.
The order is basically as follows:
1. RasDial
2. When OnConnect event fired, a Http-Request is made
3a. When data retrieved, the connection is closed by RasHangup
3b. When an error event occured (..like 676), the RasHangup-function is
called.
System: W2K SP4
Modem: Devolo Microlink 56k PCI
Environment: C# with .NET
We wrap the Windows RAS Api with a .NET class.
I would appreciate any hint or help for that problem!
Bruno