Good morning everyone,

I'm having a problem with a program I've developed for our customers. Our customers run a mix of Windows 2003 Server and Windows 2008 Server. The Windows 2008 Server sites are having no problems with this new program.

The program takes a PDF and faxes it using the FAXCOMEXLib component. The program I've written is in VB.Net. When I try to send a fax on a 2003 server I get the following error:

Error number: D, Unable to cast COM object type 'FAXCOMEXLib.FaxServerClass' to interface type 'FAXCOMEXLib.IFaxServer2'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{571CED0F-5609-4F40-9176-547E3A72CA7C}' failed due to the following error: No such interface supported (Exception from HRESULT: 0x80004002 (E_NOINTERFACE)).

I've tried different versions of the FXCOMEX.dll file to create the Interop file but it seems to be wrapping the dll from the system32 folder instead.

I've Googled this for days and have found various posts on this problem, but no clear work around.

Anyone have any ideas that might help?
Thanks
Gregg

Sorry, I have no idea. Microsoft seems to keep changing the fax-related modules from one version of Windows to the next, and it seems that your VB.Net program is indirectly dependent on a newer version.

Out of curiosity, I'm wondering what motivated writing an external fax routine rather than using the A-Shell / AlphaFax implementation. (Not that I'm sure if it works in W2003 - my test server has no modem to test with - but it would seem like a simpler approach.)

Strangely enough, the solution was found in an older version of Windows.

I got ahold of an XP system and loaded my development environment on it. XP is more related to Server 2003 than the Windows 7 box I typically work on. I simply compiled by code on the XP box and it works on 2003 and 2008 servers. I have to be honest, I didn't figure this out by myself. I found a reference to this solution on-line and thought I'd give it a try.

As far as an AlphaFax implementation, I'm not familiar enough with that to try. I was in a time crunch and went with what I thought I could figure out.

Thanks very much!

I'll add my two cents worth. Gregg and I were working on this together and, as Gregg said, we were uder a time crunch. It actually came down to the fact that he could layout the screen much faster than I could, thus the method we used. Also, I do use the fax function from within A-Shell by spooling to "FAX". It works on all our systems without fail. I know this includes server 2003 and 2008. We may go back and change the above fax to use A-Shell if we get time. That way the monkey would be on your back :rolleyes:

I should have said layout of the fax/printout above.

Note 1: the Fax-via-GDI approach uses the same layout logic as any other GDI printout, so if you are already familiar with that approach, faxing should be virtually the same as any other printing.

Note 2: you can correct your own posts directly by just clicking on the little icon that looks like a pencil and paper.

I do the faxing with the GDI approach. I'm just slow. On #2, I was afraid it was such a small change that you might wonder what I had changed

That actually made no sense. I think I'll stop now.