This content has been marked as final. Show 6 replies
I think you have started as Windows service and this is a 11g IBR server .
This is not the refinery's or Weblogic's fault. It's an issue with the operating system. Windows 2008 does not allow a service access to the print services. Conversions that utilize the native Office applications require access to the printer. Since the OS does not allow access to the printer, the conversions will not work.
You will have to start IBR from command line and then input the documents for successful conversion .
Hope this helps .
I started IBR using node manager and now I am getting the following error...
Log entry for conversion job '44':
Step MSOfficeToPostscript forced conversion failure by conversion engine because of error: Unable to convert. Native application reported: 'Object variable or With block variable not set.' Exception type is 'java.lang.Throwable'. [ Details ]
An error has occurred. The stack trace below shows more information.
!csLogJobIdPrefix,44!csLinefeed!csConversionForceFailureByStep,MSOfficeToPostscript,\!csNativeGeneralError\,Object variable or With block variable not set.!csNativeGeneralError,Object variable or With block variable not set.!syExceptionType,java.lang.Throwable
Hi Bunty ,
Is Node Manager running as Windows Service ? I assume that to be the case and that too creates this issue .
This is due to an OS "limitation;" the win2008 OS does not allow a service access to the print services. Conversion that utilize the native apps require access to the printer. Since the OS does not allow access to the printer, this conversion will not work.
Start Node Manager from command line of Windows and then start IBR server , submit contents and see if conversion works fine .
yeah, that was the case. But in our dev and prod environments, NodeManager and Admin server are running as windows service (on widows server 2008) and there are no conversion issues .
Trying to figure out the differences in dev and new environment and if successful, will udpate it here for others.
Hi Bunty ,
The aspects which can create this issue is bit version of the OS where it is deployed / running , user which has installed the managedservers and the user permission that is running the services . Check if the services are running with LocalAccount permission on the working envt or not .
have you been able to fix this issue? I'm facing the same right now...