Application using COM1 port for fax modem on windows SBS03


hello all,

i've been running dell poweredge 840 few months @ work, have been using fax server, among other things, robotics 3453c modem connected via serial cable. in beginning work fine,  past few months else start using com1 port , fax stop working. when go modem properties , try query modem, says "the port modem using open application. exit application may using port." i'm not sure using port, think may have apci multiprocessor. if uninstall , reinstall modem driver, fax start working again, pretty i've been doing 3 months, happening every day past few days, instead of 2-3 times month. i've tried create com port in device manager see if help, whenever resource conflicts apci multiprocessor , pci bus. appreciated. below modem log, not sure if help.

---
03-17-2009 10:15:43.333 - file: c:\windows\system32\drivers\modem.sys, version 5.2.3790  
03-17-2009 10:15:43.333 - file: c:\windows\system32\modemui.dll, version 5.2.3790  
03-17-2009 10:15:43.333 - file: c:\windows\system32\mdminst.dll, version 5.2.3790  
03-17-2009 10:15:43.333 - modem type: courier v.everything ext pnp (v90-x2)
03-17-2009 10:15:43.333 - modem inf path: mdmusrgl.inf
03-17-2009 10:15:43.333 - modem inf section: modemusr0084
03-17-2009 10:15:43.333 - matching hardware id: serenum\usr00ba
03-17-2009 10:15:43.333 - opening modem
03-17-2009 10:15:43.333 - 115200,8,n,1, ctsfl=1, rtsctl=2
03-17-2009 10:15:43.333 - initializing modem.
03-17-2009 10:15:43.348 - send: at<cr>
03-17-2009 10:15:45.348 - timed out waiting response modem
03-17-2009 10:15:45.348 - modem failed respond initialization command, retrying 1 more time
03-17-2009 10:15:45.348 - 115200,8,n,1, ctsfl=1, rtsctl=2
03-17-2009 10:15:45.364 - send: at<cr>
03-17-2009 10:15:47.364 - timed out waiting response modem
03-17-2009 10:15:47.364 - modem failed respond initialization command, retrying 1 more time
03-17-2009 10:15:47.364 - 115200,8,n,1, ctsfl=1, rtsctl=2
03-17-2009 10:15:47.380 - send: at<cr>
03-17-2009 10:15:49.379 - timed out waiting response modem
03-17-2009 10:15:49.379 - tsp(0000): lineevent: line_close
03-17-2009 10:15:49.379 - session statistics:
03-17-2009 10:15:49.379 -                reads : 0 bytes
03-17-2009 10:15:49.379 -                writes: 9 bytes
03-17-2009 10:15:49.379 - file: c:\windows\system32\tapisrv.dll, version 5.2.3790  
03-17-2009 10:15:49.379 - file: c:\windows\system32\unimdm.tsp, version 5.2.3790  
03-17-2009 10:15:49.379 - file: c:\windows\system32\unimdmat.dll, version 5.2.3790  
03-17-2009 10:15:49.379 - file: c:\windows\system32\uniplat.dll, version 5.2.3790  
03-17-2009 10:15:49.379 - file: c:\windows\system32\drivers\modem.sys, version 5.2.3790  
03-17-2009 10:15:49.379 - file: c:\windows\system32\modemui.dll, version 5.2.3790  
03-17-2009 10:15:49.379 - file: c:\windows\system32\mdminst.dll, version 5.2.3790  
03-17-2009 10:15:49.379 - modem type: courier v.everything ext pnp (v90-x2)
03-17-2009 10:15:49.379 - modem inf path: mdmusrgl.inf
03-17-2009 10:15:49.379 - modem inf section: modemusr0084
03-17-2009 10:15:49.379 - matching hardware id: serenum\usr00ba
03-17-2009 10:15:49.379 - opening modem
03-17-2009 10:15:49.379 - 115200,8,n,1, ctsfl=1, rtsctl=2
03-17-2009 10:15:49.379 - initializing modem.
03-17-2009 10:15:49.395 - send: at<cr>
03-17-2009 10:15:51.395 - timed out waiting response modem
03-17-2009 10:15:51.395 - modem failed respond initialization command, retrying 1 more time
03-17-2009 10:15:51.395 - 115200,8,n,1, ctsfl=1, rtsctl=2
03-17-2009 10:15:51.395 - send: at<cr>
03-17-2009 10:15:53.395 - timed out waiting response modem
03-17-2009 10:15:53.395 - modem failed respond initialization command, retrying 1 more time
03-17-2009 10:15:53.395 - 115200,8,n,1, ctsfl=1, rtsctl=2
03-17-2009 10:15:53.411 - send: at<cr>
03-17-2009 10:15:55.411 - timed out waiting response modem
03-17-2009 10:15:55.411 - tsp(0000): lineevent: line_close
03-17-2009 10:15:55.411 - session statistics:
03-17-2009 10:15:55.411 -                reads : 0 bytes
03-17-2009 10:15:55.411 -                writes: 9 bytes

 

hi,

 

thank update.

 

as issue may occur when 3 rd part application or driver occupied port. locate root cause efficient, should use adplus collect , analyze dump of crash. unfortunately, cannot analyze dump file in newsgroup threads. so, need contact microsoft customer support services (css) dedicated support professional can assist request. thank understanding.

 

regards,


nick gu - msft


Windows Server  >  Print/Fax



Comments

Popular posts from this blog

CRL Revocation always failed

Failed to query the results of bpa xpath

0x300000d errors in Microsoft Remote Desktop client