Failed to save report

irshanuddin · Post by **irshanuddin** » Thu Aug 01, 2013 9:01 am

Just setup IA and ran column analysis.
Tried to create a report and got this error:
com.ascential.acs.reporting.ReportingEngineException: /tmp/informationServer/Reporting(ServerName)Node01server1/engine/JREPORT/realm/defaultRealm/dhtmlPreference.properties (No such file or directory)

Checked the web server and there is a folder called JREPORT in this location, except the only folder under that is called temp.
Tried restarting WebSphere as suggested by IBM support site, but still no luck.
Any suggestions/advice are welcome.

Thanks

kjanes · Post by **kjanes** » Thu Aug 01, 2013 2:51 pm

I had this same error on v9.1 on RHEL 5.6 64 bit. I created the rest of the folders in the path and made sure the correct owner and permissions were set. I then restarted WebSphere and the initial message like you have is gone. I have a new message: ; nested exception is: com.ascential.acs.reporting.ReportingException: Following parameter has no value or has an invalid value(null/empty): [CDV_DomAD.parameter.dataCollection.displayName].

rjdickson · Post by **rjdickson** » Thu Aug 01, 2013 3:19 pm

This should go away if you:

1) Stop WAS
2) While WAS is stopped, delete /tmp/informationServer
3) Restart WAS

kjanes · Post by **kjanes** » Fri Aug 02, 2013 9:07 am

1) close Info Server Client
2) ./uv -admin -stop
3) ./stopServer.sh server1
4) cd /tmp
5) rm -R -f informationServer
6) ./startServer.sh server1
7) ./uv -admin -start
8 ) open info server client and rerun report

Unfortunately, this process did not resolve the problem.

irshanuddin · Post by **irshanuddin** » Fri Aug 02, 2013 9:22 am

Kevin,

You mention restarting Information Server and not Websphere Server.
Have you tried that yet?

Unix :
cd WAS_home/bin
./stopServer.sh server_name [options]
./startServer.sh server_name

refer to :
http://www-01.ibm.com/support/docview.w ... wg21497966

kjanes · Post by **kjanes** » Fri Aug 02, 2013 9:59 am

Yes, I did stop and restart WebSphere in the steps I laid out. Since DataStage/Info Server is dependent on WAS I stopped DataStage/Info Server first doing ./uv -admin -stop. I then stopped WAS using ./stopServer.sh server1. Once WAS was stopped, I deleted the files and folders recursively in /tmp/informationServer. I then started WAS back up using ./startServer.sh server1 and then started Info Server / DataStage back up using ./uv -admin -start.

Thanks,
Kevin

irshanuddin · Post by **irshanuddin** » Fri Aug 02, 2013 10:07 am

Same here. Stopped and restarted WAS several times and Info Server too.
I remember this worked for me back when we upgraded to 8.1.
No dice here on 8.5.
Any other ideas?

rjdickson · Post by **rjdickson** » Fri Aug 02, 2013 10:11 am

Hi Kevin,

I wonder if restarting the ASBAgent would help?

Who owns process server1 when you do a ps -ef | grep server1? Does that same id also own the /tmp/informationServer directory? Does that same id also own the /opt/IBM/InformationServer/ASBServer/* directory?

kjanes · Post by **kjanes** » Fri Aug 02, 2013 10:13 am

I went to /tmp/informationServer directory and had noticed it was owned by root. when this structure is created, it was assigned the owner of root. I saw this yesterday and changed owner to dsadm thinking it might help. It did not.

****Resolution*****
Having second thoughts today, I changed the owner of the /tmp/informationServer directory and all objects under it to wasadmin and the report ran.

rjdickson · Post by **rjdickson** » Fri Aug 02, 2013 10:15 am

Ah ha! I suspect that WAS is running as wasadmin. Can you please confirm or deny?

kjanes · Post by **kjanes** » Fri Aug 02, 2013 10:21 am

WAS is running under the wasadmin ID. That is correct. Not sure why that folder is created with owner root. If it is deleted and you restart WAS, the folders get recreated with the owner root. Is this a bug?

rjdickson · Post by **rjdickson** » Fri Aug 02, 2013 10:24 am

I suspect so. The workaround appears to be to either not delete the directory, or to recreate as owned by the same id that is running was

kjanes · Post by **kjanes** » Fri Aug 02, 2013 10:36 am

If the owner and user running the process do not match, it appears to be an issue. If the folder is there and owned by root or some other user other than the user running WAS, one could just recursively change the permissions throughout /tmp/informationServer.

Once in the /tmp directory, all I did was chown -R -f wasadmin informationServer.

The report ran after that.

irshanuddin · Post by **irshanuddin** » Tue Aug 06, 2013 9:41 am

I just came back from being out a few days, and saw this resolution.
I tried to log in as wasadmin and it didnt work. Found out wasadmin was never set up as a user on the websphere server ( we have a 3-tier setup).
Having an account created now, but hopefully this still holds true for me.
Thanks to everyone who coordinated to get a result.

DSXchange

Failed to save report

Failed to save report

Re: Failed to save report

Re: Failed to save report