G
Guest
Hi there. I am experiencing an error in the Application log of the Event
Viewer when sending an outgoing fax from our Windows 2003 server. The fax
does not attempt to be delivered. The error details are as follows:
--------------------------
Source: Microsoft Fax
Category: Outbound
Type: Error
Event ID: 32090
User: N/A
The fax was not submitted successfully.
The following error occurred: 1801.
This error code indicates the cause of the error.
Sender Machine Name: \\SERVERB.
Sender User Name: joeadmin.
Sender Name: Joe Smith.
Number of Recipients: 1.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
-------------------------------------
This server is a lone Domain Controller in a single domain, which is running
the "FAX" service. There were some previous issues with running the "FAX"
service on a Domain Controller, but I applied the fix from Q842207 and it
resolved the old issue. Now we need to resolve the Event ID 32090 issue for
outgoing faxes. FYI, we can successfully receive faxes with no issues.
Also, we can dial out with the modem using Hyperterminal with no issues
either.
Some stats on the server:
Windows Server 2003 (with SP1)
Fax Modem: US Robotics External 56K Faxmodem V.92
1 GB of Memory (400 MB of RAM available)
20 GB of free disk space.
The "FAX" service is running under the "NT AUTHORITY\NetworkService"
account. My suspicion was that the "NT AUTHORITY\NetworkService" account was
creating a problem. So what I did is add the "NT AUTHORITY\NetworkService"
account to the Administrators group of the Domain Controller. I then
restarted the "FAX" service and retried to send a fax. The fax was sent
successfully and there were no errors in the Event Viewer.
I then removed the "NT AUTHORITY\NetworkService" account from the
Adminstrators group and restarted the "FAX" service and I then received the
same 32090 error in the Application log of the Event Viewer. Therefore, it
would be safe to say that there is a permissions limitation for the "NT
AUTHORITY\NetworkService" account at either the file, registry or component
level.
Some troubleshooting that I have attempted:
- Applied Windows 2003 Service Pack 1. It did not resolve the error. FYI,
the 32090 error appeared before applying SP1.
- Monitored the registry and noticed that the FAX service is always
attempting to create a key in HKLM\Software\Microsoft\Tracing\TAPI32. I
noticed that the "NT AUTHORITY\NetworkService" account did not have
permissions to this key. I granted full access permissions for the "NT
AUTHORITY\NetworkService" account to the
HKLM\Software\Microsoft\Tracing\TAPI32 key and then restarted the "FAX"
service. The error was still there and the fax would not send out.
- I have enabled "Event Report Logging" as HIGH for everything within the
FAX (local) Properties. There was no additional information provided once
the 32090 error appeared during a failed outbound fax attempt.
I am quite certain that the culprit here is the permissions limitation of
the "NT AUTHORITY\NetworkService" account. However I don't know where the
limitation is. Hopefully someone out there can offer some advice to
troubleshoot this.
Viewer when sending an outgoing fax from our Windows 2003 server. The fax
does not attempt to be delivered. The error details are as follows:
--------------------------
Source: Microsoft Fax
Category: Outbound
Type: Error
Event ID: 32090
User: N/A
The fax was not submitted successfully.
The following error occurred: 1801.
This error code indicates the cause of the error.
Sender Machine Name: \\SERVERB.
Sender User Name: joeadmin.
Sender Name: Joe Smith.
Number of Recipients: 1.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
-------------------------------------
This server is a lone Domain Controller in a single domain, which is running
the "FAX" service. There were some previous issues with running the "FAX"
service on a Domain Controller, but I applied the fix from Q842207 and it
resolved the old issue. Now we need to resolve the Event ID 32090 issue for
outgoing faxes. FYI, we can successfully receive faxes with no issues.
Also, we can dial out with the modem using Hyperterminal with no issues
either.
Some stats on the server:
Windows Server 2003 (with SP1)
Fax Modem: US Robotics External 56K Faxmodem V.92
1 GB of Memory (400 MB of RAM available)
20 GB of free disk space.
The "FAX" service is running under the "NT AUTHORITY\NetworkService"
account. My suspicion was that the "NT AUTHORITY\NetworkService" account was
creating a problem. So what I did is add the "NT AUTHORITY\NetworkService"
account to the Administrators group of the Domain Controller. I then
restarted the "FAX" service and retried to send a fax. The fax was sent
successfully and there were no errors in the Event Viewer.
I then removed the "NT AUTHORITY\NetworkService" account from the
Adminstrators group and restarted the "FAX" service and I then received the
same 32090 error in the Application log of the Event Viewer. Therefore, it
would be safe to say that there is a permissions limitation for the "NT
AUTHORITY\NetworkService" account at either the file, registry or component
level.
Some troubleshooting that I have attempted:
- Applied Windows 2003 Service Pack 1. It did not resolve the error. FYI,
the 32090 error appeared before applying SP1.
- Monitored the registry and noticed that the FAX service is always
attempting to create a key in HKLM\Software\Microsoft\Tracing\TAPI32. I
noticed that the "NT AUTHORITY\NetworkService" account did not have
permissions to this key. I granted full access permissions for the "NT
AUTHORITY\NetworkService" account to the
HKLM\Software\Microsoft\Tracing\TAPI32 key and then restarted the "FAX"
service. The error was still there and the fax would not send out.
- I have enabled "Event Report Logging" as HIGH for everything within the
FAX (local) Properties. There was no additional information provided once
the 32090 error appeared during a failed outbound fax attempt.
I am quite certain that the culprit here is the permissions limitation of
the "NT AUTHORITY\NetworkService" account. However I don't know where the
limitation is. Hopefully someone out there can offer some advice to
troubleshoot this.
