Exchange 2007 and Coldfusion 9 - connection problem

Coldfusion 9
Exchange 2007 (hosted at intermedia.net)
We've been using the cfexchangecalendar tag for some time to post calendar events on behalf of our users.  It stopped working.  No events were being added and no error messages were reported.  There was some mention "around the net"
that WebDav was no longer supported.  But it was verified that Intermedia was still supporting WebDav on their Exchange 2007 server.  They've been pretty good about helping debug this problem until it came to CF.  Adobe is just so-so about helping
and also stop short of Exchange support.  The only thing I know to do is just keep asking the question until someone is curious enough to jump in and ask me the right questions.
The following is the CF code I use;
<cfexchangecalendar action="create"    
    username="exch016\user_name"  
    password="password"
mailboxName="exch016\user_name"
    server="owa016.msoutlookonline.net/owa" 
protocol="https"
port="443"
    event="#sEvent#" 
    result="theUID">
This code is supposed to insert a calendar event for "user_name".
I get various error messages from 401, 440, and even a 501.  I also get some verbose messages (depending on how I set up debugging) stating the was an error connecting with HTTP/HTTPS or verify the server, user name, and password.
I've tried http/port 80 and https/port 443.  The code was set to use http/80 when it was working, but Intermedia tells me that they only accept https/443.
I can login using the browser and see all my users, etc.  I can use the cfhttp tag and get to the server and it returns a login page.
I checked the certificates on my server and found a duplicate and deleted it. 
I am willing to try anything to provide any information someone might need to make this problem more clear.
What I don't need is a link to an Adobe/Coldfusion info page or generic Exchange info.  If you can't help, you can't help.

Are you getting any NDR? Post it.
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.

Similar Messages

  • Exchange 2007 and 2010 with Unity Connection 8.6

    Hi all,
    We have unity connection 8.6 and exchange 2007 currently in place and runnign fine. I am ready to start migrating mailboxes over to our new exchange 2010 farm and as such we will be in co-exsistance with exchange 2007 and 2010 for awhile. What are the steps or procdures to also include exchange 2010 with the 2007 in unity connections? Currently under Smart Host is the IP address of our exchange 2007 server.
    Thank you.

    Hi,
    This depends on how you plan on performing the migration. I would suggest the following:
    -Creating a new unified messaging service for Exch 2010. You can re-use the same service account name as long as you completed the configuration steps for that integration.
    -As you move over user's mailboxes from 2007 to 2010, you can delete the 2007 UM service and add the new 2010 UM service. If you want to change many users at a time you'll need to use bulk administration to change them. If you use BAT to change accounts, see the link below where I have listed them out for another CSC user.
    -You can change the Smart Host setting once you have configured the Exch 2010 enviornment to handle your main corporate mail (changing the MX records to point to a 2010 Edge Transport).
    Changing the UM service with BAT:
    https://supportforums.cisco.com/message/3572200#3572200
    Good luck.

  • ActiveSync in Exchange 2007 and 2013 Coexistence

    Hi,
    I have exchange 2007 and 2013 coexisting (exchange 2007 sp3 update rollup 13/exchange 2013 SP1)
    owa works fine from inside and outside, only that it requires users to authenticate twice when connecting from the external.
    autodiscover works well for users on both 2007 and 2013
    I have a public SAN certificate from verisign with 2 names on it, mail.mydomain.com and legacy.mydomain.com
    I have A records configured for both names on my public DNS and internal DNS
    THE ISSUES
    testing activesync from testconnectivity.microsoft.com works fine when i run the test using a mailbox on Exch2013 but fails for mailbox on Exch2007.
    New users on exch2007 & exch2013 are not able to setup email on their devices (blackberry and windows mobile),
    Existing users on exch2007 can no longer receive mails on their mobile devices
    URLs
    Exchange 2007
    Exchange 2013
    Internal owa
    mydomain.com/owa
    mail.mydomain/owa
    External owa
    legacy.mydomain.com/owa
    mail.mydomain.com/owa
    AutoDiscover
    mail.mydomain.com
    mail.mydomain.com
    EWS
    legacy.mydomain.com
    mail.mydomain.com
    ECP
    mail.mydomain.com
    Internal ActiveSync
    legacy.mydomain.com
    mail.mydomain.com
    External ActiveSync
    $null
    mail.mydomain.com
    OutlookAnywhere
    legacy.mydomain.com
    mail.mydomain.com
    I expect that users on exch2013 would be able to setup their mobile devices as the connectivity test completes successfully but it still does not.
    Any help on this would be much appreciated ..
    Richard ..
    ..forever is just a minute away*

    You don't need to use a legacy URL for ActiveSync in Exchange 2013.  It will proxy ActiveSync for Exchange 2007 just fine.  In fact, ActiveSync is usually the protocol that gives you the least amount of trouble in a transition.  I recommend
    you configure your URLs for the proxy configuration and point everything to Exchange 2013 CAS.
    http://blogs.technet.com/b/exchange/archive/2013/01/25/exchange-2013-client-access-server-role.aspx
    http://technet.microsoft.com/en-us/library/bb310763(v=exchg.141).aspx
    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

  • Getting UConn 8.5 to work with both Exchange 2007 and 2010

    According to the document below, I should be able to set up one Unified Messaging service to access mailboxes on both Exchange 2010 and Exchange 2007 servers.  I setup my service to point to 2010 CAS servers and I can access 2010 mailboxes, but testing 2007 mailboxes comes up with an http 200 error.  If I setup the CAS server as 2007, I can access 2007 mailboxes, but get an error on 2010 mailboxes.  This will be a real pain if I can't do this with one service.  I don't want to have to keep Unity Connection updated as users get moved from 2007 to 2010!  Anyoe know how to do this?
    http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/unified_messaging/guide/85xcucumg020.html#wp1198171        

    I got this to work!  My Unified Messaging Service was originally setup to Specify an Exchange Server.  That is where I had put the  DNS name of the  CAS server (and that DNS entry pointed to several CAS servers).  I changed the Service to Search for Exchange Servers instead and used that same DNS name in the Active Directory DNS Domain Name.  When I do the test of this service, it tells me it Failed to locate a Domain Controller via DNS, but that is just informational.  It also says it successfully connected to the Exchange CAS server with the autodiscover.xml.  Now my mailboxes on both Exchange 2007 and 2010 are able to receive voicemail messages with this one Service configured.

  • Exchange 2007 and outlook 2010 frequent disconnects

    Hi,
    Im having issues on SBS 2008 with exchange 2007 and outlook 2010.
    Every so often users disconnect and outlook then requires them to put there password in but if you restart outlook all is fine till the next time its random aswell.
    I have checked in IIS if windows and basic authentication are enabled which they are.
    If i dont use outlook anywhere i still get this problem.
    I have looked on the internet but everything i try doesnt seem to help me any ideas ?
    Thanks

    Hi,
    Before going further, would you please let me confirm whether all users (with all Outlook) encounter this same
    issue? Did you install any update or any third-party application on the server before this issue occurred?
    à
    Im having issues on SBS 2008 with exchange 2007 and outlook 2010.
    Would you please let me confirm whether installed Exchange Server 2007 SP2 (or SP3)? Did you install all necessary
    Update Rollups for the Exchange Server 2007?
    Please type
    outlook.exe /safe in RUN to start Outlook in Safe Mode, then check if this issue still exists. Meanwhile, please navigate to the website which contains Exchange Virtual Directories in IIS Manager, then enable kernel-mode authentication for each directory
    and monitor the result.
    If any update, please feel free to let me know.
    Hope this helps.
    Best regards,
    Justin Gu

  • Free/Busy not working Exchange 2007 and 2013 co-existence

    Hi,
    I'm migrating our Exchange 2007 environment to Exchange 2013. Now I am in a co-existence environment where all the mailboxes except some test-users resides on Exchange 2007. Between Users on the same Exchange MBX Server athe FREE/BUSY Information sharing
    works correctly, but between Exchange 2007 and 2013 it's not working.
    I verified my settings and also the EWS virtual directory on 2007 CAS Servers using Get-WebServicesVirtualDirectory.
    The internal and the external URLs are set to https://legacy.mydomain.com/....
    What am I missing?
    Thanks & Kind Regards,
    Jürgen

    Hi,
    According to your description, I understand that the free/busy information between Exchange 2007 and Exchange 2013 is not available for your coexistence environment. To narrow down the issue, please check the following points:
    1. Does the issue happen to all users or specific users?
    2. Although a user on Exchange 2013 can't get free/busy information from a user on Exchange 2007, please confirm whether Exchange 2007 user can get free/busy information from Exchange 2013 users.
    3. Close Outlook and only access user mailbox from OWA to check whether the issue persists. For Outlook client,
    create a new Outlook profile
    to have a try.
    4. Please make sure the virtual directories settings are configured correctly in both Exchange 2013 and Exchange 2007.
    Virtual directories settings in Exchange 2007:
    http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-3-step-by-step-exchange-2007-to-2013-migration.aspx
    Certificate and Virtual directories settings in Exchange 2013:
    http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-2-step-by-step-exchange-2007-to-2013-migration.aspx
    5. Restart IIS service in Exchange server by running iisreset /noforce from a command prompt window.
    If possible, please run Test E-mail AutoConfiguration in Outlook to check whether the autodiscover service can get correct Availability service URL in the results. If there is any event logs, please collect some for further analysis.
    Regards,
    Winnie Liang
    TechNet Community Support

  • When I try to sign into photoshop elements I keep getting error code 400 connection error. I am connected to wifi and have no connection problems anywhere else. How do I fix this?

    When I try to sign into photoshop elements I keep getting error code 400 connection error. I am connected to wifi and have no connection problems anywhere else. How do I fix this?

    FRANK M
    What computer operating system is your Premiere Elements 9 running on? I will assume Windows 7, 8, or 8.1 64 bit for now.
    As for the Help Menu/Update way for updating, are you doing that with antivirus and firewall(s) disabled? If not, please do so.
    Do you have the 9.0.1 Update of the program installed? What version of Camera Raw do you have installed?
    Premiere Elements 9 is an older program where you can still do manual installs for that one and only Update. And, Camera Raw for 9 is no longer being updated.
    For the 9.0.1 Update
    http://www.adobe.com/support/downloads/detail.jsp?ftpID=4929
    Camera Raw (last update possible for 9) is 6.5
    Camera Raw-compatible Adobe applications
    Adobe - Adobe Camera Raw and DNG Converter : For Windows : Camera Raw 6.5 update
    Please review and consider the above, and then let us know the outcome.
    Thank you.
    ATR

  • Difference between Exchange 2007 and 2010

    Hello, 
    I want to know what are the differences between Exchange 2007 & 2010, i mean what was missing in 2007 which is addresses in 2010. Both from Administrator point of view and client point of view. How admins are going to benefit from 2010 and how clients
    will see changes in their outlook 2010 because of Exchange 2010? 
    Hasan

    Hello,
    Can you Please help me out, what is the Difference? 
    Difference between Exchange 2003 and 2007
    Difference between Exchange 2007 and 2010
    Thanks 

  • Exchange 2007 and 2013 coexistence

    Hi,
    we have exchange 2007 and 2013 coexistence. we have created a new url for 2007 legacy servers. Now, when using OWA url (now set for exchange 2013 server)  i am getting OWA exchange 2007 login page for exchange 2007 mailboxs.
    I was expecting exchange 2013 OWA page and then redirection to OWA 2007.
    Thanks

    Hello,
    Please check your DNS configuration and ISA/TMG rules.
    We recommend you use TMG or UAG.
    You can refer to the "TMG rules" section in the following article:
    http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-3-step-by-step-exchange-2007-to-2013-migration.aspx
    Cara Chen
    TechNet Community Support

  • I update my exchange server 2013 cu6 with exchange 2007 and my exchange 2013 db shutdown every 25 minute and recover. You have any hotfix I can use for this solution.

    I update my exchange server 2013 cu6 with exchange 2007 and my exchange 2013 db shutdown every 25 minute and recover. You have any hotfix I can use for this solution.

    Hi,
    From your description, you have deployed Microsoft Exchange Server 2013 and Microsoft Exchange Server 2007 in a co-existence environment. After you upgrade to CU6, databases unexpectedly shut down. In your case, here is a kb for your reference.
    Exchange Server 2013 databases unexpectedly fail over in a co-existence environment with Exchange Server 2007
    http://support2.microsoft.com/kb/2997209
    Hope this can be helpful to you.
    Best regards,
    Amy Wang
    TechNet Community Support

  • Coexistence Exchange 2007 and 2013 - Clients on 2013 cant connect to Outlook, OWA works fine

    Hi
    We are currently running all our users on Exchange 2007. I've installed Exchange 2013 on another hardware following several guides on coexistence between 2007 and 2013.
    I'm now testing with a few test users I've migrated from 2007 to 2013.
    Everything was working fine until I messed up with something. It's either the certificates and/or Exchange Web Services and/or activating Outlook Anywhere.
    Now, all my tests users on Exchange 2013 can connect and send/receive emails on OWA, but Outlook clients cannot connect to Exchange server.
    When I start Outlook, I get the error Unable to open the default mail folders
    When I try to create a new Outlook profile, I get the error: "The action cannot be completed. The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action"
    When I click on Check Name, I get: "The name cannot be resolved. The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action" 
    Thanks for any help you could provide
    Martin

    Changed the
    ExternalClientAuthenticationMethod  for the 2007 server.
    Output for  Get-OutlookAnywhere | fl *method*
    ExternalClientAuthenticationMethod : Ntlm
    InternalClientAuthenticationMethod : Ntlm
    IISAuthenticationMethods           : {Basic, Ntlm, Negotiate}
    ExternalClientAuthenticationMethod : Ntlm
    InternalClientAuthenticationMethod : Ntlm
    IISAuthenticationMethods           : {Basic, Ntlm, Negotiate}
    Now everytime I try to create an Outlook profile whose mailbox is on Exchange 2013 it's
    asking for credentials.
    If I dig further and try to manually configure server settings:
    If I specify the Exchange 2013 server and try a 'Check
    Name', it says: "Outlook cannot log on. Verify you are connected to the network and are using the proper server and mailbox name. The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action."
    If I specify the Exchange 2007 server and try a 'Check
    Name', the server changes for the fqdn of the 2013 server and it does resolve 'Check Name' process. Clicking on Next at this point completes the 'Add new e-mail account wizard". But is I try to start Outlook, I got an error saying "Microsoft Exchange is unavailable"
    Any other thoughts on this issue?
    Thanks,
    Martin

  • Mail format problem with Exchange 2007 and 3g 2.2

    For some reason, quite often mails read on the iphone are only 1 character per line. If read in Outlook it all looks normal until someone replies.
    l
    i
    k
    e
    s
    o
    I've tried stripping sigs and images out of the originator account, closing the ruler bar (long story) deleting and reinstalling Outlook, spyware and virus scans etc.
    Looking for some help or at least a confirmation that someone else is seeing this. We've got close to 20 people in our company seeing this.
    Anyone who replies to the screwed up mail is forced to conform to about a 1 in margine.
    [------] about so wide. No amount of switching from HTML, to RTF etc will strip out that hidden formatting.
    Tips?
    Exchange 2007 latest SPs
    3g Iphones running 2.2
    Thanks in advance.

    /bump
    Sorry, if I get no hits this time I won't bump again.

  • Exchange 2007 and 2013 coexistance Problem

    We are in the process to migrate our current Exchange 2007 to Exchange 2013.
    Our environment is as follows:
    HT01= Hub CAS Server (Exchange 2007)
    MB1, MB2 = Mailbox CCR Cluster (Exchange 2007)
    CAS1= CAS Server (Exchange 2013)
    MBNew1, MBNew2 = Mailbox Servers (Exchange 2013)
    Emails for users that are on Exchange 2007 can send and receive external emails. But they cannot send emails to users that are on Exchange 2013.
    Users on Exchange 2013 can send/receive externally, send to Exchange 2007 users, but cannot receive emails from Exchange 2007 Users.

    Are you getting any NDR? Post it.
    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.

  • Exchange 2007 and iCal issue

    Today I set up my MacBook Pro to my work email. We run Exchange 2007. My mail works great. My contacts also works great. For some reason iCal does not work. I get the following error:
    "iCal needs a valid email address to connect to the Exchange account "mike (at) worktankseattle (dot) com".
    The email address "mike (at) worktankseattle (dot) com" isn't a valid address for your Exchange account. Enter the email address for your Exchange account, and then click OK. "
    mike (at) worktankseattle (dot) com is my email. It is valid. This same email works for ical and contacts. Why does it not work with iCal? Any ideas?
    Thanks!

    I was having this problem as well, but other users in my company were not (Mail and Address Book synced fine, but iCal would not - kept stating that I did not have a valid e-mail address). So, I looked through the Exchange 2007 Management Console on the server, and tried to find inconsistencies between my e-mail account and the users who had no problem with iCal.
    It turned out that, for some unknown reason, a check box on my e-mail account ("Hide from Exchange address lists") was checked on mine but not the others. Once I unchecked that option, iCal synced up fine.
    So, I would suggest that you speak to your Exchange Admin person and ask them to check your specific E-mail Account Properties Page and have them make sure that this box is not checked. I hope that this helps some of you...

  • Mail 4.2 Snow Leopard Exchange 2007 and Subfolders

    Hello,
    I am running Mail 4.2 on Snow Leopard connecting to Exchange 2007. My account seems to be working fine for my INBOX and for sending mail; however, although I am able to see my sub-folders (under my INBOX) none of the contents have been synchronized. They are empty in Mail but when I go on the server my messages are there.
    Please help.
    Thank you,
    Darren

    rebuild your whole mail index. quit Mail and delete the file home directory/library/mail/envelope index. start mail and say yes when it asks to import your messages.

Maybe you are looking for