Entourage 2008 EWS Attachment limit on Exchange 2010

Hi Folks,
I'm having a problem allowing my Entourage users to attach files larger than 10MB. I've looked through all of the potential attachment limits on Transport config/Send connectors/Receive connectors/Users mailbox settings, but they all look okay to me.
[PS] C:\Windows\system32>get-mailbox user | fl max*
MaxSafeSenders    :
MaxBlockedSenders :
MaxSendSize       : 150 MB (157,286,400 bytes)
MaxReceiveSize    : 150 MB (157,286,400 bytes)
[PS] C:\Windows\system32>get-sendconnector | fl max*
MaxMessageSize : 150 MB (157,286,400 bytes)
MaxMessageSize : 150 MB (157,286,400 bytes)
[PS] C:\Windows\system32>get-receiveconnector | fl max*
MaxInboundConnection                    : 5000
MaxInboundConnectionPerSource           : unlimited
MaxInboundConnectionPercentagePerSource : 100
MaxHeaderSize                           : 64 KB (65,536 bytes)
MaxHopCount                             : 30
MaxLocalHopCount                        : 8
MaxLogonFailures                        : 3
MaxMessageSize                          : 150 MB (157,286,400 bytes)
MaxProtocolErrors                       : 5
MaxRecipientsPerMessage                 : 5000
MaxAcknowledgementDelay                 : 00:00:30
MaxInboundConnection                    : 5000
MaxInboundConnectionPerSource           : 20
MaxInboundConnectionPercentagePerSource : 2
MaxHeaderSize                           : 64 KB (65,536 bytes)
MaxHopCount                             : 30
MaxLocalHopCount                        : 8
MaxLogonFailures                        : 3
MaxMessageSize                          : 150 MB (157,286,400 bytes)
MaxProtocolErrors                       : 5
MaxRecipientsPerMessage                 : 200
MaxAcknowledgementDelay                 : 00:00:30
[PS] C:\Windows\system32>get-transportconfig | fl max*
MaxDumpsterSizePerDatabase : 100 MB (104,857,600 bytes)
MaxDumpsterTime            : 7.00:00:00
MaxReceiveSize             : 150 MB (157,286,400 bytes)
MaxRecipientEnvelopeLimit : unlimited
MaxSendSize                : 150 MB (157,286,400 bytes)
I'm running Exchange 2010 (with Rollup3 installed), on Server 2008R2.
My clients are running Entourage 2008 EWS, patched up with the latest Office Mac updates.
Apart from their inability to send 10+MB attachments, everything else is fine.
Regards,

Shane
Toutges solution worked for us. Exchange Server 2010 (current patch level as of March 2015), Mac OS Outlook 2011 via EWS.
Key to the solution is this revision:
maxReceivedMessageSize value
to [example value]
51200000 underneath the heading <EWSMessageEncoderSoap11Element />. There are 6 places to make this change (bytes)
I have not seen this noted under the several MS Tech Net articles that pertain to the problem of sending large email attachments via Mac Outlook 2011 via EWS.

Similar Messages

Upgrade Windows 2008 R2 sp1 on an Exchange 2010 SP3 server

I have looked high and low for an answer to this question:
1. I have Windows 2008 R2 running Exchange 2010 SP3
2. Can I upgrade Windows 2008 R2 to SP1 with Exchange 2010 SP3 onboard?
3. Are there pre-requisites for doing this?
4. If so, where can I get the documentation?
I have spent hours looking through Google and Technet. Lots of information about compatibility of 2008 R2 and Exchange SP1 and SP2.
Your wisdom and experience would be appreciated. Thank you!!
Charlie

Hi,
"Can I upgrade Windows 2008 R2 to SP1 with Exchange 2010 SP3 onboard?"
Yes, you can.
"Are there pre-requisites for doing this?"
There is no pre-requisites, however, as what Idan Vexler mentioned above, downtime is required.
"If so, where can I get the documentation?"
Here are two related threads for your reference.
http://social.technet.microsoft.com/Forums/en-US/1093a91d-aed8-4c91-b538-ca82f5860523/upgrading-windows-2008-r2-enterprise-to-sp1-on-exchange-2010?forum=exchange2010
http://social.technet.microsoft.com/Forums/exchange/en-US/0a7f29a2-04a5-485f-9b0c-061f89b311a5/installing-windows-2008r2-sp1-on-exchange-server-2010?forum=exchange2010
Hope this helps.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Total Attachment Size Restrict - Exchange 2010

Hi Guys,
Am trying to create a Transport rule to restrict attachment size for a particular group members. (restriction to 1MB total attachment size)
The problem is that when a member of user tries to send email with four attachment(300KB x 4nos.) which exceeds 1MB he/she is still able to send emails.
When a users send single attachment of 1MB above, he/she gets the NDR which is what am expecting.
Reference:- http://technet.microsoft.com/en-us/library/bb124345%28v=exchg.150%29.aspx
Attachment size limits These limits apply to the maximum allowed size of a
single attachment within a message. The message may contain many attachments that greatly increase the overall size of the message. However, an attachment size limit applies to the size of an individual attachment only.
How to restrict total/sum size of all attachment which exceeds 1MB?
- Charles

Hi,
Based on my knowledge, we can't limit total attachment size for a message directly. But As Ed said, we can use message size limit to limit the total size of a message as a workaround.
Hope this can be helpful to you.
Best regards,
Amy Wang
TechNet Community Support

Snow Leopard-Exchange Server 2003-Entourage 2008 (12.2.1)

+I have one final question before I upgrade to Snow Leopard.+
I currently run a 2.8 GHz Mac Pro, Leopard 10.5.8, Entourage 2008 (12.2.1) using Exchange server 2003. Everything is happy and works well.
I understand that I won't be able to use the new Snow Leopard built-in Exchange Server support.
*But, if I upgrade to Snow Leopard...will everything stay happy with what I've been running?*

There are connectivity issues between Exchange Server 2003 and Exchange accounts in Entourage 2008 running on Snow Leopard. These connectivity issues are also evident via web-based email (Safari & FireFox) on Snow Leopard and Exchange Serve 2003.
You will eventually loose connection to Exchange Server 2003. Restarting your computer will solve the problem temporarily.
POP accounts appear to work fine in this environment.

Exchange 2010 Store.exe Memory Usage

I have read about msExchESParamCacheSizeMax and it seems to do nothing with my server.
I am running Server 2008 R2 x64. With Exchange 2010 x64 with 1 Mailbox Store and 10 Mailboxes. The store.exe process sucks up anywhere from 11-13GB of Ram on my 32GB server.
What is the true way to limit the store.exe process or the database?

Hi Miller,
I agree with Amit.
We usually receive questions that Exchange service (store.exe) is using most of the memory on a mailbox server.
If another process should need the more memory, the Exchange store.exe process will released it as required. This is by design.
More details to see following blog:
Exchange 2010 store.exe service takes high memory utilization.
http://blogs.technet.com/b/maliks/archive/2012/04/25/exchange-2010-store-exe-service-takes-high-memory-utilization.aspx
I also find a similar thread for your reference:
Exchange 2010 and Store.exe
https://social.technet.microsoft.com/Forums/exchange/en-US/b18cbeb5-8ec7-4669-b25e-c7ea95992b9a/exchange-2010-and-storeexe
Thanks
Mavis Huang
TechNet Community Support

Exchange 2010 failing to upgrade to SP1, SP2, or SP3

My host server is running Windows Server 2008 R2 Standard. Currently Exchange 2010 is without any service pack. I initially tried to upgrade to SP1 but that failed with the message below. Thinking that I could perhaps skip to SP2 or even SP3 I attempt that
upgrade and received a similar message though not posted here. The Schema for our domain shows that it is at the Windows Server 2008 R2 level. I am attempting to apply the update using the Enterprise/Schema admin account for our network.
Here is the error message that I receive. This happens after all prereq checks are done and the installation has actually started.
Summary: 15 item(s). 0 succeeded, 1 failed.
Elapsed time: 00:00:04
Organization Preparation
Failed
Error:
The following error was generated when "$error.Clear();
Write-ExchangeSetupLog -Info "Set the default Accepted domain from the default recipient policy";
$defaultEmailAddressPolicy = get-EmailAddressPolicy -Identity:"Default Policy";
$defaultSmtpTemplate = $defaultEmailAddressPolicy.EnabledPrimarySMTPAddressTemplate;
$index = $defaultSmtpTemplate.IndexOf("@");
$eapAuthoritativeDomain = $defaultSmtpTemplate.Substring($index+1);
$defaultDomain = get-accepteddomain | where {$_.DomainName -eq $eapAuthoritativeDomain };
$defaultDomain | set-accepteddomain -MakeDefault:$true;
Write-ExchangeSetupLog -Info "Default domain $defaultDomain";
" was run: "The operation couldn't be performed because object 'Default Policy' couldn't be found on 'marvin.intercity.org'.".
The operation couldn't be performed because object 'Default Policy' couldn't be found on 'marvin.intercity.org'.
Click here for help... http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.1.218.11&e=m...
Error:
The following error was generated when "$error.Clear();
Write-ExchangeSetupLog -Info "Set the default Accepted domain from the default recipient policy";
$defaultEmailAddressPolicy = get-EmailAddressPolicy -Identity:"Default Policy";
$defaultSmtpTemplate = $defaultEmailAddressPolicy.EnabledPrimarySMTPAddressTemplate;
$index = $defaultSmtpTemplate.IndexOf("@");
$eapAuthoritativeDomain = $defaultSmtpTemplate.Substring($index+1);
$defaultDomain = get-accepteddomain | where {$_.DomainName -eq $eapAuthoritativeDomain };
$defaultDomain | set-accepteddomain -MakeDefault:$true;
Write-ExchangeSetupLog -Info "Default domain $defaultDomain";
" was run: "You cannot call a method on a null-valued expression.".
You cannot call a method on a null-valued expression.
Click here for help... http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.1.218.11&e=m...
Error:
The following error was generated when "$error.Clear();
Write-ExchangeSetupLog -Info "Set the default Accepted domain from the default recipient policy";
$defaultEmailAddressPolicy = get-EmailAddressPolicy -Identity:"Default Policy";
$defaultSmtpTemplate = $defaultEmailAddressPolicy.EnabledPrimarySMTPAddressTemplate;
$index = $defaultSmtpTemplate.IndexOf("@");
$eapAuthoritativeDomain = $defaultSmtpTemplate.Substring($index+1);
$defaultDomain = get-accepteddomain | where {$_.DomainName -eq $eapAuthoritativeDomain };
$defaultDomain | set-accepteddomain -MakeDefault:$true;
Write-ExchangeSetupLog -Info "Default domain $defaultDomain";
" was run: "You cannot call a method on a null-valued expression.".
You cannot call a method on a null-valued expression.
Click here for help... http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.1.218.11&e=m...
Error:
The following error was generated when "$error.Clear();
Write-ExchangeSetupLog -Info "Set the default Accepted domain from the default recipient policy";
$defaultEmailAddressPolicy = get-EmailAddressPolicy -Identity:"Default Policy";
$defaultSmtpTemplate = $defaultEmailAddressPolicy.EnabledPrimarySMTPAddressTemplate;
$index = $defaultSmtpTemplate.IndexOf("@");
$eapAuthoritativeDomain = $defaultSmtpTemplate.Substring($index+1);
$defaultDomain = get-accepteddomain | where {$_.DomainName -eq $eapAuthoritativeDomain };
$defaultDomain | set-accepteddomain -MakeDefault:$true;
Write-ExchangeSetupLog -Info "Default domain $defaultDomain";
" was run: "Cannot bind argument to parameter 'Identity' because it is null.".
Cannot bind argument to parameter 'Identity' because it is null.
Click here for help... http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.1.218.11&e=m...
Elapsed Time: 00:00:04
Preparing Setup
Cancelled
Stopping Services
Cancelled
Languages
Cancelled
Remove Exchange Files
Cancelled
Preparing Files
Cancelled
Copy Exchange Files
Cancelled
Language Files
Cancelled
Restoring services
Cancelled
Languages
Cancelled
Hub Transport Role
Cancelled
Client Access Role
Cancelled
Mailbox Role
Cancelled
Management Tools
Cancelled
Finalizing Setup
Cancelled

Agreed - check the default email address policy is not corrupt and same for remote domains - did you make ay modifications to them?
Since he is running this as das Uber-admin, it will prep Exchange schema and AD even if not explicitly done prior. Exchange setup is helpful like that, well some times....
Cheers,
Rhoderick
Microsoft Senior Exchange PFE
Blog:
http://blogs.technet.com/rmilne
Twitter:   LinkedIn:
  Facebook:
  XING:
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Allow all mailbox users to send emails up to 100 recipients (Exchange 2010)

Greetings,
Could you please help on writing a Powershell script using Exchange Management Shell on how to realize the following:
I want to grant all recipients the ability to send emails up to 100 recipients, this rule will be applied by default to all mailboxes including the new created ones and the old ones.
FYI, i tried the following cmdlets from the organizational level:
Set-TransportConfig -MaxRecipientEnvelopeLimit 100
This cmdlet did not applied to all mailboxes, because i have found some ones have unlimited RecipientLimits, some others have more than 100, newly created
mailboxes are unlimited by default !
Here is the cmdlet i have used to verify the
RecipientLimits one some mailboxes:
Get-Mailbox -Identity
"username" | Select-Object RecipientLimits | fl
I want to force all users including the new and old ones to have RecipientLimits to 100, and if a user needs more than 100 i can grant him/her explicitly.
Thanks in advance.
Redouane
Redouane SARRA

Thanks a lot, it works with all existing mailboxes, But not with new mailboxes which are unlimited by default.
I want this to apply to all mailboxes including newly created mailboxes.
Redouane SARRA
Ask in Exchange forum to teach you how to create users from a template and set the template to the value you want.
The Transport limit superceded the user limit. If the transport is set to 100 then ALL users are limited to 100.
This is why I recommend posting in the Exchange forum. Don't ask how to write a script. Ask how to set the limit in Exchange 2010. They will give you a link to the appropriate documentation, The issue I snot a scripting issue but
is a "how do I use Exchange " issue. Asking the correct question will get you further. Of course training in Exchange would be most helpful.
¯\_(ツ)_/¯

Exchange 2007 to Exchange 2010 cross forest simultaneous mailbox move limits

Hi All,
I am testing the throughput of mailbox moves from Exchange 2007 to Exchange 2010 cross forest. Single mailbox moves seem to be quite fast and I am not concerned about network, disk IO or server resource limitations, however I have not tested multiple simultaneous
mailbox moves to determine what the Exchange limitations are. If anyone could identify the limitations of the items below it would be much appreciated:
Limit of Exchange 2007 simultaneous mailbox moves per database
Limit of Exchange 2007 simultaneous mailbox moves per Mailbox server
Limit of Exchange 2007 simultaneous mailbox moves per CAS server
Limit of Exchange 2010 simultaneous mailbox moves per database
Limit of Exchange 2010 simultaneous mailbox moves per Mailbox server
Limit of Exchange 2010 simultaneous mailbox moves per CAS server
Any other Exchange 2007 or 2010 hard coded limits
Thanks in advance.
Michael.

My usual answer to this question is that Microsoft set these limits for a reason. Increasing them may not offer you much in the way of benefits if you end up slamming the server. I generally recommend that you leave them alone.
I have had occasional opportunities to change these constraints, most notably back during a migration to Exchange 2003 and international mailbox moves (Asia to U.S.) where the limiting factor was network latency. I was able to increase the number of
concurrent threads to 16 from the default 2 and there was still available bandwidth because the process was limited by the latency.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Exchange 2010 - Accepting Messages Above the Attachment Size Limit

Recently we implemented a new Exchange 2010 server in a site. This site is in another country with very poor WAN connectivity. Our standard attachment limit is 50MB (51200 kb) .
Since we have put this server in place I am seeing messages get stuck in the queue that are above the 50MB limit.
What I am confused about is how are they making it there, why is Exchange accepting them? I have checked all the connectors, they are all appear to be set correctly.
What I also notice is these messages sit in the queue and get error:
421 4.4.2 Connection dropped due to ConnectionReset
Any ideas?

Consider applying an enterprise limit by using Set-TransportConfig -MaxSendSize -MaxReceiveSize.
http://technet.microsoft.com/en-us/library/bb124151(v=exchg.150).aspx
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Entourage 2008 Exchange to Outlook Web Access

Okay, bear with me: I'm an end-user and not especially technically inclined.
That said, for years I've used Entourage 2008 as my email client (on a MacBook Pro, OSX 10.9), and it successfully works with the web-based Outlook account that my ISP provides, through a POP connection.
Now, I'd like to sync my Entourage calendar with one in Outlook.
Importing the Entourage calendar into Outlook was easy. But when I build an Exchange account in Entourage, I seem to have fallen on my face.
It still imports mail, but can't send mail
It doesn't sync the Outlook calendar (on the web) to Entourage's
I have upgraded Entourage to the EWS version of 12.3.6.
After configuring the Web Services Edition (as best I could), I still can't send email — or sync Entourage to the online Outlook calendar.
Here's the error message: "Unexpected data was encountered" Error: -17997
I'm using the same settings I see in my Nokia N8 mobile's Exchange mailbox settings (which works perfectly with Outlook including syncing its calendar with OWA's calendar).
What puzzles me is that an Exchange account on Entourage and my MacBook won't work using the same settings as Exchange ActiveSync on my Nokia N8, which syncs flawlessly with OWA. Any and all suggestions gratefully received.

An additional point of information. You've posted to an Exchange 2013 forum. Is your Exchange organization running Exchange 2013? If not, the Exchange previous versions forums are here:
http://social.technet.microsoft.com/Forums/en-US/category/exchangeserverlegacy.
You should share the Exchange version, service pack and update level you're running.
If you believe that it's an Exchange configuration problem as opposed to Entourage, then the issue would likely be in the configuration of Exchange Web Services, particularly the EWS virtual directory.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Exchange 2010 SP2 RU2 - Indexing backlog reached a critical limit of 48 hours or the number of items in the retry queue is greater than 10000 for one or more databases

We have been getting intermittent SCOM alarms for our Exchange 2010 MBX server citing "Indexing backlog reached a critical limit of 48 hours or the number of items in the retry queue is greater than 10000 for one or more databases"
I see events in EventViewer that SCOM is triggering on, but not whats generating the events or how else to test for them.
    get-eventlog -computername SERVERNAME -logname "Application" -after "03/14/2013" | ?{$_.eventid -eq "5604"} | select MachineName,EventID,EntryType,Message | ft -autosize
One MS Forum post online says it is a bug in RU4, unclear if it may also be a bug in RU2 (our installed version).
    http://social.technet.microsoft.com/Forums/en-US/exchangesvradmin/thread/9dcb3011-9327-4935-9479-62b38a6ddd87
    "I was looking for the same error and found this.. it basically says that this is a bug in RU4 and RU4-v2...and it needs to be removed."
tests using troubleshooting scripts find no issues with search indexer,
    [PS] C:\Program Files\Microsoft\Exchange Server\V14\scripts>.\Troubleshoot-CI.ps1
    Get-EventLog : No matches found
    At C:\Program Files\Microsoft\Exchange Server\V14\scripts\CITSLibrary.ps1:622 char:40
    + $msftesqlCrashes = get-eventlog <<<< -computername $Server -after $StartTime -logname "Application" -source $msftesqlServiceName | where {$_.eventId
    -eq $msftesqlCrashEventId}
        + CategoryInfo : ObjectNotFound: (:) [Get-EventLog], ArgumentException
        + FullyQualifiedErrorId : GetEventLogNoEntriesFound,Microsoft.PowerShell.Commands.GetEventLogCommand
    Name IsDeadLocked CatalogStatusArray
    SERVERNAME False {DATABASENAME\SERVERNAME, DATABASENAME\S...
    [PS] C:\Program Files\Microsoft\Exchange Server\V14\scripts>
and tests against searches on each DB themselves show no issues and respond typically within 3 seconds.
    [PS] C:\Program Files\Microsoft\Exchange Server\V14\scripts>Test-ExchangeSearch | ft Server, Database, ServerGuid, ResultFound, SearchTimeInSeconds, Error -AutoSize
    Server Database ServerGuid ResultFound SearchTimeInSeconds Error
    SERVERNAME DATABASENAME b16e3461-257c-40dd-a9ad-99a5f41a927e True 2.937
I also tried to check the Performance Viewer for the MSExchange Search Indexer and MXExchange Search Indices but am unsure which of the many metrics would indicate this issue.
We have had no reports of search issues from our users and have been unable to duplicate any impairment in our testing.
Does anyone else have any suggestions for tests to check or steps to take on this alert? Is it simply a false alarm or a timeout of other sorts during testing? We have 80 DAGs on this server (as well as all our servers, some of which have also reported the
same alert) and the Test-ExchangeSearch command times out before completely testing all DAGs.

Hi IAMChrisL,
Any updates?
Frank Wang
TechNet Community Support

Exchange 2010 on windows server 2008 r2 (VMware Virtual Machine)

Hello All,
I am trying to get an exchange 2010 test environment running.
This is a virtual deployment on windows server 2008 r2 sp1 and the actual exchange install passes the initial requisite checks, during the install it however fails on creating a hub transport tole with the following messages in the setup log.
[ERROR] An error occurred with error code '3221685951' and message 'The remote procedure call failed and did not execute.'.
[1] The following 1 error(s) occurred during task execution:
[1] 0. ErrorRecord: An error occurred with error code '3221685951' and message 'The remote procedure call failed and did not execute.'.
[1] 0. ErrorRecord: Microsoft.Exchange.Management.Deployment.ExsetdataException: An error occurred with error code '3221685951' and message 'The remote procedure call failed and did not execute.'.
[1] [ERROR] The following error was generated when "$error.Clear();
install-ExsetdataAtom -AtomName Server -DomainController $RoleDomainController
" was run: "An error occurred with error code '3221685951' and message 'The remote procedure call failed and did not execute.'.".
[1] [ERROR] An error occurred with error code '3221685951' and message 'The remote procedure call failed and did not execute.'.
[1] [ERROR-REFERENCE] Id=AllADRolesCommon__ExsetdataServer Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
[1] Setup is stopping now because of one or more critical errors.
Any of you exchange gurus out there seen this before?
Any help is much appreciated.
Regards

Hi ,
I tried a Exchange 2007 SP3 install (over Windows 2008 R2 too) with the same error code message: "Error code
3221685951. Remote procedure call"
It occurs to me:
1-The Schema master is in another site.
2-There are two ISA Servers in between but I shut down the feature "Strict RPC compliance."
Beyond that, I really don't know what to do.
Luis Olías Técnico/Admon Sistemas . Sevilla (España - Spain)

Event IDs 136 and 137 0x80000000000000 in System Log on Windows 2008 R2 Server, Exchange 2010 in Cluster

Hi,
I'm having an issue with one of my exchange 2010 Servers. We had a power outage and upon recovery, I cannot start Services Net.Pipe Listener Adapter and Net.Tcp Listener Adapter (And thus cannot Start IIS and provide Exchange Client Services.) This is a
physical server (Not VMWare or Hyper-V)
The System event log has lots of Event 136's and 137s on Ntfs with the keyword - 0x80000000000000 - The General Messages are: The default transaction resource manager on volume C: encountered an error while starting and its metadata was
reset. The data contains the error code.
and
The default transaction resource manager on volume OS encountered a non-retryable error and could not start. The data contains the error code.
XML Output as follows:
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Ntfs" />
<EventID Qualifiers="32772">136</EventID>
<Level>3</Level>
<Task>2</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated
SystemTime="2014-11-17T18:10:37.788942300Z" />
<EventRecordID>315532</EventRecordID>
<Channel>System</Channel>
<Computer>server.domain.com</Computer>
<Security />
</System>
- <EventData>
<Data />
<Data>C:</Data>
<Binary>1C00040002003000020000008800048000000000060019C000000000000000000000000000000000060019C0</Binary>
</EventData>
</Event>
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Ntfs" />
<EventID Qualifiers="49156">137</EventID>
<Level>2</Level>
<Task>2</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated
SystemTime="2014-11-17T18:10:37.788942300Z" />
<EventRecordID>315531</EventRecordID>
<Channel>System</Channel>
<Computer>server.domain.com</Computer>
<Security />
</System>
- <EventData>
<Data />
<Data>OS</Data>
<Binary>1C0004000200300002000000890004C000000000020100C000000000000000000000000000000000020100C0</Binary>
</EventData>
</Event>
When I attempt to start the services - I get the following errors:
The Net.Pipe Listener Adapter service depends on the Windows Process Activation Service service which failed to start because of the following error:
Transaction support within the specified resource manager is not started or was shut down due to an error.
The Net.Pipe Listener Adapter service depends on the Windows Process Activation Service service which failed to start because of the following error:
Transaction support within the specified resource manager is not started or was shut down due to an error.
I have tried the "fsutil resource setautoreset true" fix without success.
Any ideas or direction would be much appreciated. Restoring this server will be extremely difficult.
Thanks!

We can close this question.
From an elevated prompt, I ran 'fsutil resource setautoreset true' and attempted to remove the files with .blf and regtrans-ms file extensions from C:\Windows\System32\config\TxR. but these files were locked by system processes. (They are also
tagged with the hidden file attrib so you may not see them at first)
So, I booted the system with a Windows 2008 R2 Install Disk, selected repair OS and selected the command prompt. I then performed a chkdsk /f c: and selected "Y" to unmount the drive. It made some repairs.
With the system booted from the install disk, and chkdsk executed, the locks were freed and I was able to delete the files from C:\Windows\System32\config\TxR.
Once the system rebooted, the services came back fine and everything was back to normal.

Installing Exchange 2010 on Server 2008 R2 Get error with Hub Transport Role

Hub Transport Role
Failed
Error:
The following error was generated when "$error.Clear();
          install-MsiPackage `
          -PackagePath ($RoleInstallPath + "TransportRoles\agents\Hygiene\ASEntIRS.MSI") `
          -LogFile ($RoleSetupLoggingPath + "\InstallASEntIRS.msilog") `
          -PropertyValues ("ALLUSERS=1") `
          -UpdatesDir $RoleUpdatesDir
        " was run: "Installing product D:\Program Files\Microsoft SQL Server\Microsoft\Exchange Server\V14\TransportRoles\agents\Hygiene\ASEntIRS.MSI failed. Fatal error during installation. Error code is 1603.".
Installing product D:\Program Files\Microsoft SQL Server\Microsoft\Exchange Server\V14\TransportRoles\agents\Hygiene\ASEntIRS.MSI failed. Fatal error during installation. Error code is 1603.
Fatal error during installation
Elapsed Time: 00:00:01
Client Access Role
Cancelled

Hi,
From the description, I recommend you copy the Exchange installation files to the local machine, or download a fresh copy of Exchange 2010 and then reinstall it.
Besides, please ensure that you install Exchange 2010 on 64-bit edition of Windows Server 2008 R2 Standard with SP1 or Windows Server 2008 R2 Enterprise with SP1.
If the issue persists, please refer to the following KB further troubleshooting.
You receive error 1603 when you try to install the Exchange Server 2010 RU1
https://support.microsoft.com/kb/981474
Hope it helps.
If you need further assistance, please feel free to let me know.
Best regards,
Amy
Amy Wang
TechNet Community Support

Is WMF3 or WMF4 supported in Exchange 2010 SP3 UR5 installed on Server 2008 R2 SP1?

We'd like to upgrade WMF (aka powershell) on our Exchange 2010 servers but I haven't been able to find any updated information on support with the most recent servicepack/update rollup.
Is installing WMF3 or WMF4 supported on Server 2008 R2 SP1 w/ Exchange 2010 SP3 UR5?

WindowsPowerShell 3.0 is supported. Haven't seen 4.0 running for exchange 2010 on 2008 R2
http://blogs.technet.com/b/heyscriptingguy/archive/2013/11/30/weekend-scripter-wmf-powershell-and-exchange-server-compatibility.aspx
http://blog.crayon.no/blogs/janegil/archive/2013/11/17/how_2D00_to_2D00_install_2D00_windows_2D00_powershell_2D00_4_2D00_0.aspx
Cheers,
Gulab Prasad
Technology Consultant
Blog:
http://www.exchangeranger.com    Twitter:
  LinkedIn:
   Check out CodeTwo’s tools for Exchange admins
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.
Gulab,
Where did you read that WMF3 is supported on Exchange 2010 SP3 on Server 2008 R2?
Neither of the links you pasted suggest that and in fact explicitly say "There has been no testing with ExchangeServer 2010 SP3 and WMF 3.0 installed on Windows Server 2008 R2."
My Bad, that was TYPO...
Cheers,
Gulab Prasad
Technology Consultant
Blog:
http://www.exchangeranger.com    Twitter:
  LinkedIn:
   Check out CodeTwo’s tools for Exchange admins
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Entourage 2008 EWS Attachment limit on Exchange 2010

Similar Messages

Maybe you are looking for