RE: Event 32090 when Faxing To Multiple Recipients



Hi Scorbet,

Thanks for posting in our newsgroup.

I am sorry for the delayed response due to weekend.

From the description, I know that with you try to send fax to multiple
recipients, you get the following message:

The fax was not submitted successfully.

The following error occurred: 4.
This error code indicates the cause of the error.

Sender Machine Name: \\SBSERVER.
Sender User Name: administrator.
Sender Name: Administrator.
Number of Recipients: 5.

If I am off base, please let me know.

I noticed you have tried every steps in our Engineer Nathan' s post, but
the problem persists. At this post, the problem may be more complex and
time consuming. Thanks for your understanding and patience.

Please let me know the following to make the situation more clearly:

1. Do all users or some specific ones have the problem?
2. What important change did you make before the problem first occurred?

First, I'd like to double confirm you have done the following:

Step 1: First at all, please make sure your fax modom is on the (Hardware
Compatibility List) HCL. If not, we can't guarantee its functionality on
Windows Server 2003.

To check the HCL, visit the following Microsoft Web site:
http://www.microsoft.com/windows/catalog/server/

Step 2: Please check the Group Policy on SBS Server:

1. On the SBS Server, click Start -> Run, type GPMC.MSC and click OK.

2. Expand Forest:Domain.com\Domains\Domain.com, right click the Default
Domain Policy, and select Edit.

3. Open Computer Configuration\Windows Settings\Security Settings\Local
Policies\User Rights Assignment\Impersonate a client after authentication,
add the Network Service and Administrator accounts into that policy.

Then, go to Group Policy Result in the GPMC console, right click the Group
Policy Result, select Group Policy Result wizard. In the wizard, select the
local computer (the SBS Server) and the user account (the one which you
used to logon, which should be the administrator account), follow the
wizard to generate a report.

After the report is created, select the report in the left panel and then
select the Settings tab in the right panel, check the policy we modified
above to make sure that the policy settings are applied.

Step 3: Please check the fax service running at Network Service account
account.

Then click Start -> Run, type Services.MSC and then click OK on the SBS
Server. Open the properties page of the FAX Service, go to Logon tab, make
sure that the FAX server is using the NT AUTHORITY\Network Service account.
Then, open the properties page of the Printer Spooler service and make sure
that it is using Local System account.

Step 4: Please make a clean boot to make sure the problem is not caused
third party software on SBS:

1. Click Start->Run...->type msconfig and press Enter.
2. Click Services tab and select Hide All Microsoft Services and Disable
All third party Services.
3. Click Startup tab and Disable All startup items.
4. Click OK and choose Restart.
5. After reboot, check whether the problem still occurs.
6. If there are no more problems, please use the above steps to enable
services and startup items one by one in order to figure out the root cause
of this issue.

The error code 4 means "Error_too_many_open_files" or "The System cannot
open the file", this is usually caused improper file permission or registry
key.
The above are the general steps to trouble shot this issue. If that doesn'
t work , we need to get more informaton to find out the root cause of the
problem :

1. Filemon and Regmon

Download the Filemon application from <
http://www.microsoft.com/technet/sysinternals/utilities/filemon.mspx >
Download the Regmon application from <
http://www.microsoft.com/technet/sysinternals/ProcessesAndThreads/Regmon.msp
x >

Monitor the system:

1. Open a new Fax, send it to 5 recipients. Please make sure that these 5
recipients are active recipients.
2. Before you send the fax, run the Filemon and Regmon application.
3. Send the fax.
4. When the issue occurs, stop the filemon and regmon application, email me
the log file.

2. Fax Activity log

a. Enable the full Fax event logs. Right-click the Fax snap-in and choose
'Properties'. In 'Event Reports' tab, tune all the scroll bar to the right
site (High).

b. Click 'Activity Logging' tab, check the option boxes to enable the Fax
activity logging. Modify the log folder location to C:\ActivityLog\ (Please
create the folder first).

c. Restart the Fax service. Send several Fax's to the SBS server. After
reproducing the problem, wait for a few minutes and go back to the server.
Collect the logs from C:\ActivityLog\

3. Please collect the MPS Report on the server box. The steps as follows:

a. Download the MPSRPT_ SETUPPerf.EXE from the following link and then run
this tool to gather some information from the problematic computer:
http://download.microsoft.com/download/b/b/1/bb139fcb-4aac-4fe5-a579-30b0bd9
15706/MPSRPT_SETUPPerf.EXE

b. Double-click on the MPSRPT_SETUPPerf.EXE file.

[Note] This process may take some time; however, it will not have a
negative effect on the performance.

c. A CAB file will be generated in the
%systemroot%\MPSReports\Network\Reports\Cab directory called
%COMPUTERNAME%_MPSReports.CAB. The CAB file will contain the reports
generated by the MPS Reporting Tool. Then send it me.

Please send the information to v-robeli@xxxxxxxxxxxxx with subject:
39738887 39945439-Event 32090 when Faxing To Multiple Recipients.

I am looking forward to hear from you.

If you need further assistance, please don't hesitate to let me know.

Best regards,

Robert Li(MSFT)

Microsoft CSS Online Newsgroup Support

Get Secure! - www.microsoft.com/security

=====================================================

This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx

When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.

Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.

For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

Any input or comments in this thread are highly appreciated.

=====================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
<From: scorbet@xxxxxxxxxxxxxxx
<Newsgroups: microsoft.public.windows.server.sbs
<Subject: Event 32090 when Faxing To Multiple Recipients
<Date: Fri, 20 Jul 2007 07:20:40 -0700
<Organization: http://groups.google.com
<Lines: 20
<Message-ID: <1184941240.298675.164100@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
<NNTP-Posting-Host: 68.236.220.145
<Mime-Version: 1.0
<Content-Type: text/plain; charset="iso-8859-1"
<X-Trace: posting.google.com 1184941240 28439 127.0.0.1 (20 Jul 2007
14:20:40 GMT)
<X-Complaints-To: groups-abuse@xxxxxxxxxx
<NNTP-Posting-Date: Fri, 20 Jul 2007 14:20:40 +0000 (UTC)
<User-Agent: G2/1.0
<X-HTTP-UserAgent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.2; SV1;
..NET CLR 1.1.4322; .NET CLR 2.0.50727),gzip(gfe),gzip(gfe)
<Complaints-To: groups-abuse@xxxxxxxxxx
<Injection-Info: q75g2000hsh.googlegroups.com; posting-host=68.236.220.145;
< posting-account=ps2QrAMAAAA6_jCuRt2JEIpn5Otqf_w0
<Path:
TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTFEEDS01.phx.gbl!news-out.
cwix.com!newsfeed.cwix.com!newscon02.news.prodigy.net!prodigy.net!news.glorb
..com!postnews.google.com!q75g2000hsh.googlegroups.com!not-for-mail
<Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:51610
<X-Tomcat-NG: microsoft.public.windows.server.sbs
<
<We can fax to 1 recipient just fine from any workstation. When we try
<to send to more than 1 recipient, we get this error message
<
<The fax was not submitted successfully.
<
< The following error occurred: 4.
< This error code indicates the cause of the error.
<
< Sender Machine Name: \\SBSERVER.
< Sender User Name: administrator.
< Sender Name: Administrator.
< Number of Recipients: 5.
<
<
<I have tried everything in this link.
<
<http://www.tech-archive.net/Archive/Windows/microsoft.public.windows.server
..sbs/2005-07/msg02323.html
<
<Please help!
<
<

.



Relevant Pages

  • Re: Erroneous E-mails sent entries in Server Usage Report
    ... The messages are being delivered successfully by Exchange - there is no external mail server involved. ... the Administrator is the typically the only user account that has non-zero values listed in the report. ... the information "E-mail sent to external recipients" lists *zero* messages being sent by all users other than Administrator. ...
    (microsoft.public.windows.server.sbs)
  • Re: E-mail deos not get to the destination
    ... It sounds like your e-mails are being blocked by the server due to policy ... Either blocked attachment, too many recipients or your domain ...
    (microsoft.public.exchange2000.general)
  • Re: Automated HTML messages & Second Server
    ... You might examine the settings of the SMTP virtual server on both servers ... Other reports are being received just fine to recipients on both ... servers except this one report. ... server B receive it as plain text (broken HTML). ...
    (microsoft.public.exchange.admin)
  • Re: Setting up Exchange 2003
    ... You can create policy to govern the smtp address under you ... recipients policies/ create a new policy and give it the smtp address you ... want this server to expect mail for. ...
    (microsoft.public.exchange.setup)
  • Re: SMTP CHange
    ... We at one time ran in mixed mode when we ... How can I manual remove this orignal 5.5 server. ... policies, and then from all recipients manually, with a script, or by some ... You can force the reapplication of the recipient policy, ...
    (microsoft.public.exchange.admin)