Dabacon Error 580 is listed as 'File refresh failed' so my guess is that you are suffering network connectivity drop-outs from time to time which are only resovled by changing modules
Try running PDMS with the logging options turned on and see what messages are output...
For example, set the following evars before going into PDMS: set PDMSLOG=C:\PDMSLog.txt
set PDMSLOGOPT=MDBMODSWEXPUNGECOMMDB
Are you saying the log file has NO MESSAGES or just none that you consider to be relevant?
We don't get any problems here with McAfee but obviously the software could be configured differently... I would guess that in the end you will have to contact AVEVA support
In the meantime though you could try running some tests with the model on the local hard disk to see if you still get the problem when you no longer access data across the network
10 Dec 12:20:47.489 llpa:Xfb0-NLIDSK7004 Database error 38 from DFINDI
10 Dec 12:20:47.504 llpa:Xfb0-NLIDSK7004 - File read failed
10 Dec 12:20:47.520 llpa:Xfb0-NLIDSK7004 Extra info: 1GP:Name is \\NLIVEA05\PDMS\PROJECT\SLA\SLA000\slasys,Dbno is 8191,pgid is 6 1,Token is 49,Flayer error is MCD:64
The specified network name is no longer available.
10 Dec 12:20:47.520 llpa:Xfb0-NLIDSK7004 Current element is =24575/4 [illegal refno]
10 Dec 12:20:47.536 llpa:Xfb0-NLIDSK7004 Unhandled Database error 38 from DFINDI
10 Dec 12:20:47.536 llpa:Xfb0-NLIDSK7004 - File read failed
10 Dec 12:20:47.551 llpa:Xfb0-NLIDSK7004 Extra info: 1GP:Name is \\NLIVEA05\PDMS\PROJECT\SLA\SLA000\slasys,Dbno is 8191,pgid is 6 1,Token is 49,Flayer error is MCD:64
The specified network name is no longer available.
10 Dec 12:20:47.551 llpa:Xfb0-NLIDSK7004 Last Dabacon routines called:
10 Dec 12:20:47.551 llpa:Xfb0-NLIDSK7004 db_go_to_element =16382/25 %COMM [no name] in Comm Db, number 8190
10 Dec 12:20:47.551 llpa:Xfb0-NLIDSK7004 db_go_to_element =16382/25
10 Dec 12:20:47.567 llpa:Xfb0-NLIDSK7004 DNTGTS =16382/25
10 Dec 12:20:47.567 llpa:Xfb0-NLIDSK7004 DGOTO =16382/25
10 Dec 12:20:47.567 llpa:Xfb0-NLIDSK7004 DFINDI =24575/4 %STAT /*S in System Db, number 8191
10 Dec 12:20:47.567 llpa:Xfb0-NLIDSK7004 This error was set in call 224 to DABKER
10 Dec 12:20:47.583 llpa:Xfb0-NLIDSK7004 Current element was =24575/4 %STAT /*S in System Db, number 8191
10 Dec 12:20:47.614 llpa:Xfb0-NLIDSK7004 Exiting : Database error 38
10 Dec 12:23:21.569 llpa:Xb78-NLIDSK7004 Entering PDMS on NLIDSK7004, running 5.1
IT dept says nothing is ruuning at this time from their end.
Aveva support desk, as usual, knows less about Pdms than I do. I'm lucky if I can get one that has actually used Pdms. I've been using Pdms for 24 years and am tired of being told the obvious when I contact them. I don't tend to contact them until I have tried ALL possible routes I (and my contacts) can think of.
From reading your last post the answer would seem to relate to this Flayer message in the log file: Flayer error is MCD:64
The specified network name is no longer available.
My understanding of this is limited but I believe that after you have initially entered PDMS successfully your network must be dropping out temporarily for some reason (not related to PDMS) between your PC and the server holding the databases. Some time later when PDMS running on your PC tries to find the database files that had been located and opened on entry the files are no longer available... and everything comes crashing down!
HowlingWolf, I totally agree with your conclusions.
However, what makes it strange is this. We have our license files on the same server and the conection to these are not lost. If the connection goes down then the user should get a warning that FlexLM is trying to re-connect (usually up to 5 times).
This happens everyday between 12 and 1. Even stranger though is the fact that it only affects a handful of people (we have 56 users in the project and only 6 or 7 occurances of this problem).
Not that I am a professional IT guy by any means but it sounds to me like there is a problem with a part of the network in your office, maybe a bad switch or something of that nature.