Hello,
I'm using FM0 writer on FME desktop and everything works fine.
When I try to run the same workspace on FME Server I get exception: Caught a COM Exception in FM0Writer::open()
Im writing file to nas share.
\\\\naslocation\\test.fm0
but when I would write it to zipped location:
\\\\naslocation\\test.zip\\test.fm0
then it works fine.
What can be the reason for that?
+19Hi @witos,
FME uses Geomedia to create the .fm0 file. It may be that the process calling Geomedia does not have write permission on the share drive. When writing to the zip, FME writes the .fm0 file to a local temp folder first, then a different process creates the zip file on the share drive.
Nobody has reported this issue before, so it may be particular to your setup. You may need to give the system user on the FME Server computer full read/write access to the share drive.
Hi @DaveAtSafe
Thanks for the clue.
I think that geomedia (fm0 writer) writes to mdb file (ms access) and for some reason it fails after writing 256 KB. I can see that on the share always no matter how big file should be, there is first part of it written (256 KB) and then in logs I have:
IDispatch error #3221
The database has been placed in a state by an unknown user that prevents it from being opened or locked.
GDatabase::OpenDatabase
And then:
Caught a COM Exception in FM0Writer::open()
Caught a COM Exception in FM0Writer::open()
Destination Feature Type Routing Correlator(RoutingFactory): Caught a COM Exception in FM0Writer::open()
Caught a COM Exception in FM0Writer::open()
|ERROR |
A fatal error has occurred. Check the logfile above for details
+19Hi @DaveAtSafe
Thanks for the clue.
I think that geomedia (fm0 writer) writes to mdb file (ms access) and for some reason it fails after writing 256 KB. I can see that on the share always no matter how big file should be, there is first part of it written (256 KB) and then in logs I have:
IDispatch error #3221
The database has been placed in a state by an unknown user that prevents it from being opened or locked.
GDatabase::OpenDatabase
And then:
Caught a COM Exception in FM0Writer::open()
Caught a COM Exception in FM0Writer::open()
Destination Feature Type Routing Correlator(RoutingFactory): Caught a COM Exception in FM0Writer::open()
Caught a COM Exception in FM0Writer::open()
|ERROR |
A fatal error has occurred. Check the logfile above for details
Hi @witos,
If you create a new MDB warehouse on the share drive in Geomedia, can you write to it with FME (with Overwrite Existing Database set to No)?
Hi @DaveAtSafe
Thanks for the clue.
I think that geomedia (fm0 writer) writes to mdb file (ms access) and for some reason it fails after writing 256 KB. I can see that on the share always no matter how big file should be, there is first part of it written (256 KB) and then in logs I have:
IDispatch error #3221
The database has been placed in a state by an unknown user that prevents it from being opened or locked.
GDatabase::OpenDatabase
And then:
Caught a COM Exception in FM0Writer::open()
Caught a COM Exception in FM0Writer::open()
Destination Feature Type Routing Correlator(RoutingFactory): Caught a COM Exception in FM0Writer::open()
Caught a COM Exception in FM0Writer::open()
|ERROR |
A fatal error has occurred. Check the logfile above for details
I created new empty dataWarhouse on share using geomedia. I tried to use fme to write data there with overwrite existing database set to no, and unfortunately the result is the same as before. The same error.
+19I created new empty dataWarhouse on share using geomedia. I tried to use fme to write data there with overwrite existing database set to no, and unfortunately the result is the same as before. The same error.
Hi @witos,
I think this might be better handled as a support case. Please report a problem at https://www.safe.com/support/report-a-problem/, and I will pick up the case.
I'm sorry to make you describe the problem again, but I have no access to your email on this platform.
Hi @witos,
I think this might be better handled as a support case. Please report a problem at https://www.safe.com/support/report-a-problem/, and I will pick up the case.
I'm sorry to make you describe the problem again, but I have no access to your email on this platform.
Hi @DaveAtSafe
Thanks, I created the support case.
