Re: Error 52 Bad File

Greg Boehnlein ( )
Thu, 6 Mar 1997 18:29:47 -0500 (EST)

On Thu, 6 Mar 1997, Jeff Woods wrote:

> At 10:41 AM 3/6/97 -0500, you wrote:
> >> >Emerald error 52: Bad File Name or Number
> >I've seen this when the file-system that you are exporting the information
> >to is not mounted, or that the file your are trying to write to is Write
> >Protected or something silly like that.
> No such beast -- it's a LOCAL hard drive, Win95.
> >In our environment, we mount a UNIX machine via Samba, and if the user
> >isn't logged into that resource, Emerald complains about it. Mounting that
> >particular drive where the file is located solves the problem.
> What drive are you talking about here? The Temp directory? Which
> location is it "exporting" to, if not the local temp directory?

You'll need to configure, in Emerald Administrator, the following. (This
assumes Emerald 2.0.88 and the latest Emeradmin)

1. Under the "Config Database" option, select the "External Systems" tab.
2. Select the specific system that you are exporting to (In my case, I've
defined one as "Linux Shell/Mail Server".
3. Make sure that you have "Standard / Export" type configured.
4. Leave EVERYTHING else blank except for the last two fields
- WorkDir is actually mislabled, and should be called "export
file" or something similar. Put "c:\emerald.export" in this
field and it will write all exports to that file.
- Logfile is a file that logs the changes and export times
I believe, and should be configured as something like

That should help you out. This was a weird one for us, but Dale pointed
out the "quirks" in the naming convention and it fixed it right up.

--      President of New Age Consulting Service, Inc.  Cleveland Ohio             SLIP/PPP/Unix Shell   28.8k / ISDN / Leased Line    (216)-524-8414