FAXCOMLib really sucks on Windows 2003, but it works on Windows 2000. WHY???
- From: "Red Eagle" <andreabilli@xxxxxxxxxxxxxxxxxxx>
- Date: 16 Jan 2007 07:18:29 -0800
Well, dear developers, here it is a tough question for you all !! Let's
see what you can do...
Have you ever tried to use the mighty FAXCOMLib on Windows 2003 to send
a fax and get its status? No? Well, you are LUCKY! Because these lines
of code works PERFECTLY on a Windows 2000 Server machine (my great and
old Windows 2000 server!!!)...
faxJob = (FAXCOMLib.FaxJob)faxJobs.get_Item(iFaxJobNumber);
try
{
if (Environment.OSVersion.Platform.ToString().ToLower() == "win32nt")
faxJob.Refresh();
}
catch (Exception ex)
{
Misc.LogException(ex, "Symmetry");
}
string sDeviceStatus = faxJob.DeviceStatus.ToUpper();
string sQueueStatus = faxJob.QueueStatus.ToUpper();
int iFaxPages = faxJob.PageCount;
....BUT on any brand new Windows 2003 Server it throws an exception when
the faxJab.Refresh() method is called. Guess what? Windows 2003 says
"Parameter is incorrect"... WHAT THE HELL?!?!?
This really sucks, because the faxcomlib is the easiest way to send a
fax from a stand-alone .net application and it's a shame that it's not
correctly supported. Any idea on how to get the DeviceStatus of a job
working under the wings on Win2003?
Thank you very much! :-)
.
- Prev by Date: Re: w2k3 standart server fax routing
- Previous by thread: Re: w2k3 standart server fax routing
- Index(es):
Relevant Pages
|
