Error Log entry Unable to write file with XML Saver

[Former Member]

Hi all,

I have just encountered the following problem. I am saving a XML file using the XML Saver. Another BLT reads the file, changes something, and saves it again with the same name.

The file is saved, but the NetWeaver SAP Log gives the error

"Unable to write file /usr/sap/<SID>/JC00/j2ee/cluster/server0/apps/sap.com/xapps_xmiiear/servlet_jsp/XMII/root/CM/<folder>/file.xml"

Is it a problem with the new storage mechanism in MII 12? Even if I delete the file first and then save it again with the same name, the error is displayed (though the file is saved).

Michael

[agentry_src · Accepted solution]

Michael,

If you execute the second transaction using Ctrl-F5 in the workbench, does the Save XML action block generate an error message in the execution window?

Mike

Edited by: Michael Appleby on Oct 24, 2008 5:17 PM

[Former Member · Accepted solution]

Hi Mike,

no, the Debug only says "Begin Action XML Saver" and "End Action XML Saver".

The action however writes the file, the contents has changed after the BLT has run.

Well, I have just tried the Text Saver with the same file (name and contents). It also gives the error. I now wanted to delete the folder. The folder disappered from the workbench view, and the Netweaver log says "Unable to process service message".

I then clicked "publish" on the parent folder and tried to create the folder again, but although the folder was not displayed, the workbench said "the folder already exists". When I start my BLT, it could write the file into the folder which then reappeared in the workbench.

Hm, maybe our installation has some problems? Feels like missing authorizations...

Michael

[agentry_src · Accepted solution]

Michael,

It sounds like the problem starts when it gets to the NW level. Or at least that is where the error handling is initiating. At this point, I don't know really where to point you, although I think I would agree with you about the permissions. But if it really were permissions, then why is the Save working.

Maybe restarting the NW instance will take care of the folder persistence. Outside of that, I am not sure what to suggest.

Good luck,

Mike

[Former Member · Accepted solution]

Mike,

I have solved the issue.

The problem was, that besides the folder a file existed with the same name as the folder. Don't ask me how this happened, but this seemed to be the reason why I could not re-create the folder and the message appeared.

After deleting the file with the folder name, I could re-create the folder and now the xml files can be stored without an error message.

Have a good start into the new week!

Michael