9/20/2006 1:56 PM | |
Posts: 1275 Rating: (123)
|
Hi! The log files are in the C:\Program Files\Siemens\WinCC\Diagnose folder, as a default. |
9/27/2006 4:49 AM | |
Posts: 18 Rating: (0) |
Sorry for delayed response My 4 WinCC log files are attached in zip folder. Note that the behaviour of the project i mentioned in my first post in a bit inconsistent. Sometimes it goes 3 days back and some times 8 min back data in an attempt to fetch last 6 min of data. Sometimes it works well for the first cycle query and then starts misbehaving. One thing it is consistent about is that it keeps on giving the values of first cycle again and again until WinCC is restarted again. I am not using Time synchronization and not using any C Scripts AttachmentWincCC Log files.zip (282 Downloads) |
9/28/2006 11:05 AM | |
Joined: 9/27/2005 Last visit: 11/27/2007 Posts: 1398 Rating: (150)
|
Your log file contains lots of errors like : "ArchiveManager,Database ArchiveManager\TagLoggingSlow\KIII_Dhabeji WInCC_TLG_S_200609031901_200609041901.mdf does not exist!" and : "TLGRT,Error archiving at least one tag - tagname: ProcessValueArchive\MV_MF4_kVAr_R" It sounds like your database files may be corrupt / missing / something ! If possible I would delete all runtime data (http://support.automation.siemens.com/WW/view/en/17853608). I would also recommend you look at the above tag and see why it cannot be archived. It could be that the configuration database is messed up to !!? If so then you can use the Excel Configuration Tool to export the database into a new project to recover from the corruption (only do this as a last resort as it is a little fiddly). Key thing is, you have a problem querying your tag logging data and your log files show errors with the tag logging data. Clear the errors and the querying problem should disappear too. |
9/29/2006 7:45 AM | |
Joined: 10/13/2005 Last visit: 1/30/2024 Posts: 33 Rating: (3) |
Your problem with the hysteresis 0,0% tag that has no value (has never changed) might be the same problem I had when using the conn. pack to get alarm archive values. I found out that the WinCC OLE DB driver "errors out" when the result dataset is empty (instead of just returning an empty dataset). The error situation was diagnosed by the Siemens Conn. Pack developers and they found an error in the conn. pack. They then sent me a Hotfix (Hotfix 5) and I verified that the problem was fixed. This hotfix isn't yet available to the public but will be in the next service pack of WinCC. More info on the problem here: /tf/WW/en/Posts/3788 |
Follow us on