Unable to insert hyperlinks in Exchange 2007 OWA messages

Hi, we have recently moved to Exchange 2007 OWA and users are unable to insert links to shared files on the network. I was wondering if there might be something in our Windows 7 GPO that is preventing this from happening?

do you mean they cannot see the network path or that they are not able to type
\\networkshare\share ?
If first one,please check Outlook Web app policy and enable/customize Direct file Access.
Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you. Thank you! Off2work

Similar Messages

How to get current user in Exchange 2007 OWA customization page?

Hi,all
I customize an ASPX page(smsconfig.aspx) in Exchange 2007 OWA( this file in ..\Exchange\ClientAccess\OWA\smsconfig.aspx, I don't modify registry.xml & web.config).
My Exchange 2007 OWA has been configurated with Forms-Based Auth.
https://mail.myexchange.com/owa/smsconfig.aspx The page works fine, but it cannot get current logon user with HttpContext.Current.User.Identity or
UserContext.MailboxIdentity or UserContext.LogonIdentity
<%@ Page language="c#" AutoEventWireup="false" Inherits="Microsoft.Exchange.Clients.Owa.Core.OwaPage" %>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<%@ Import namespace="Microsoft.Exchange.Clients"%>
<%@ Import namespace="Microsoft.Exchange.Clients.Owa.Core"%>
<%@ Import namespace="Microsoft.Exchange.Clients.Owa.Premium"%>
<%@ Import Namespace="System" %>
<%@ Import Namespace="System.Data" %>
<%@ Import Namespace="System.Data.SqlClient" %>
<%@ Import Namespace="System.Xml" %>
<%@ Import Namespace="System.Collections.Generic" %>
<%@ Import Namespace="System.Text" %>
<script runat="server">
。。。(my codes in here)
</script>
thanks for your help.
Your Passion.My Potential.

Microsoft.Exchange.Clients.Owa.Core.OwaContext.Current.UserContext.LogonIdentity.PrimarySmtpAddress
Высказанное мною здесь - мои личные взгляды, а не позиции корпорации Microsoft. Вся информация предоставляется "как есть" без каких-либо гарантий.

Exchange 2007 OWA sends attachments Outlook connector clients cannot send attachments.

Exchange Server 2007 SP1 + Rollup ***Problem with sending email attachments from Outlook 2007***
* Inbound mail arrives in OWA and Outlook normally with and without attachments.
* OWA email to external email account with attachment goes thru successfully.
* Outlook 2007 sends to an external email address with attachments the message does not arrive at the external mailbox. The messages leave Outbox but are never delivered. The messages appear in Sent Items also.
* Outlook sends non attachment emails to external addresses successfully.
* Outlook sends email attachments to local domain accounts fine.
#1 Exchange Server on Server 2013 fully patched problem commences. Exchange Server on version less than first RTM release of Exchange 2007.
#2 Outlook profiles were changed to see if that is the problem.
#3 Upgraded Exchange to SP1 and Rollup 10(Rollup was autodownloaded by MSUpdate)
#4 Ran EXBPA nothing of any interest in the report.
--Unified Messaging not configed (Done nothing)
--SenderID (Re-enabled) I had shut all of the antispam to eliminate these.
-- Junk Store threshold not configed (No change)
Any suggestions to get Outlook clients capable of sending attachments configured.
Thx,
-Scot

Hi Scot,
Providing some information on Poison Queue:
The poison message queue is a special queue that's used to isolate messages that are determined to be harmful to the Exchange system after a transport server or service failure.
The messages may be genuinely harmful in their content and format.
Alternatively, they may be the results of a poorly written agent that has caused the Exchange server to fail when it processed the supposedly bad messages.
The poison message queue is typically empty. If the poison message queue contains no messages it doesn't appear in Queue Viewer or
Get-Queue results. The messages in the poison message queue are never automatically resumed or expired. Messages remain in the poison message queue until they're manually resumed or removed by an administrator.
According to the description above, I suspect Outlook 2007 changed the email's format when send email with attachment. The reason as below:
If the original email's (with attachment) content or format is harmful to the Exchange 2007 server, it will go to the Poison Queue when sending via OWA. However it didn't, sending via OWA is perfect. So I suspect it is an issue on the Outlook 2007
client side.
Please using Pipeline Tracing to verify whether there is something changed during transmission.
More details in the following article:
Using Pipeline Tracing to Diagnose Transport Agent Problems
http://technet.microsoft.com/en-us/library/bb125198(v=exchg.80).aspx
If it is convenient, I suggest doing following tests to narrow down this issue:
Note: Same content, same attachment, same format.
1. Please using Outlook 2010/2013 or others' Outlook clients for testing.
2. Please change to another format for testing. More details in the following article:
Change the message format to HTML, Rich Text, or plain text
http://office.microsoft.com/en-001/outlook-help/change-the-message-format-to-html-rich-text-or-plain-text-HP001232996.aspx
Thanks
Mavis
Mavis Huang
TechNet Community Support

Exchange 2007 OWA Error after installing Service Pack 3 (MSExchange OWA event 65)

Hi everyone, I have multiple servers in Exchange 2007 SP1, Windows Server 2003 SP2 64bit.
I installed SP3 and RU15 a CAS / HUB server and now I access OWA, showing the below error:
Outlook Web Access did not initialize. There has been an event for the system administrator can resolve the problem. Contact the support of the organization.
Object reference not set to an instance of an object.
Request
URL: https: // mailserver01: 443 / owa / auth / error.aspx url = https: // mailserver01 / owa / & reason = 0
Exception
Exception type: Microsoft.Exchange.Clients.Owa.Core.OwaInvalidConfigurationException
Exception message: Object reference not set to an instance of an object.
Call stack
in Microsoft.Exchange.Clients.Owa.Core.OwaConfigurationManager.CreateAndLoadConfigurationManager () in Microsoft.Exchange.Clients.Owa.Core.Globals.InitializeApplication () in Microsoft.Exchange.Clients.Owa.Core.Global.ExecuteApplicationStart (Object sender,
EventArgs e)
Inner Exception
Exception type: System.NullReferenceException
Exception message: Object reference not set to an instance of an object.
Call stack
in Microsoft.Exchange.Clients.Owa.Core.Configuration.CheckPublicFolders (ADSystemConfigurationSession session, ADObjectID [] pfdbIds, Boolean & allLegacy, Boolean & allLater) in Microsoft.Exchange.Clients.Owa.Core.Configuration..ctor (ADSystemConfigurationSession
session, String virtualDirectory , String WebSiteName, ADObjectID distinguishedName, Boolean isPhoneticSupportEnabled) in Microsoft.Exchange.Clients.Owa.Core.OwaConfigurationManager.LoadConfiguration () in Microsoft.Exchange.Clients.Owa.Core.OwaConfigurationManager.CreateAndLoadConfigurationManager
In server events next event is logged
Event Type: Error
Event Source: MSExchange OWA
Event Category: ADNotifications
Event ID:. 65
Date: 12/27/2014
Time: 7:20:54
User: Not available
Team: mailserver01
Description:
There was an error loading the configuration parameters of Outlook Web Access. Virtual directory "owa". Website: "Default Web Site".
Error message:
"Object reference not set to an instance of an object."
HOW CAN I SOLVE THIS?
thank you very much
Microsoft Certified IT Professional Server Administrator

Hello
everyone,
thank you
for
answering,
finally
opened
with
Microsoft
support
case
and
showed
me
that
delete
servers
from
ADSEDIT.
I deleted
the
servers
that
should
not
be
and
immediately
everything
started
to
work
properly
Many
thanks to
all
for
the
help
Microsoft Certified IT Professional Server Administrator

Exchange 2007 OWA with S/MIME installed Context Menu Disspear

Hi Guys,
We are experiencing the following issue with Exchange 2007 SP3 OWA when S/MIME control is installed:
Context Menu and Email Format are grey out
Does anyone know if this behavior is by design??
Best Regards
Federico Giampietri
Federico Giampietri Latamsupport IT Infrastructure Services

Hi,
I tested in my lab, Exchange 2007 SP3. The result is the same with you.
Without the S/MIME
control, Cut, Copy, and Paste from the Context Menu worked as expected and I could change email format . When I installed the
S/MIME
Control, the behavior with the Context Menu was reproducible, and email format is greyed out, but I could use Ctrl +X/C/V to cut, copy and paste.
I searched through internal channel and found this behavior is by design. However, as a workaround for choosing Cut, Copy, or Paste from the Context Menu, we can use Ctrl +X/C/V to cut, copy and paste.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Belinda Ma
TechNet Community Support

Microsoft Exchange 2007 owa data storage exception

Good morning,
we have MS Exchange 2007 server. I have a problem with the owa service and particularly with one user account. From outlook I can see and navigate in all folders. From owa when I try to navigate in few folders I receive the following exception: Exception type:
Microsoft.Exchange.Data.Storage.CorruptedDataException Exception message: The configuration object data is corrupted. Field=UserConfigurationType.
Call Stack: Microsoft.Exchange.Data.Storage.UserConfiguration.BuildConfigurationFromQueryItem(Folder, folder, Object[] row) Microsoft.Exchange.Data.Storage.UserConfiguration.GetIgnoringCache(UserConfigurationManager manager, Folder folder, String configurationName,
UserConfigurationTypes freefetchType) Microsoft.Exchange.Clients.Owa.Core.UserConfigurationUtilities.GetFolderConfiguration(String configurationName, UserContext userContext, StoreId folderId) Microsoft.Exchange.Clients.Owa.Basic.ListViewPage.OnLoad(EventArgs
e) Microsoft.Exchange.Clients.Owa.Basic.MessageView.OnLoad(EventArgs e) System.Web.UI.Control.LoadRecursive() System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
Any help will be appreciated.
Thanks in advance,
Carlo

Hi,
There are corruptions on the specific mailbox. The cause of my last case for your reference:
The below property can be missing from the mailbox:
Tag: 0x7C060003
Type: PT_LONG
Property Name(s): PR_ROAMING_DATATYPES, PidTagRoamingDatatypes
DASL: http://schemas.microsoft.com/mapi/proptag/0x7C060003
To get to the property of the mailbox, we used MFCMAPI application.
• Launch MFCMAPI.exe by double clicking it (on client machine where we have logged in as the user).
• Click on SessionLOGON in the menu bar
• Double click on the mailbox under the display name column, you will get another window.
• Expand ROOT CONTAINERTOP OF INFORMATION STORE
Find the corrupted folders’ properties.
Thanks,
Simon Wu
TechNet Community Support

How to export an exchange 2007 owa certificate from production to lab environment

I'm setting up an Exchange 2007 Lab but I have a trouble regarding exchange's certificate
Note: My lab environment is not conected to internet
I've followed the next link but it doesn't work
https://www.digicert.com/ssl-support/pfx-import-export-exchange-2007.htm
Once I finished all the steps if I run the next powershell command get-excahangecertificate I see that my exchange certificate has the status as unknown
I'm not sure if the problem is related with the server is not conected to internet, so exchange is not be able to check the status of the certificate.
I've tried to turn off the Check for publisher’s certificate revocation option on the server
To do this, follow these steps.
Start Internet Explorer.
On the Tools menu, click Internet Options.
Click the Advanced tab, and then locate the Security section.
Click to clear the Check for publisher’s certificate revocation check box, and then click OK.
After the update rollup installation is complete, turn on the Check for publisher’s certificate revocation option.
But it still not working
Could anyone help me?
Thanks in advance

Hi Pardo,
According to your description, I understand that the exchange certificate cannot work and display unknown status after import it.
If I misunderstand your concern, please do not hesitate to let me know.
Depending on the results of “Get-ExchangeCertificate | FL”, please pay attention to following points:
1. RootCAType: Registry
“An internal, private PKI root CA that has been manually installed in the certificate store.”
2. Status: Unknown
“This status generally indicates that the status of the certificate cannot be verified because the certificate revocation list (CRL) is unavailable or this server cannot connect to it.”
The reason why it failed is that internal Exchange server cannot connect to CRL. As you mentioned, exchange can’t be able to check the status of the certificate.
More information about Certificate Use in Exchange Server 2007, please refer to
Certificate Fields and Configuring Access to the Certificate Revocation List
section in below link:
http://technet.microsoft.com/en-us/library/bb851505(v=exchg.80).aspx
However, we can renew a certicate from local CA:
http://technet.microsoft.com/en-us/library/bb310781(v=exchg.80).aspx
Best Regards,
Allen Wang

Onsite Scanner Unable To Send Documents Through Exchange 2007 Server (SBS 2008)

I have an SBS 2008 server complete with Exchange 2007 in house and have configured Exchange 2007 to use the Exchange Online Protection (EOP) to process mail for malware, etc. This setup has worked great for the last year or so with no issues.
However, all of a sudden in the last couple of weeks our onsite copier can no longer send documents through email to anyone within the organization. The copier is a Kyocera TaskAlfa 3050CI and exists with the same network. The copier can scan
to a network folder without issue.
If I change the SMTP settings to use a gmail account instead of a local account I can send mail to outside email address. Even with this changed though I still can't send to our domain addresses.
I tried running a message trace from the Exchange Management Console but it doesn't find anything for hte given subject or date/time when I scanned the document.
I am not exactly sure what I should be checking or what piece of the puzzle is causing the problem here. Any ideas on what might be happening or how to correct it?
Thanks so much!

Hi,
Any update? Would you please let us confirm some questions as Howtodo mentioned. Please feel free to let us
know.
Based on your description, it seems that only the copier can’t send documents via emails. On your SBS 2008
environment, please check if some user accounts encounter the similar issue. In other words, did users also can’t send emails attached with documents? If the email was attached with a small size document, will the same result?
In addition, can find any relevant error or events?
Hope this helps.
Best regards,
Justin Gu

Unable to insert hyperlinks after reinstalling CS6

Hi, I recently got a new computer and just reinstalled CS6. Since the installation, I've been having trouble with the link panel. Now when I open it, there is no space to enter a URL. I've attached a screenshot (the links you see were already saved in the file before the re-installation). I can still use the function that converts all URLs in the file to hyperlinks, but as I want to link individual words without showing the URL, this isn't sufficient. I've also already tried deleting my InDesign preferences file when starting up, and that hasn't changed anything. Any tips would be appreciated!

Try the Hyperlinks panel. (Window > Interactive > Hyperlinks)
The Links panel is for objects only that are linked, not embedded.
us-hh

E71 unable to sync Calendar with Exchange 2007

I updated my MfE client from 2.04 to 2.09.158 but that did not help. When I look at my admin log file, I see these messages:
failed to create Calendar sync command (error=-1)
Mail For Exchange Error -15000
Mail For Exchange Error -15000
When I am trying to sync the phone, it simply says: System Error. Please try again later.
I tried the trick where you set your date/time on the phone off into the distant future, and then delete all calendar events from before that date, and then set the current date back and run Synchronize, but it didn't make a difference.
Any suggestions?
Thanks,
Hal

I seem to be having a similar problem, calendar initially synced up, but after a while though I do get the invite mails but they dont get updated to calendar even if I accept them. I am running mfe 2.0.7. Any inputs would be appreciated.
thanks
Manish

Mail + Exchange 2007 + Move message doesn't work

I have my Apple mail program setup to use my work Exchange account and for the most part it works great. However, when I try to move mail from my Inbox to a subfolder, it fails. I've tried dragging the mail to the folder and I've tried going through the right click menu. I've also tried different folders and different pieces of mail with the same result. I can move messages with my iPhone and with my work PCs Outlook client. Lastly, I've checked the main network ports on the Exchange server to verify that my communications with the server are not being blocked. Any ideas on how to fix this?

I've been looking at a lot of the posts concerning this issue and I am posting my console messages to each of them. This is the console message I get when trying to delete a message:
9/16/09 2:45:03 PM Mail[540] * Assertion failure in -[EWSCopyItemsResponseOperation executeOperation], /SourceCache/Message/Message-1076.1/MessageStores.subproj/EWSCopyItemsResponseO peration.m:44
Copying an EWS message returned success, but didn't have 1 item in the response message, got 0 items; most likely one of the Exchange Server components is not running Service Pack 1 Update Rollup 4
0 Message 0x00007fff80498828 -[MFAssertionHandler _handleFailureWithPreamble:description:arguments:] + 137
1 Message 0x00007fff8049878d -[MFAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 220
2 Message 0x00007fff803de753 -[EWSCopyItemsResponseOperation executeOperation] + 519
3 Message 0x00007fff804a6a57 -[MonitoredOperation main] + 229
4 Foundation 0x00007fff8614411a -[__NSOperationInternal start] + 673
5 Foundation 0x00007fff86143dd8 ___startOperations_block_invoke2 + 99
6 libSystem.B.dylib 0x00007fff83f5ecf6 dispatch_call_block_andrelease + 15
7 libSystem.B.dylib 0x00007fff83f3d1e9 dispatch_workerthread2 + 231
8 libSystem.B.dylib 0x00007fff83f3cb28 pthreadwqthread + 353
9 libSystem.B.dylib 0x00007fff83f3c9c5 start_wqthread + 13
)

Exchange 2013 + 2007 OWA coexistance not redirecting properly (HTTP 400)

Hello. I am using this document to funnel our new Exchange 2013 external traffic through an IIS ARR reverse proxy, much like we already do for MIcrosoft
Lync 2013 on this machine.
http://blogs.technet.com/b/exchange/archive/2013/08/02/part-2-reverse-proxy-for-exchange-server-2013-using-iis-arr.aspx
I followed this guide to a T. especially the part on the page 2 that I linked above about creating the legacy.domain.com server farm and URL rewrite rule. This
IIS ARR proxy seems to work fine for Outlook Anywhere, ActiveSync, OWA if the user's mailbox is on the Exchange 2013 server, but it does not work if an OWA user logs in with a mailbox on 2007.
When the user has a mailbox on 2007, after logging into OWA they get HTTP 400 error. The URL bar in the browser is changed to https://legacy.domain.com/owa/auth/owaauth.dll
The Exchange 2007 server IIS logs show this:
70.x.x.x, -, 11/1/2014, 9:45:48, W3SVC1, MAIL, 10.1.1.3, 0, 523, 132, 400, 0, POST, /owa/auth/owaauth.dll, -,
I can't figure out why this is happening. DNS is correct. legacy.domain.com points to the 2007 Exchange server. webm.domain.com points to the
Exchange 2013 server.
Any ideas?

Doing more testing, I almost think the Exchange 2007 server keeps redirecting. So the HTTP 400 is because when you hit legacy.domain.com, it redirects
to webm.domain.com which redirects back to legacy.domain.com and vice versa.
I put a test.txt file in the Exchange 2007 owa virtual directory and I cannot access it in any browser. I tried https://legacy.domain.com/owa/test.txt and
It redirects me to https://webm.domain.com(Exchange 2013). I can however go
one level (or more) deep on the legacy server and get a file such as https://legacy.doamin.com/owa/8.3.342.1/themes/base/logon.css and
in the browser I see the code (both externally AND internally, so I know DNS and firewall is working).
I can't find anywhere on IIS 6.0 on the Exchange 2007 server where any kind of redirection is taking place though. Virtual Directory properies for owa say
"A directory located on this computer: "C:\Program Files\Microsoft\Exchange Server\ClientAccess\owa" Enable default content page is checked with default.aspx but I looked at default.aspx in notepad and I don't see ANY code telling it to
redirect.
In Exchange 2007 management console OWA internal URL and External URL both sayhttps://legacy.domain.com/owa .
I have no idea what is causing this redirection. I did an iisreset and also recycled the OwaAppPool and no change.

Migrate from Exchange 2007 to 2013 without modifying client devices

Let's use contesso.com as an example. Let's say the Exchange 2007 server's internal and external
name are currently mail.contesso.com. Now I am going to introduce a new Exchange 2013 server named mail2.contesso.com. The Exchange Server Deployment Assistant says that we should make the external DNS entry point mail.contesso.com to the 2013
server and legacy.contesso.com point to the 2007 server. That takes care of external clients. I don't understand how internal clients will find the correct server because they are all configured for mail.contesso.com which internally points to
the 2007 server. We have over 200 users with multiple devices. We do not want to be forced to create new Outlook profiles or change the configuration of their mobile devices.
Thanks,
Tina
Tina M. White Boundless Data

Hi,
Mail.contesso.com -> Exchange 2013 OWA/ActiveSync/OA
Legacy.contesso.com -> Exchange 2007 OWA/ActiveSync/OA
Autodiscover.Contesso.com
Make sure the Redirection settings are configured properly.
Regards,
Simon Wu
TechNet Community Support

Exchange 2007 to Exchange 2010 URL redirection

Hi,
I am performing exchange 2007 to exchange 2010 migration in co-existence. When i am accessing exchange 2010 OWA and logged in with exchange 2007 user then silent redirection is happening.
But when i am accessing the exchange 2007 OWA and logged in with exchange 2010 user, this is asking for manual redirection to exchange 2010 OWA url.
Please suggest the silent redirection method from exchange 2007 to exchange 2010 URLs.
All exchange servers are in same active directory site.
Regards Sunny Chauhan

Hi Sunny,
You can run the below command to resolve this error
Set-OWAVirtualDirectory <CAS2007>\OWA* -LegacyRedirectType Silent
The LegacyRedirectType parameter specifies the type of redirect that Outlook Web App uses to a legacy Client Access server or front-end server when forms-based authentication isn't used on the Exchange 2013 Outlook Web App virtual directory.
The following values are valid for this parameter:
•Silent
•Manual
Silent causes a standard redirect. Manual displays an intermediate page that shows the legacy URL so that users can change their bookmarks.
Please mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you.
Regards,
Sathish

Exchange 2007 - User getting 404 File or directory not found

Exchange 2007 OWA 404 - File or directory not found. I have two database on the same server and this problem is only affecting one database and the user in the other database is fine. I did a test and move the user to the other database and I gave
myself full access to the user mailbox and use OWA (Change mailbox) to access other user and later login as the user itself and everything is fine. I have thousands of user, and doing this is time consuming. Anythough on this?

Hi Tony,
According to the description, I notice that you have a problem on OWA. When logon OWA with users from specific database, get error "Exchange 2007 OWA 404 - File or directory not found".
I suggest check following points.
1. Please make sure OWA Virtual Directory in IIS is available.
2. Please make sure the OWA Virtual Directory in IIS has configured Basic Authentication by default.
3. Please try to re-build OWA VD for testing. I saw someone solved this issue by re-building OWA VD.
4. Since you have tested, moving mailbox to another database can auto-fix this issue, please also try to follow Ed to solve this issue.
Thanks
Mavis Huang
TechNet Community Support

Unable to insert hyperlinks in Exchange 2007 OWA messages

Similar Messages

Maybe you are looking for