RE: [NMusers] error (157) forrtl: severe

Brian, I sent you the screen shot directly. For the NMusers: n=
o there is no file name associated with it. Joachim =

m> 07.12.2007 15:00 To "'Mark Sale - Next Level S=
olutions'" <mark_at_nextlevelsolns.com>, <Joachim.Grevel_at_merckserono=
.net> cc <nmusers_at_globomaxnm.com> Subject RE: [NMus=
ers] error (157) forrtl: severe Jo=
achim, I tried running two jobs simultaneously in the same dire=
ctory and received the error: C:\Documents and Set=
tings\brian\nonmem.exe Access is denied. Then after th=
e normal warnings: forrtl: severe (47): write to READONLY file,=
 unit 12, file C:\Documents and Settings\brian\Documents\FDATA I=
mage PC Routine Line Source nmtr=
an.exe 005106BE Unknown Unknown Unknown =

EADONLY file, unit 6, file C:\Documents and Settings\brian\OUTPUT =

nonmem.exe 00524E3E Unknown Unknown Unknown =
  Stack trace terminated abnormally. 031.OUT 031.CTL=
OUTPUT 1 file(s) copied. C:\Documents and Setting=
s\brian\Documents\OUTPUT The process cannot access the file because it=
 is being used by another process. C:\ > While the=
 file name may vary depending upon which file is being read/written a=
t any given time, these are the sorts of errors suggested by Mark. =
The number for the error (47 above and 157 in your case) may be compi=
ler specific (I?m running Intel Fortran 9.1). You may also have the =

 a network access violation may be the cause. Is there a file name =
associated with the error? Cheers? Brian From=
: owner-nmusers_at_globomaxnm.com [mailto:owner-nmusers_at_globomaxnm.com] =
On Behalf Of Mark Sale - Next Level Solutions Sent: Friday, Dece=
mber 07, 2007 7:44 AM To: Joachim.Grevel_at_merckserono.net Cc: =
nmusers_at_globomaxnm.com Subject: RE: [NMusers] error (157) forrtl: se=
vere Joachim, This is probably a file access =
error, from Fortan/OS, not from NONMEM. Does NMTRAN run? Does the =
compiler run? Does nmlink6 run (do you get link.lnk)? Do you get =
an executable? Does NONMEM start then stop? If you get the executabl=
e (nonmem.exe or fsubs.exe), then the error is with file access i=
n the NONMEM itself. Don't know which file, but if NMTRAN runs it i=
sn't the (NMTRAN) data set, still could be FDATA, FCON, FSTREAM, FRECORD, =
any of the FILE? (but probably not) or an MSF. Fortran should clos=
e all the files when it exits, by any method (e.g., if it crashes=
). Cou! ld conceivable be a library file from the compiler as wel=
l. Mark Mark Sale MD Next Level Solutions, LLC=
www.NextLevelSolns.com 919-846-9185 -------=
- Original Message -------- Subject: [NMusers] error (157) forrtl: sev=
ere From: Joachim.Grevel_at_merckserono.net Date: Fri, December =
07, 2007 6:19 am To: nmusers_at_globomaxnm.com A quest=
ion for FORTRAN experts: Fortran Error 157: access viol=
ation is the error we see when NONMEM crashes on our server ins=
tallation with models which otherwise run fine on our local PC instal=
lations of NONMEM. These crashes occur with very simple (ADVAN2) an=
d also with rather complicated (ADVAN5, ADVAN7) models. They can b=
e avoided when models are reformulated with ADVAN6 TOL=5. Of cou=
rse with ADVAN6 all models run slower and this is not really a soluti=
on of our problem. We run NONMEM VI without the recent bug fi=
xes in a "naked" fashion on the server, and with "wings" on the PCs=
. Our compiler is Compaq Visual Fortran (latest version). =
We appreciate your thoughts on that. __________________=
________________________ Joachim GREVEL, Ph.D. MERCK SERONO I=
nternational S.A. Exploratory Medicine 1202 Geneva Tel: =
+41.22.414.4751 Fax: +41.22.414.3059 Email: joachim=
.grevel_at_merckserono.net This message and any attachment are =
confidential, may be privileged or otherwise protected from disclosur=
e and are intended only for use by the addressee(s) named herein. I=
f you are not the intended recipient, you must not copy this message =
or attachment or disclose the contents to any other person. If you =
have received this transmission in error, please notify the sender im=
mediately and delete the message and any attachment from your system=
. Merck Serono does not accept liability for any omissions or errors =

r damages resulting from any unauthorized changes of the content of t=
his message and any atta! chment thereto. If verification is requir=
ed, please request a hard-cop y version. Merck Serono does not guar=
antee that this message is free of viruses and does not accept liabil=
ity for any damages caused by any virus transmitted therewith. =

This message and any attachment are confidential, may be privileged or ot=
herwise protected from disclosure and are intended only for use by the ad=
dressee(s) named herein. If you are not the intended recipient, you mus=
t not copy this message or attachment or disclose the contents to any oth=
er person. If you have received this transmission in error, please noti=
fy the sender immediately and delete the message and any attachment from =
your system. Merck Serono does not accept liability for any omissions o=
r errors in this message which may arise as a result of E-Mail-transmissi=
on or for damages resulting from any unauthorized changes of the content=

red, please request a hard-copy version. Merck Serono does not guarante=
e that this message is free of viruses and does not accept liability for =
any damages caused by any virus transmitted therewith.

Received on Fri Dec 07 2007 - 09:26:58 EST