ReportSDKException: Unexpected error determining relative path---- Error code:-2147217395 Error code

com.crystaldecisions.sdk.occa.report.lib.ReportSDKException: Unexpected error determining relative path---- Error code:-2147217395 Error code name:serverProgrammingError

at com.businessobjects.reports.sdk.d.byte(Unknown Source)

at com.businessobjects.reports.sdk.JRCCommunicationAdapter.a(Unknown Source)

at com.businessobjects.reports.sdk.JRCCommunicationAdapter.void(Unknown Source)

at com.businessobjects.reports.sdk.JRCCommunicationAdapter.connect(Unknown Source)

at com.crystaldecisions.proxy.remoteagent.y.a(Unknown Source)

Cause:

For the JRC XI Release 1 and higher, the reportLocation tag value you'd place in CRConfig.xml is relative to the location of CrystalReportEngine.jar file. You'd get that error if the app can't walk up the path from the jar file location to where it expects to find the rpt files.

Solution:

Make sure you've placed CrystalReportEngine.jar & all aother supporting jars in applications WEB-INF/lib.

List of jar files in my lib folder:

commons-discovery.jar
commons-logging.jar
Concurrent.jar
corbaidl.jar
CRDB_JavaServer.ini
CRDBJavabeansServer.jar
CRDBJavaServer.jar
CRDBJavaServerCommon.jar
CRDBJDBCServer.jar
CRDBXMLExternal.jar
CRDBXMLServer.jar
crlov.jar
crlovexternal.jar
crlovmanifest.jar
CrystalCharting.jar
CrystalCommon.jar
CrystalContentModels.jar
CrystalDatabaseConnectors.jar
CrystalExporters.jar
CrystalExportingBase.jar
CrystalFormulas.jar
CrystalQueryEngine.jar
CrystalReportEngine.jar
CrystalReportingCommon.jar
ebus405.jar
freessl201.jar
icu4j.jar
jaxrpc.jar
jrcerom.jar
jsafe.jar
keycodeDecoder.jar
log4j.jar
mergeboar.jar
MetafileRenderer.jar
pullparser.jar
rasapp.jar
rascore.jar
rpoifs.jar
saaj.jar
serialization.jar
sslj.jar
u211java.jar
URIUtil.jar
webreporting.jar
webreporting-jsf.jar
wsdl4j.jar
xbean.jar
xercesImpl.jar
xml-apis.jar
asn1.jar
axis.jar
axis-ant.jar
cecore.jar
celib.jar
ceplugins.jar
cereports.jar
certj.jar
cesession.jar
ceutils.jar
cexsd.jar
clientSDKOptions.xml

J2CA0045E: Connection not available while invoking method createOrWaitForConnection for resource

The error "J2CA0045E: Connection not available while invoking method createOrWaitForConnection for resource jdbc/DEMO." can be caused by many problems.

        They are showing a time-out condition where a resource or a managed connection is not available to fulfill a connection request.

        Probably you might have many connections or long running transactions to process.

        Action Plan:

        1. Increase the "Maximum connections" from 10 to 30. This is likely to help fix this issue.

        To ask your question:

        You can check the current active connection when the ConnectionWaitTimeoutException happened by dumping java threads or javacores.

        The following document will guide you to collect requested information. Please use manual collection steps.

        [Please follow through the section "Manual collection of troubleshooting data (optional)"]

        MustGather: Performance, Hang, or High CPU Issues on Windows

        - http://www-01.ibm.com/support/docview.wss?uid=swg21111364

       

        Recommendation:

        1. It is recommended to test the scripts which is attached the above document first or before the problem occurred to ensure it does work in your environment.

        2. Could you please check the database side? Has database provided enough cursors or connections to serve requests?

            Is (Are) there any lock in database table?

        3. Please check with your program coding side. Does it close connection(s) to database when it finished the task or transaction?

More Info:

http://www-01.ibm.com/support/docview.wss?uid=swg21217062

Similar Prob:

http://forums.sun.com/thread.jspa?threadID=5387319

IE8 RTM cann't print preview checked checkbox

IE8 has a new bug with printing. When you change a checkbox or radio button on a page either by clicking it or calling some JavaScript function to toggle it - it looks like it changed but if you try to print it, it won't print in the new state.

In fact it won't even show up correctly in the print preview window!

The best part is that this ONLY occurs in Standards Mode. If you render your pages in the Legacy IE7 Mode the checkboxes and radio buttons print (and preview) properly.

https://connect.microsoft.com/IE/feedback/ViewFeedback.aspx?FeedbackID=431489

https://connect.microsoft.com/IE/feedback/ViewFeedback.aspx?FeedbackID=434706

Parsing error processing resource path /WEB-INF/struts-config.xml

ERROR [http8080-Processor1] action.ActionServlet (ActionServlet.java:768) - Parsing error processing resource path /WEB-INF/struts-config.xml

java.lang.reflect.InvocationTargetException

at org.apache.commons.digester.Digester.createSAXException(Digester.java:2792)

at org.apache.commons.digester.Digester.createSAXException(Digester.java:2818)

at org.apache.commons.digester.Digester.startElement(Digester.java:1289)

at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)

at org.apache.xerces.parsers.AbstractXMLDocumentParser.emptyElement(Unknown Source)

at org.apache.xerces.impl.dtd.XMLDTDValidator.emptyElement(Unknown Source)

at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)

at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)

at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)

at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)

at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)

at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)

at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)

at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)

Possible causes:

1. version problem of the JDKs. Check the version of xerces.jar.

2. different Java (JRE) versions on the two machines (the developer-machine had 1.6 and the target-machine only 1.5)

Solution:

1.make sure the very first line in config or web.xml should not be blank. The contents should start with the very first line.

2. Compile project with JRE version equals to target-machine.

HTTP Server Error Message 'make_sock could not bind to address'

Error Message:

Only one usage of each socket address is normally permitted.  : make_sock could not bind to address 0.0.0.0:80 no listening sockets available, shutting down

Unable to open logs

Problem:

Port 80 is listening by some process.

Solution:

Find which one uses the 0.0.0.0:80 port. Just stop it and keep it free. Then start up apache.

1) 'netstat -noa' will give you the PID of the process that reserves your precious port.

2) 'Ctrl-Alt-Del' and your Windows task manager, if you choose View >Select Colums and check PID, will show you which PID is stealing your port. Stop it.

3) Start HTTP server