| SOCKET.ERR |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through June 21, 2007 ⬆ |
◄ ► |
| Author | Message | |||
| Ramon Sazon New member Username: Ramonsazon Post Number: 19 Registered: 08-2006 |
Hi, I saw this file "SOCKET.ERR" in the NOWSMS directory. It was empty but I was just concerned. Do you guys know what it means? Thanks. RS | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6998 Registered: 10-2002 |
Hi Ramon, I know that this is a file that NowSMS sometimes creates, as I've seen it before. But I don't know too much about it, so I had to do some investigation. It appears that this file is created if the NowSMS service starts up and the "Web port" cannot be allocated (usually because another web server is already using the port). When this happens, NowSMS generates an event log message, and optionally an e-mail alert. It also creates this empty file. The empty file is simply used as an external signal for NowSMS to know that it has encountered this problem. This particular error is considered fatal, and causes the NowSMS service to fail to initialise. When this happens, the service manager waits a little while, and then tries again. When NowSMS encounters an error again, it looks to see if SOCKET.ERR already exists ... and if it does, it checks to see if it was created the same day. If it was created the same day, NowSMS doesn't generate another alert or event log entry, as it would do this repeatedly, causing other problems. If it was created on a different day, NowSMS re-creates it, and generates its log entry/alert. However, there is no "ok" situation which causes NowSMS to delete this file. If the file was ever created, it just stays there. It is ok to delete the file ... or it is ok to leave it. -bn | |||
| Ramon Sazon New member Username: Ramonsazon Post Number: 20 Registered: 08-2006 |
Thanks Bryce. | |||
