Failed to save report
-
- Participant
- Posts: 44
- Joined: Wed May 27, 2009 3:01 pm
Failed to save report
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
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
Re: Failed to save report
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].
Kevin Janes
Re: Failed to save report
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.
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.
Kevin Janes
-
- Participant
- Posts: 44
- Joined: Wed May 27, 2009 3:01 pm
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
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
Irshan S.
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
Thanks,
Kevin
Kevin Janes
-
- Participant
- Posts: 44
- Joined: Wed May 27, 2009 3:01 pm
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.
****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.
Kevin Janes
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.
Once in the /tmp directory, all I did was chown -R -f wasadmin informationServer.
The report ran after that.
Kevin Janes
-
- Participant
- Posts: 44
- Joined: Wed May 27, 2009 3:01 pm
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.
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.