Exchange 2013 OWA: Cannot set auto reply in shared mailbox

We use Exchange 2013 and Outlook 2010. We have 3 users tha connect to a shared mailbox. We would like to have an auto-reply on this mailbox but cannot set it with the OWA. We get the following error:
Client Information
User Agent: Mozilla/5.0 (compatible; MSIE 10.0; Windows NT 6.3; WOW64; Trident/7.0; .NET4.0E; .NET4.0C; InfoPath.3)
CPU Class: x86
Platform: Win32
System Language: nl-NL
User Language: nl-NL
CookieEnabled: true
Exception Details
Date: Fri Jul 11 11:31:40 UTC+0200 2014
Message: Kan de eigenschap _events van een niet-gedefinieerde verwijzing of een verwijzing naar een lege waarde niet ophalen
Url:
https://owa.'domainname'.nl/ecp/15.0.712.22/scripts/microsoftajax.js
Line: 5
Call Stack
Dump Event
errorMessage = Kan de eigenschap _events van een niet-gedefinieerde verwijzing of een verwijzing naar een lege waarde niet ophalen
errorUrl =
https://owa.'domainname'.nl/ecp/15.0.712.22/scripts/microsoftajax.js
errorLine = 5
errorCharacter = 57312
errorCode = 0
actionURL =
altKey = false
altLeft = false
behaviorCookie = 0
behaviorPart = 0
bookmarks = null
boundElements = [object HTMLCollection]
button = 0
buttonID = 0
cancelBubble = false
clientX = 1187
clientY = 72
contentOverflow = false
ctrlKey = false
ctrlLeft = false
data =
dataFld =
dataTransfer = null
fromElement = null
keyCode = 0
nextPage =
offsetX = 0
offsetY = 0
origin =
propertyName =
qualifier =
reason = 0
recordset = null
repeat = false
returnValue = true
screenX = 2373
screenY = 343
shiftKey = false
shiftLeft = false
source = null
srcElement = null
srcFilter = null
srcUrn =
toElement = null
type = error
url =
wheelDelta = 0
x = 0
y = 0
getAttribute =
function getAttribute() {
    [native code]
removeAttribute =
function removeAttribute() {
    [native code]
setAttribute =
function setAttribute() {
    [native code]
Detailed Call Stack

Hi,
Error information is quite important. In order to solve your issue effectively, please take your time to describe the error in English for my research.
Best regards,
Amy Wang
TechNet Community Support

Similar Messages

Exchange 2013 OWA is not auto formatting hyperlinks when forwarding a message

I have 2 sales managers in a company that receive sales leads via email from our website. The email is formatted in HTML with a table containing the name and email address of the customer and the url of the product they're interested in from our website.
The managers then forward this email to the next available sales associate to contact the potential customer.
The first sales manager uses Outlook and receives the sales lead email with active hyperlinks intact for the email address of the customer and url of the product. When you inspect the email, there is no href code in the source, so outlook is recognizing
the types 'email address' and 'url' to make the text active. He then forwards the email to sales with active hyperlinks in the source. (they prefer this)
The second sales manager uses OWA. when he receives the email, the email address and url are plain text (which is how its coded) so when he forwards the email to sales there are no hyperlinks.
Is it possible to set OWA (for exchange 2013) to auto format (recognize then format) email addresses and url's from an email when forwarding it that didn't have the href code in the source to begin with? ...like Outlook does?

Hi,
Does this issue happen on all the OWA users or on specific user?
Does this issue happen when sending emails by HTML format?
Thanks,
Simon Wu
TechNet Community Support

Exchange 2013 OWA HTTP 500 error when opening another mailbox

We have an Windows Server 2012 Exchange 2013 server with OWA.
All users can login fine, but when I open another mailbox with my Admin account, having enabled access to that user's mailbox, the URL redirects to /owa/auth/errorfe.aspx?httpCode=500 and shows:
something went wrong
Sorry, we can't get that information right now. Please try again later. If the problem continues, contact your helpdesk
Google won't help me in this instance. Where in the eventlog are OWA events logged?

Hello,
I am joining to the thread opener, however, we do not use exchange server. we are using the Cloud services through Microsoft and as far as I know, the version is 2013 wave 15 (again, through Microsoft's cloud).
when I open the outlook, I can see the shared mailbox just fine.
when I open the office web access, and I search the mailbox through the 'add another mailbox..' It finds it however when I press the add button I get the HTTP 500 error.
when I tried to open a different mailbox (another shared mailbox I gave myself permissions for), it opens just fine.
it seems (from what I can tell) it is this specific shared mailbox that I cannot open through OWA while others I can.
when I try to open the mailbox in question through a different internet browser (Chrome) I get this Error:
NegotiateSecurityContext failed with for host 'db3pr04mb138.eurprd04.prod.outlook.com' with status'LogonDenied'
the error seems to be persistent on this specific mailbox only regardless to what browser I am trying to access with.
I can only assume that the solutions you (Winnie) offered isn't relevant in my case.
thanks in advance for any attempt to help me with this issue.

Exchange 2013 Issue: Outlook 2010 auto populating the From Tab when forwarding email

Exchange 2013 Issue: Outlook 2010 auto populating the From Tab when forwarding email
I am running Exchange 2013 and I have an end user who connects to it via Outlook 2010. All was going well till he went to forward an email and he noticed that the From button appeared and auto populated the sender's email address.
I have clicked the Empty Auto Complete List in Outlook's Send messages... still displayed the From tab when forwarding.
I recreated the profile in outlook... same thing.
I created the profile with outlook 2013... same thing.
There is only one user profile setup in Outlook.
(I know the from tab usually appears when you have multiple profiles setup in Outlook and/or when you configure the "From" tab.)
I opened the end user's email in Exch 2013's OWA... what was different here was when I clicked on the email and it opened, it did NOT have the Reply or Forward option... and it displayed as a "Draft" email.
Does anyone have any ideas?

So are you saying that the from button is filling the option with the original senders address (eg the person who sent the message to your user), or that it's filling in the your users address (in which case I don't understand what the issue is, since
it IS going from your user)?

Exchange 2013 OWA IM to federated users

Hi I configured Exchange 2013 OWA IM for Lync server and everything is working fine except that I can't IM federated Lync users when the conversation is initiated from OWA. When I start an IM conversation from the federated user to my OWA, everything is
working fine. Also the replies arrive then! So it must be something with initiating the session. I don't have issues with federated users form normal Lync desktop clients or mobile clients.
In the lync logs I notice the following when starting the conversation from OWA:
1027;reason="Cannot route this type of SIP request to or from federated partners";
I also notice there's a KB2977259 (http://support.microsoft.com/kb/2977259) that discusses similar things but I'm not working with contacts like that and I guess they don't mean that you have to do this for every federated contact a Lync user has.
Does somebody else also experience this issue?
Update: following this KB I tried to add a new outlook contact in owa and add my sip address as "sip:[email protected]". When doing this it actually work to IM this federated user. But this is actually a workaround you can't expect your users
to implement. I can't believe nobody else has issues with this.

Hi DS_Kevin,
Please post a little more log information. It seems that IM from OWA can’t locate the federated user’s SIP address without the sip prefix.
Best Regards,
Lisa Zheng
Lisa Zheng
TechNet Community Support

Exchange 2013 owa integration with ADFS and cooexistance with exchange 2007

Team,
I have successfully integrated adfs 3.0 and Exchange 2013 owa and ecp. However, we have a coexistence environment with exchange 2007. When you access owa, which then redirects you to adfs, sign-in, and then get redirected back to owa. If your
mailbox is still within exchange 2007, you get a blank login page. If you mailbox is in exchange 2013 then you successfully get the owa page for 2013. The problem is that all exchange 2007 mailbox users get blank pages at login. So I have determined
that exchange 2013 cas is not doing the service location lookup on the mailbox to determine if a redirect to the legacy owa address is needed. Is there a configuration setting that I might be missing? Or does the integration with adfs and owa not support
the much needed mailbox lookup for a coexistance environment? A side note: if we enable FBA with owa, both login scenarios work just fine (legacy and new 2013). The legacy namespace has been created, and applied to the exchange 2007 urls.

Hi,
Try using AD FS claims-based authentication with Outlook Web App and EAC
http://technet.microsoft.com/en-us/library/dn635116(v=exchg.150).aspx
Thanks,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

How to configure Exchange 2013 OWA with Single Sign On

Hi All ,
How to configure Exchange 2013 OWA with Single Sign On ?
Thanks .

Hi,
From your description, I am not quite sure what you really want to achieve. Could you explain it furthermore? If you need to set up Exchange 2013 OWA single sign on with Exchange 2010, here is a helpful thread for your reference.
Exchange 2013 OWA Single Sign on with Exchange 2010
https://social.technet.microsoft.com/Forums/en-US/2899ebfc-8622-4cdc-8d77-d76b607618f7/exchange-2013-owa-single-sign-on-with-exchange-2010?forum=exchangesvrdeploy
If that is not your case, please feel free to tell me.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Amy Wang
TechNet Community Support

Exchange 2013 OWA internal only

Hi all,
Does anyone know how to restrict Exchange 2013 OWA for internal only, but can't impact Exchange ActiveSync service?
I guess IP Address and Domain Restrictions can make it, but it may impact ActiveSync.
Any good solution?
Thank,
Ian

Hi,
Based on my research, we can install the CAS and Mailbox roles in separate two servers. Then we can create new website with a unique IP and only adding ActiveSync to that website. That would give us a website hosted on the box that served the ActiveSync
devices but nothing else, leaving the OWA open for internal access. The firewall would point to this website/IP on the CAS. We could also create a virtual directory under there for /OWA and /Exchange which would serve up the generic ““this service is no longer
available, please contact the help desk” message as the default webpage
http://blogs.technet.com/b/messaging_with_communications/archive/2011/05/02/how-to-block-owa-for-external-users.aspx
Thanks,
Angela Shi
TechNet Community Support

Publish Exchange 2013 OWA + Active Sync + Outlook Anywhere using TMG 2010

We plan to publish our new Exchange 2013 SP1 servers (3 in DAG) outside corporate network using TMG 2010. I am looking for some guide how to do it in the proper way. What I found is little old and does not take into consideration Exchange 2013
SP1
http://blogs.technet.com/b/exchange/archive/2012/11/21/publishing-exchange-server-2013-using-tmg.aspx
Any advice how to publish Exchange 2013 OWA using form-based authentication and how to use Kerberos Constrained Delegation?

Hi,
The blog below describes some scenarios about publishing Exchange. You could have a look the Scenario 2.
Exchange publishing after TMG/UAG
http://dizdarevic.ba/ddamirblog/?p=168
Note: Microsoft provides third-party contact information to help you find technical support. This contact
information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information
Best Regards,
Joyce
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Medrec pointbase orace RDBMS migration (Cannot set auto-commit mode)

For proof-of-concept purposes, I'm trying to install the MEDREC application on an Oracle database. I've migrated the schema using the demo.ddl found on the base install image. However, when I update the JDBC connect string to point to the oracle rdbms, I rec'v the message below. Has anyone discovered a workaround?
After the jdbc connect string is updated to point to Oracle, I see the app server connected successfully to the database.
javax.ejb.EJBTransactionRolledbackException: EJB Exception: ; nested exception is: <openjpa-1.1.0-r422266:657916 nonfatal general error> org.apache.openjpa.persistence.PersistenceException: Cannot set auto-commit mode when using distributed transactions
     at weblogic.ejb.container.internal.BaseLocalObject.handleSystemException(BaseLocalObject.java:794)
     at weblogic.ejb.container.internal.BaseLocalObject.postInvoke1(BaseLocalObject.java:486)
     at weblogic.ejb.container.internal.BaseLocalObject.postInvokeTxRetry(BaseLocalObject.java:424)

For proof-of-concept purposes, I'm trying to install the MEDREC application on an Oracle database. I've migrated the schema using the demo.ddl found on the base install image. However, when I update the JDBC connect string to point to the oracle rdbms, I rec'v the message below. Has anyone discovered a workaround?
After the jdbc connect string is updated to point to Oracle, I see the app server connected successfully to the database.
javax.ejb.EJBTransactionRolledbackException: EJB Exception: ; nested exception is: <openjpa-1.1.0-r422266:657916 nonfatal general error> org.apache.openjpa.persistence.PersistenceException: Cannot set auto-commit mode when using distributed transactions
     at weblogic.ejb.container.internal.BaseLocalObject.handleSystemException(BaseLocalObject.java:794)
     at weblogic.ejb.container.internal.BaseLocalObject.postInvoke1(BaseLocalObject.java:486)
     at weblogic.ejb.container.internal.BaseLocalObject.postInvokeTxRetry(BaseLocalObject.java:424)

Auto-mapping of shared mailboxes in a resource forest scenario

In a resource forest scenario you assign full access to a shared mailbox using:
Add-MailboxPermission -Identity SharedMailbox -User AccountForestDomain\UserID -AccessRights FullAccess
This provides the user in the account forest full access, but it will NOT auto-map the shared mailbox in Outlook.
If you use the command:
Add-MailboxPermission -Identity SharedMailbox -User UserID -AccessRights FullAccess
and UserID is the disabled account of the linked mailbox in the resource forest then the user in the account forest does not have the necessary permission to
open the mailbox, but the auto-mapping of the mailbox in Outlook works.
You have to use both commands to have the auto-mapping feature and have access to the shared mailbox.
This looks like another issue of the auto-mapping feature. The intention of the feature is good, but the way it was implemented can be improved.
How do you configure full access to shared mailboxes in a resource forest scenario?

Hi J-H,
Because i don’t have such a lab environment, so I am unable to do a test.
Now let’s separate the issue.
1. The first issue is
[email protected]
unable to auto configure outlook profile.
I suggest you
changing the user’s attributes in the account forest, does it work?
2. The second issue is
[email protected] unable to open a shared mailbox in the resource
forest.
At first, I suggest you create a shared mailbox in resource forest with this command.
New-Mailbox -name
<name> -Database <Database name> -OrganizationalUnit Users –UserPrincipalName
<UPN value, example: [email protected]> -<ResourceType: Room, Equipment or Shared>
Managing
Resource Mailboxes in Exchange Server 2007 (Part 1)
Then test if you can log on the shared mailbox via outlook.
If yes, then grant full access right for
[email protected]
to [email protected]
Resource:
Shared mailbox
permission in resource forest with linked users
Manage Full Access Permissions
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Microsoft Outlook 2010 & 2013 cannot set automatic reply settings

Hello,
We cannot seem to set automatic reply's within outlook 2010 & 2013. We have an exchange server 2010. We
can setup automatic reply through OWA absolutely fine. The error that we receive is 'Your automatic reply settings cannot be displayed because the server is currently unavailable. Try again later.
However we can setup out of office on any other office version below 2010 fine. We have run through
a number of tests and have come to the conclusion that the auto discover service is not configured correctly. I have been told to run through the following
"We need to make sure the IIS service is assigned to the certificate which includes mail.mydomainname.co.uk
name:
Enable-ExchangeCertificate -Thumbprint 62C247B3BD081D0A8B074D4A928A76E6DA3BABBA -Services
POP,IMAP,SMTP,IIS
Then restart IIS service
to apply the changes.
If the user is connect
to mailbox from external environment as your test results, it is recommended to add the autodiscover.mydomain.co.uk name in your certificate with IIS service. If so, the autodiscover
service can be accessed successfully in your posted second steps(https:/autodiscover.mydomain.co.uk/autodiscover/autodiscover.xml). Alternatively, if you don’t want to change your certificate configuration, we need to create a new SRV record for mail.mydomainname.co.uk
to make your autodiscover succeed in last steps of Srv Record lookup method".
So I followed this and opened Exchange Managemnet Shell and ran the following.....
'Enable-ExchangeCertificate -Thumbprint 62C247B3BD081D0A8B074D4A928A76E6DA3BABBA -Services POP,IMAP,SMTP,IIS'
The following output was displayed:
"VERBOSE: Connecting to SERVER2011.EXCHANGE.local
VERBOSE: Connected to SERVER2011.EXCHANGE.local.
[PS] C:\Windows\system32>Enable-ExchangeCertificate -Thumbprint 62C247B3BD081D0A8B074D4A928A76E6DA3BABBA -Services POP,I
MAP,SMTP,IIS
WARNING: This certificate will not be used for external TLS connections with an FQDN of 'SERVER2011.EXCHANGE.local'
because the CA-signed certificate with thumbprint '71ADF367E190E269C1036BBF4A09C55E62536791' takes precedence. The
following receive/send connectors match that FQDN: Default SERVER2011.
WARNING: This certificate will not be used for external TLS connections with an FQDN of
'mail.companyname.co.uk' because the CA-signed certificate with thumbprint
'67ECB1A383CBD05424C58F6A5E753C9377F49D3D' takes precedence. The following receive/send connectors match that FQDN:
Windows SBS Internet Receive SERVER2011, Fax/Printer.
Confirm
Overwrite the existing default SMTP certificate?
Current certificate: '67ECB1A383CBD05424C58F6A5E753C9377F49D3D' (expires 09/08/2015 09:06:17)
Replace it with certificate: '62C247B3BD081D0A8B074D4A928A76E6DA3BABBA' (expires 06/08/2015 17:05:22)
[Y] Yes [A] Yes to All [N] No [L] No to All [?] Help (default is "Y"):"
I opened up 'Internet Information
Services (IIS) Manager to find 2 Server Certificates issues to 'mail.companyname'
with the certificate hash' 62C247B3BD081D0A8B074D4A928A76E6DA3BABBA' and '71ADF367E190E269C1036BBF4A09C55E62536791'.
I opened up the Exchange Management
Console to confirm that the IMAP, POP, IIS, and SMTP services are bound to both of the certificates for 'mail.companyname'.co.uk
I need to know if it is okay to proceed in replacing the certificate and running this
command.
Thank you

Hi,
We have this problem with some of our users, in that they get the server unavailable error when trying to activate the out of office.
In our case this is because the Proxy is blocking the connection from the PC to the Exchange, so we just go to Internet Options - Connections - LAN Settings - Advanced (under proxy server) then just add *.domain.com into the Exceptions box at the bottom.
This seems to resolve the issue and allow them to set their out of office. The only reason this reoccurs for these users is because their roaming profile for some reason won't save the proxy settings, which is a different issue.
Hope this helps.

In Exchange 2013 i cannot open mails with attachments greater than 19.6 MB in EWS or OWA

Hello,
i have in Exchange 2013 CU3 on Windows 2012 the following problem :
When backup mails using EWS i get the message " EWS Error Code : ErrorMessageSizeExceeded." in mails with attachments greater than 20.137 KB ( 19.6 MB).
Then I checked all the settings of the EWS , but the defaults are already significantly higher than these 19.6 MB (Base64 approximately 26.5 MB)
web.config ( maxAllowedContentLength = " 85000000 ").
Settings of the MaxSendSize and ReceiveSize are 300MB .
All requestfiltering settings in IIS are set to 85MB.
When i access via EMS or OWA , file attachments over 19.6 MB can not be opened .
However, the preview shows in OWA the correct mail including attachment and it can be saved from the preview up to the set maximum size.
By double clicking on an email in OWA bigger than 19.6 MB i get the following error message:
"Error : Your request can not be completed right now Please try again later . . "
Send and receive mail can also be up to maxsize .
When accessing via Outlook , this problem does not occur.
i hope anyone here can help me
Thanks in advance

Hi,
To change the maximum message size for Outlook Web App clients, you need to change the value of
maxAllowedContentLength, maxRequestLength and both instances of
maxReceivedMessageSize by editing %ExchangeInstallPath%ClientAccess\Owa\web.config in notepad.
To change the maximum message size for Exchange Web Services clients, you need to change the value of
maxAllowedContentLength and all instances of maxReceivedMessageSize="67108864" in %ExchangeInstallPath%ClientAccess\exchweb\ews\web.config.
When you are finished, save and close the Web.config file. Also need to restart IIS by running the following command:
IISReset /noforce
For more information about Configure Client-Specific Message Size Limits on Client Access Servers, please refer to:
http://technet.microsoft.com/en-us/library/hh529949(v=exchg.150).aspx
Thanks,
Winnie Liang
TechNet Community Support

Exchange 2013: how to set up multiple domain for OWA and ECP

Exchange 2013 on Windows 2012R2
Currently we have set this up using the guide below:
http://mouzzamh.wordpress.com/2013/02/04/accessing-owa-from-multiple-domain-url/
We can access OWA and ECP using the internal IP address/owa or ECP but when we use the URL it fails.
We gave it an external IP address as well just to check if it will externally since the external DNS are pointing to the correct records: same issue it only works on IP address/owa or /ecp
We were able to follow the guide from start to finish including the certs..
The only difference on the guide and our exchange IIS environment for the new website is when he mentioned "Under IIS Settings / ISAPI and CGI Restrictions" we only have "ISAPI filters"...." ISAPI and CGI Restrictions" is only
applicable to the default and backend website..
Also, when the guide points to the path, should it be the new website path?
Or maybe to avoid confusion, can anyone guide me on how to do it or any other guide that helped you if ever you had the same issue as mine?
Thanks.

Hi,
Please run the following to check your OWA virtual directories for all web sites:
Get-OWAVirtualDirectory | FL Identity,*URL*,path
Personal suggestion, please consider to deploy another new CAS server. Then we can configure different OWA URLs in different servers. And pointed mail.domain.com and webmail.domain.com to two CAS servers respectively.
Regards,
Winnie Liang
TechNet Community Support

Exchange active sync cannot connect to server after migration mailbox user from exchange 2007 to exchange 2013 coexistence

Hello, everyone, my name is rafl
I have a problem with exchange 2013 active sync.
I have installed exchange 2013 coexistence with legacy exchange 2007, I have to migrate user mailboxes: [email protected] from exchange 2007 to exchange 2013.
but any problem with active sync connection on the mobile device after moving mailbox user. I reconfigure the exchange ActiveSync external connection domain (latest.domain.com) on mobile device replacing legacy exchange ActiveSync external connection domain
(legacy.domain.com)
the process of moving mailboxes successfully without error.
Access OWA for exchange 2007 and exchange 2013 is running normally
access mail from Outlook running normally
Certificate request has been installed and has no problem with it
The OWA virtual directory is configured for internal and external connections and different from the legacy exchange
The autodiscover virtual directory is configured for internal and external connections and different from the legacy exchange
ActiveSync virtual directory is configured for internal and external connections and different from the legacy exchange
user mailboxes are still on exchange 2007 is not problematic.
only problem with Exchange Active Sync on mobile devices, where I set up an email with android, iphone, windows phone. the error message: cannot connect to the server.
but, if I create a new user and create user mailboxes directly in exchange server 2013, ActiveSync can run without error on mobile device, access through OWA, MsOutlook, Outlook Anywhere also run normally.
only the results of user migration from exchange 2007 to exchange 2013 which is troubled with exchange ActiveSync connection.
any ideas for this problem, and what should I check on the exchange server ..?

i have run the activesync test connectivity and get some error :
Testing TCP port 443 on host domain.co.id to ensure it's listening and open.
The specified port is either blocked, not listening, or not producing the expected response.
A network error occurred while communicating with the remote host.
Elapsed Time: 3091 ms.
Testing TCP port 443 on host autodiscover.domain.co.id to ensure it's listening and open.
The specified port is either blocked, not listening, or not producing the expected response.
A network error occurred while communicating with the remote host.
Elapsed Time: 21072 ms.
Testing TCP port 80 on host autodiscover.domain.co.id to ensure it's listening and open.
The specified port is either blocked, not listening, or not producing the expected response.
A network error occurred while communicating with the remote host.
Elapsed Time: 21049 ms.
I have allowed access to port 443 (https) and 80 (http) on the firewall and re-run testconnectivity, but still with the same results. if I enable active sync for users who created directly in Exch 2013 there is no problem with the ActiveSync, just a problem
for users who moved from Exch 2007 to Exch 2013. @Android, iPhone, and Blackberry the error message "cannot connect to the server"

Exchange 2013 OWA: Cannot set auto reply in shared mailbox

Similar Messages

Maybe you are looking for