File Not Found Exception error

[st...@murrays.co.uk]

Hi, I am getting various errors when running the XML Printer in a windows 64bit, 2008r2 environment.

The error details from the printer logs are:

12/05/2012 12:34:31.873  dispatch

System.IO.FileNotFoundException: Could not load file or assembly 'ReachFramework, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.

File name: 'ReachFramework, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'

at #=qLy75MonA$eBc6w3rtpJ3G2l7_UDAfzz3HfXxPVZ$AKY=.#=quB4zByaJ$92at4GqGFFVcA==(String #=qdhavtmw8yX86XTPtkKZDVA==, String #=qbzkOIl3VCjKXz6iMj1n$eg==, #=qEgVV6wrqEsXlHfAzecp5jWg_vyKq6oOM4RsDK1lbRKc5mPhExGLhEDYlMyxkq_z8 #=q$nEjcW9kAHVKIx8jeRk1KA==)

at #=qc5peHk6c_uK1TDYqHPoJSTJdGCtfTVE1L031D6xCAXjyJT5rKsAESRPFd04qCLqE.#=qJIVKSk_CRcmKN0uD3rENXg==(HttpReqResp #=qOC_5garHdeec0JcEe650Jg==)

WRN: Assembly binding logging is turned OFF.

To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.

Note: There is some performance penalty associated with assembly bind failure logging.

To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

 

12/05/2012 12:34:31.869  dispatch Monitor finished writing into C:\ProgramData\XML Printer\69cceef9-a3ea-4765-b28b-20bcb2085e37.xps 

12/05/2012 12:34:31.766  monitor Writing to C:\ProgramData\XML Printer\69cceef9-a3ea-4765-b28b-20bcb2085e37.xps 

12/05/2012 12:34:31.564  monitor AxpStartDocPort full backing sheet laser.frx 

Is this a compatibility issue with the OS?

Regards

-- 

Steve

[st...@murrays.co.uk]

An different error occurs when I change the processing to 'Save As' 

System.Runtime.InteropServices.COMException (0x80040154): Retrieving the COM class factory for component with CLSID {E1C5D730-7E97-4D8A-9E42-BBAE87C2059F} failed due to the following error: 80040154.

at #=qc5peHk6c_uK1TDYqHPoJSTJdGCtfTVE1L031D6xCAXjyJT5rKsAESRPFd04qCLqE.#=qMXVpmdKNJQB7q2B8_q8xNw==(HttpReqResp #=qQcpPvI8QU4YCJXddLFAXcA==)

[Tomas]

Hi Steve,

The second problem seems to be related to scanning and should appear in normal XML Printer usage (unless you use XML Scanner).

We've tested XML Printer with Windows 2008 and didn't come across any issues yet.

Tomas.