Originally posted by: SystemAdmin
As jmenning was saying...
The workfiles is where TX is going to write out the data so it can manipulate it when the map runs. If you can't write to the direcotry because of access issues, you'll get this error. Under workspace in map settings, you have "file", and probably "mapname" for the name of the files, so everytime it runs, it uses the same filenames. If one of the files is being held by another process, you'll get this error.
I used to get it with event server under Windows, when we accidently started the service when one was already running, and you'd see two instances under processes running in the task manager. One instance would kick off the map, then the second instance would also, and they were both trying to use the same workfiles.
Using all the info, just see what's up in the direcotry you're running on. You can always set workspace to memory, and not have the problem.
#DataExchange#IBM-Websphere-Transformation-Extender#IBMSterlingTransformationExtender