I've got a fex that builds a simple html phone list for our company. We had it up and running for months before we upgraded to 7.6.2 in July.

Now we're getting...
0 ERROR AT OR NEAR LINE 97 IN PROCEDURE rpt_phone_list
(FOC350) ERROR WRITING OUTPUT FILE: JK

The fex is very simple...
FILEDEF JK DISK \\SVR99MAIL\PHONE\PAGE.HTM
*focus code*
ON TABLE HOLD AS JK FORMAT HTML
*stylesheet code*

We've checked and double check the permissions on this SVR99MAIL server, but we're missing something.

Anyone seen this before? I didn't see anything in focal point that was useful, so it's either really really simple or really complex.

I'm in a Unix shop and whenever I see that message, it is because

a. the file now belongs to someone else and the person who is trying to write it is not allowed.
b. the person trying to write it in Dev Studio is not who he thinks he is, i.e. the cookie got messed up.

You were right to look at permissions. The only other thing I can think of is space issues.

Well, the system's admin and I are having a hard time of all this.

Does anyone know where we can find the user the IBI is using to create a file listed in a filedef so we can grant that user the appropriate permissions?

-SET &USERID=GETUSER('A8');
-TYPE THE USERID FROM GETUSER IS &USERID
  

That is if you are using a secured reporting server.

say Jason
does your file get written if you
TABLE FILE CAR
PRINT *
ON TABLE....
END
?
If so, its not the filedeffing and writing, its something whacky in your phone number data, perhaps. Check that sort of thing first.

Or just do a -WRITE to the filedef after the filedef has been registered.
So:
FILEDEF JK DISK .....
-RUN
-WRITE JK Something

Maybe you'll find what's wrong in this way.
By the way, if you're running non-secure, the user the server runs under is the local system account. And that account only has full rights on the local machine and will not be allowed to write on other servers, regardless of the security level of that other server.
If that's the case it may be advisable to run the server as a secure (EDAEXTSEC=ON) or pass through (EDAEXTSEC=PTH) server.

Jason has your report changed to using Amperautoprompt?

GamP: I think you're on to something with your suggestion. I think we are running non-secure. Is there any way to make this work with the non-secure setup that we have?

All: we are able to create the file on local drives, c: for example, but not on any other server, either through the UNC path or through mapping the drive on the reporting server first.

Thanks!