MonitorWare Knowledge Base

Hi

When looking at my database of syslogtags (in SQL server) they all have a carriage return appended to the end of the syslog tag.

This is causing me problems with my application which queries the database using filters (to filter out the syslog tags I don't want to see)

can someone confirm if this is a problem, and whether this will be fixed?

Thanks

Hi tosh.

I think there are 3 possibilities where the carriage returns could have come from.
1.The syslog tag itself (How do your syslog tags look like?)
2.While writing the database entry (sounds plausible)
3.While viewing the db with SQL Server. (but you said, they where there when you used your app to access the db.)
Still thinking.

Hi

I've got a Vigor 2600 ADSL router, which is throwing out messages like:

ADSL_Status:[Mode=G.DMT States=SHOWTIME UpSpeed=288000 DownSpeed=2272000 SNR=12.5 Atten=43.0 ]

Therefore the SysLogTag is ADSL

When I look in SQL Query Analyzer at the row, I can copy the ADSL item from the grid, and when I paste it into Notepad, it appears with a <CR>

I've worked around it, by trimming the value of SysLogTag whenever I use it, but you may want to fix this in the future.

I think this also used to happen with PIX messages (i've since purged my PIX messages from the database) - I think you have a PIX there, and so can test this yourself (if you also have SQL server).

Let me know if you want any more information from me

Regards

Ho Tosh,

sorry for the delay. I checked that with Query Analyzer. It always appends a CRLF if you copy something out of it. Even if you copy a field with a NULL value, it appends a linefeed.

So there seems to be another Problem. Possibly, a space is at the end of the SyslogTag value?

ok, thanks for the info

I've got a workaround, by doing a TRIM when I get the value out of the database, so it's not a problem for me.

If I find any more info, I'll update the post.

Regards