COM error in faxing component
-
I am having an issue with a Fax component. It works when installed on a WinXP machine, but has an exception on Server 2003. Here is my exception: The COM class factory for component with CLSID {D73733C8-CC80-11D0-B225-00C04FB6C2F5} failed due to the following error: 80040154. I found a couple of articles stating that this is a problem seen in 64-bit operating systems. I have personally confirmed that neither system is 64-bit, yet the problem persists (no exception in XP, exception in server 2003). This is my first time using FAXCOMLib, so if I am making some rookie mistake please let me know. Thank you! Here is the section of code that is failing: FAXCOMLib.FaxServer faxServer = new FAXCOMLib.FaxServerClass(); faxServer.Connect(Environment.MachineName); FAXCOMLib.FaxDoc faxDoc = (FAXCOMLib.FaxDoc)faxServer.CreateDocument(file.FullName); faxDoc.RecipientName = recipientName; faxDoc.FaxNumber = faxNumber; faxDoc.DisplayName = displayName; faxDoc.Send(); faxServer.Disconnect();
-
I am having an issue with a Fax component. It works when installed on a WinXP machine, but has an exception on Server 2003. Here is my exception: The COM class factory for component with CLSID {D73733C8-CC80-11D0-B225-00C04FB6C2F5} failed due to the following error: 80040154. I found a couple of articles stating that this is a problem seen in 64-bit operating systems. I have personally confirmed that neither system is 64-bit, yet the problem persists (no exception in XP, exception in server 2003). This is my first time using FAXCOMLib, so if I am making some rookie mistake please let me know. Thank you! Here is the section of code that is failing: FAXCOMLib.FaxServer faxServer = new FAXCOMLib.FaxServerClass(); faxServer.Connect(Environment.MachineName); FAXCOMLib.FaxDoc faxDoc = (FAXCOMLib.FaxDoc)faxServer.CreateDocument(file.FullName); faxDoc.RecipientName = recipientName; faxDoc.FaxNumber = faxNumber; faxDoc.DisplayName = displayName; faxDoc.Send(); faxServer.Disconnect();
It should be easy to fix it: It means that your module is not registered, so you have certainly copied the library to your target system without registring it. * regsvr32 xxxx.dll if you have an error use a tool to check if a missing dependency is not missing (dependency [^] Keep update us.
-
I am having an issue with a Fax component. It works when installed on a WinXP machine, but has an exception on Server 2003. Here is my exception: The COM class factory for component with CLSID {D73733C8-CC80-11D0-B225-00C04FB6C2F5} failed due to the following error: 80040154. I found a couple of articles stating that this is a problem seen in 64-bit operating systems. I have personally confirmed that neither system is 64-bit, yet the problem persists (no exception in XP, exception in server 2003). This is my first time using FAXCOMLib, so if I am making some rookie mistake please let me know. Thank you! Here is the section of code that is failing: FAXCOMLib.FaxServer faxServer = new FAXCOMLib.FaxServerClass(); faxServer.Connect(Environment.MachineName); FAXCOMLib.FaxDoc faxDoc = (FAXCOMLib.FaxDoc)faxServer.CreateDocument(file.FullName); faxDoc.RecipientName = recipientName; faxDoc.FaxNumber = faxNumber; faxDoc.DisplayName = displayName; faxDoc.Send(); faxServer.Disconnect();
OK, the COM problem is fixed - the Windows Fax service was not configured on the account the prog is using. (Apparently Windows fax must be configured for each account?) However, a different exception is being thrown by the same code block: Access is denied. (Exception from HRESULT: 0x8007005 (E_ACCESSDENIED)) So apparently, it has permissions issues in reaching the Fax service...
-
OK, the COM problem is fixed - the Windows Fax service was not configured on the account the prog is using. (Apparently Windows fax must be configured for each account?) However, a different exception is being thrown by the same code block: Access is denied. (Exception from HRESULT: 0x8007005 (E_ACCESSDENIED)) So apparently, it has permissions issues in reaching the Fax service...
The difference maybe in UAC control which may prevent to load the DLL or to access a specific resource. Look at this policy explainations for more details: http://www.15seconds.com/Issue/040121.htm[^] Because, remotely it will be difficult to find any potential security reasons. Depending on the installation and the way you have installed your software. :suss: Good luck. Keep us updated.