Thanks very much for the great support. I will be placing an order for the software.

Hi,

I am testing out the Data Logger Suite before purchasing to see if it's meets our needs and I have come across the following problem.
I am sending sms data to a test database and it is correctly importing the data but the following error message appears SMS Interface. Command "AT+CMGD=0 is not supported". The SIM card eventually fills up with 50 messages and then no further messages are received. The modem is a Sierra Wireless Fastrack Xtend FXT009.

Thanks

Hi Arthur,
I have emailed you the requested files.

Hi,
We are using the SQL Database Professional plugin to export our data to a MSSQL database. In the 'Handling Errors' screen we have set it to 'Write data to a temporary file, then try to write to the database again', so far so good. When it does get an error though it writes the data successfully to the temporary file, the problem then occurs when it then reads the data from the temporary file and inserts in to the database. It successfully writes the data but it doesn't then remove the data or flag it as inserted in to the database, so it keeps writing the data to the database every time it reads from the file. The error log has full read/write permissions and it does sometimes successfully write to the database once and the data is then removed from the log.
If I manually remove the text from the error log it stops writing the multiple entries to the database and if I then add the data back to the log it starts inserting the data multiple times again so i'm pretty sure that this is where the problem is occurring.
Thanks

Ok, so i'm getting a little further with this problem. Before the weekend I changed the location of the MSSQL database that the data is wrote to. This morning I checked the error log and I have found that there is only 6 errors compared to 100's of errors before. The previous database was set to not allow duplicates. The current database does allow duplicates. I have checked the error log and all of the 6 lines of data have been inserted in to the database correctly, the problem is that the same line of data has been inserted 1000's of times in to the database. If I watch the live data coming in I can see the error message:
"Restoring row #1"
"unable to write to database[[Microsoft][SQL Server Native Client 11.0] invalid cursor state"
It does this for each of the 6 lines of data in the error log.

I have checked the data that is failing with previous lines of successful data and there is no difference.

No I don't think so because the problem is intermittent, so sometimes that data is inserted in to the database correctly and every line in the error log shows 0|0
Then for no reason (the last one happened at 04:30 this morning for around 30 minutes) the data doesn't get inserted to the database and the error log shows 1|0 on the first line then the very next line shows identical data but with a 0|0 but the data still doesn't get inserted

Thanks for the reply. The problem is the data still hasn't been restored

Hi Arthur,

I have emailed the error log, it includes one row with 1|0 and the second row with the same data but a 0|0 at the start of the row

You want me to post the data on here?

What are the 1|0 or 0|0 for in the error log?

Hi Arthur,
I have had some errors recently where data isn't being inserted in to the MSSQL database from TCP/IP logger. I have checked the error log and am I correct in assuming that if the start of the data shows 0|0 the insert has been successful and 1|0 if the insert was unsuccessful?
The error log that I checked this morning shows the data coming in and first shows 1|0 then the following line shows the exact same data but with 0|0 at the start. The problem is that the data hasn't actually been inserted in to the database.
Please could you tell me where the software receives the success insert flag from, does it receive it from the database. Also could you offer any assistance in tracing the source of the error?

Thanks

Hi Arthur,
The SQL plugin had been working fine and had been correctly registered previously but for some reason registering it again resolved the issue.

Hi,

I am running Advanced TCP/IP logger as a service on Server 2012, it logs on as a local system account and it has access to interact with the desktop and mostly it works well. The issue I have is if there is a problem with data being received and I want to see if the data is coming and being sent to the database, I can't check it as I can't open the GUI without first stopping the service and then re-opening the program as administrator. This is OK but then I have closed and opened the program as a different user (which may resolve the issue, so I don't know what caused it), also when I then try to close the program and restart it as a service it doesn't always start up properly and start logging. Yesterday when I did this I spent hours trying to find out why it wasn't logging data and in the end I had to re-register the sqldb_pro.dll.

Thanks,