Exchange Server 2007 sp1 to sp2 upgrade error

Hello,
I am trying to upgrade exchange server 2007 to exchange server 2010 but my exchange server 2007 is running sp1 which cannot be directly upgraded to exchange 2010. To do this I need to first upgrade my exchange server 2007 sp1 to sp2, i am stuck because I
keep getting the error below:
Error:
The well-known object entry with GUID 6c01d2a7-f083-4503-8132-789eeb127b84 on the otherWellKnownObjects attribute on the container object CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domain,DC=mw refers to a non-USG CN=Exchange Servers,OU=Microsoft
Exchange Security Groups,DC=domain,DC=mw. Please either delete the well-known object entry or promote the target object to a universal security group.
Does anyone know how to resolve this error?? please assist

My recommendation to you is to upgrade it to Exchange 2007 SP3 with latest Rollup Updates.
Note: Before you start installing the SP3 make sure you upgrade the AD Schema for Exchange 2007 SP3.
For the error you are getting
https://social.technet.microsoft.com/Forums/exchange/en-US/a9d56cc7-dbf8-401c-b4ea-1bfd3c1f13fa/problems-installing-exchange-2007-sp1-ghost-guid?forum=exchangesvradminlegacy
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

Migrating Public Folders on Exchange Server 2007 SP1 to Exchange Online\Office 365

Hello,
Our company is looking to migrate from Exchange 2007 on premises to Exchange Online/Office 365. We have a number of public folders on our exchange server that function similarly to how the new shared mailboxes work in Exchange Online. That is to say that
we have many outside users (customers and wholesale dealers) emailing this public folder ([email protected]) and our end users are given permission to view and respond as themselves ([email protected]). I've been looking all over but haven't found a clean
way to migrate the current public folders directly into shared mailboxes. I'd just start from scratch, but we want to keep the records of the emails we've received at these public folders for customer support reasons. Can anyone help?

Hi psh8989,
According to your description, I know that you want to migrate public folder from Exchange 2007 to Office 365.
Since Office 365 is different from Exchange On-Premises, I suggest ask Office 365 Forum for help so that you can get more professional suggestions. For your convenience:
http://community.office365.com/en-us/default.aspx
However, I can also share some information for your reference : )
Based on my knowledge, Exchange supports moving your public folders to Office 365 and Exchange Online from Exchange 2007 SP3 RU10 or later. I notice that your Exchange server version is SP1, please upgrade to SP3 RU10 first and perform migration.
More detailed information to see:
Migrate legacy public folders to Office 365 and Exchange Online
http://technet.microsoft.com/en-us/library/jj983799(v=exchg.150).aspx
Thanks
Mavis Huang
TechNet Community Support

MS Forefront Server Security for Exchange Server 2007 SP1 - License Expired - Unable to update

Hi
1. My Windows SBS 2008 Server Console shows:
Virus Protection for e-mail STATUS alert CRITICAL (Forefront Security for Exchange Server)
Details: None of the engines enabled for updates have been updated in the last week.
Forefront Security for Exchange Server SP 1
2. Event Viewer
Error GetEngineFiles
Event ID 6012
Generation: Microsoft Forefront Server Security encountered an error while performing a scan engine update.
Scan Engine: vBuster (same for microsoft, Kespersky5, Wormlist, etc.)
Error Code: 0x80004005
Description: The product license has expired.
Error Microsoft Forefront Security
Event ID 7007
General: None of the engines enabled for updates have been updated in the last week.
3. About forefront
Opened Forefront Server Security Administrator > Help > About Forefront
Forefront Server:
Version: 10.1.0746
Service Pack: 1
Product Id:
Licensed Components:
Component: Forefront, License Type: Evaluation, Expiration Date: 16 Dec 2013
DO I HAVE TO BUY THIS PRODUCT or DO I HAVE TO INSTALL Forefront Security for Exchange Server SP2 or SP3?
Can please someone advise in this regard,
Thanks

-->Component: Forefront, License Type: Evaluation, Expiration Date: 16 Dec 2013
Evaluation version? didn't activate this product? You
can convert an evaluation license to a subscription license by activating the product. Be sure to have the product key available when activating FPE. After the product is activated, you can also align when the product expires with your license agreement, and
easily renew your license by entering a new expiration date.
Best,
Howtodo

After upgrading Exchange Server 2007 to SP3 with update rollup 13, OWA not working

Hi,
We have just installed Service Pack 3 and update rollup 13 on our Exchange Server 2007, but unfortunately our OWA has gone inaccessible.
PROBLEM- The following error comes up when we try to access OWA :
Exception
Exception type: Microsoft.Exchange.Clients.Owa.Core.OwaInvalidConfigurationException
Exception message: Object reference not set to an instance
of an object.
Call stack
Microsoft.Exchange.Clients.Owa.Core.OwaConfigurationManager.CreateAndLoadConfigurationManager()
Microsoft.Exchange.Clients.Owa.Core.Globals.InitializeApplication()
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
Microsoft.Exchange.Clients.Owa.Core.Configuration.CheckPublicFolders(ADSystemConfigurationSession session, ADObjectId[] pfdbIds, Boolean& allLegacy, Boolean& allLater)
Microsoft.Exchange.Clients.Owa.Core.Configuration..ctor(ADSystemConfigurationSession session, String virtualDirectory, String webSiteName, ADObjectId distinguishedName, Boolean isPhoneticSupportEnabled)
Microsoft.Exchange.Clients.Owa.Core.OwaConfigurationManager.LoadConfiguration()
Microsoft.Exchange.Clients.Owa.Core.OwaConfigurationManager.CreateAndLoadConfigurationManager()
ACTION TAKEN SO FAR :
1. Removed OWA virtual directories and recreated them again.
2. IIS has been reset.
3. Restarted the HUB/CAS server.
4. Created public folder database.
Even after doing all these activities, owa is still inaccessible. Please help.
Regards,
Ankur

Hi Ankur,
From your description, you can't access to OWA after upgrading Exchange server 2007 to SP3 rollup 13. Firstly, please locate to C:\ExchangeSetupLogs and make sure that it is a successful installation. If not, this issue often occurs.
If it is a successful upgrading, please follow the steps below for troubleshooting.
1. Open IIS Manager, click Default Web Site -> Authentication, make sure that Anonymous Authentication and Windows Authentication are enabled.
2. Click Default Web Site -> SSL Settings, check "Require SSL" and click Ignore.
3. Click Default Web Site -> HTTP Redirect, check Redirect (enter your
https://URL), check "Only redirect" box and Status code Found 302.
4. Expand Server Configuration -> Client Access ->double click owa ->Authentication tab. Check the Basic Authentication and check the Use forms-based authentication button Logon Format: Domain\user name.
Hope it helps.
Best regards,
Amy Wang
TechNet Community Support

Exchange Server 2007 error during updating SP3

Hi
My exchange server 2007 needs to update to sp3 and the OS is W2K8 Ent. During the update process, there was a prerequisite check and its failed to continue because of the following error.
1.Error:The Simple Mail Transfer Protocol (SMTP) service is installed on this computer. This must be removed before Setup can continue.
2.Error:The Windows Firewall service must be started before Setup can continue.
3.Error:Setup cannot continue with the upgrade because the 'beremote' () process (ID: 7860) has open files. Close the process and restart Setup.
I tried to remove the SMTP but it wont uninstall from the server, and IIS is installed on the server also.
So, is the SMTP is dependent with IIS and how can I proceed the update now ? And also please remarks on the 3rd error.
Thanks in advance.

run the servermanagercmd -q
see the output, does it list out smtp servier in green.
if you have previously uninstalled SMTP service, try restarting your server.
there was another post with the same error,
http://social.technet.microsoft.com/Forums/en-US/7ab14bc1-1a1a-4b6c-a15a-8a13469ae1c8/exchange-2008-installer-detects-smtp-service-but-its-not-installed?forum=exchangesvrdeploylegacy
If you find this helpful then kindly mark this as answer. Thanks.

What is the order for upgrading exchange server 2013 SP1 servers to CU7?

Hi All
I am planning to upgrade my exchange server 2013 SP1CU4 to CU7 . As per my understanding , we always proceed with the CAS servers and then the Mailbox Servers during up-gradation.
But I am confused now , since I have seen articles stating , that the Mailbox servers has to be upgraded first and then the CAS servers in exchange 2013.
What will be the correct order . My environment consists of 2 Mailbox servers in DAG and 2 CAS servers (Exchange server 2013 SP1)
Thanks in Advance .
Joyso Senior Messaging Admin

Hi Joyso,
The Microsoft recommendation regarding the order in which the Exchange 2013 server roles should be installed or Upgraded is Mailbox and then CAS.
It makes sense as the CAS Role is a stateless server and all major components are held by the Mailbox Role.
Until a 2013 mailbox server comes online, the CAS server is pretty much useless. Hence, the recommended installation order in 2013 is the reverse of 2010 – Mailbox role first & then CAS
Note: If your DAG have more nodes, you need first upgrade all non-PAM nodes and then upgrade PAM node.
Some References:
The recommendation from the Product Group is to install Exchange 2013 Preview Mailbox Role first, and then the
CAS role.
If you're separating your server roles, we recommend installing the Mailbox server role first.
Upgrade your Exchange 2013 server roles in the required order. First, upgrade Mailbox servers
and then upgrade Client Access servers. -Upgrade DAG Mailbox servers
Exchange 2013 Server Roles Installation Order – Mailbox First:
Regards,
Satyajit
Please “Vote As Helpful”
if you find my contribution useful or “Mark As Answer” if it does answer your question. That will encourage me - and others - to take time out to help you.

Upgrade directly from Exchange Server 2010 SP1 to Exchange Server 2010 SP3

Hi,
We have current setup with Exchange Server 2010 SP1 ( DAG & CAS Array with WNLB).
Can we upgrade directly from Exchange Server 2010 SP1 to
Exchange Server 2010 SP3 . ?
Thanks in Advanced.
Regards,Ali

Hi Ali,
Yes, you can. Please upgrade your Exchange 2010 SP1 server roles in the following order: Client Access, Hub Transport, Unified Messaging, Mailbox, Edge Transport. What's more, please note that when you install a Service Pack or update rollup on a server
that's a DAG member, several services will be stopped during the installation, including all Exchange services and the Windows Cluster service.
For more information, here is a helpful article for your reference.
Installing Update Rollups on Database Availability Group Members
http://technet.microsoft.com/en-us/library/ee861125(v=exchg.141).aspx
Hope this can be helpful to you.
Best regards,
Amy Wang
TechNet Community Support

Upgrading from SBS 2008 and Exchange Server 2007 and Adding Modest Failover Protection

I haven't seen anyone describe this scenario, so maybe it can't be done, but it seems it should work. Can someone either confirm this is viable or set me straight and tell me it's not wise (and if not, why not).
I currently have SBS 2008 (2008 Server + Exchange Server 2007 + some other components). I use redirected folders so all my user data is stored primarily on the server, and then sync'd with their local harddrives for roaming use and as an additional
backup precaution. I want to upgrade to a modern version of Exchange (don't care too much about the underlying server OS, but seems like a good time to upgrade everything). I also want to improve the reliability for rapid recovery in the event of a system
failure. I have always felt nervous with SBS because it only runs on a single server.
My plan is:
Install Windows Server 2012 Standard on a new server machine
Join that new server to the existing SBS domain and sync the users, etc.
Install Exchange Server 2013 on the new 2012 Server
Migrate the existing Exchange data and account info to the new server
Demote the SBS Server and promote the new server to primary DC
Reformat the old SBS server and install Windows Server 2012 on it too, and join it to the domain as a second DC
Set up DFS Replication and keep all my user data folders between the two servers (so if one server fails, the other can take over, just not automatically like with a cluster)
Install Exchange Server 2013 on the reformatted 2012 Server box (so second instance on the domain) and set it up to sync with the first Exchange Server 2013 via DAG (so if either computer crashes, the other can take over for both Exchange Server and file
services)
Wouldn't that give me a complete slow-response failover system without the need for setting up a cluster (I know a cluster would provide instant failover protection, but I don't need that kind of speed - a manual switchover in the rare event of a server
failure is acceptable for us)? I could do this using cheap hardware for each server, because unless both servers fail at the same time, clients can point to the other server. And because it's not a formal cluster, I don't need to buy anything for a shared
SAN. This seems like such an obvious more cost-effective solution for a small network, I don't understand why this isn't a common approach, which makes me wonder if there is some reason it won't work.
Any suggestions or feedback? Are Redirected Folders still recommended for users on a Server 2012-based domain?
Thanks,
Colin
Colin

Ed, thanks again for your help. OK, so here's my updated plan (I realize I should probably check on some of these pieces on the Server group, instead of this Exchange group).
Constraints/objectives:
None of the machines are truly server grade hardware, but only 5 people on the network, so performance is generally not an issue, unless a given server is just pegged on CPU or HD due to its own internal maintenance tasks and can't respond to user requests.
Haven't seen any problems, since upgrading server from 4GB RAM to 8GB a few years ago.
Not going to buy any new hardware at this time, but do have several unused consumer-grade computers I can deploy as wimpy or moderate servers.
Main issue is to limit repair time in the event of a system failure (instant failover is not required, but want to be able to restore network functions within less than 24 hours in the event of a hardware failure) and minimize time spent on IT
maintenance.
Because of light IT maintenance (not anyone's primary job and we're too small to justify a dedicated IT person or to pay for outside help), almost every touch takes me research and time to re-learn what I haven't done in weeks, months, or years -- so also
want to keep all IT tasks as simple as possible.
We philosophically want to invest now for the next 5 years and avoid ongoing cloud fees (so zero interest in Windows Server Essentials with Exchange Online)
A little nervous about using VM's, just because I never have before, but I do respect that's probably the right way to do many of these things...
Currently I have SBS 2008 (Windows Server 2008 R2, Exchange Server 2007, WSUS 3, all with latest SP's, also includes SharePoint and other stuff, but I don't really care about most of it) on a single 8GB consumer grade system, which functions as a file
server and Exchange server. We use Redirected Folders and Offline files for all users, which works great for us and provides additional file redundancy (if server goes down, all of each user's files are also on their own machine and they can even continue
to work just fine w/o the server, losing only ability to send and receive e-mail). It has been sufficient, but I want to upgrade our version of Exchange and I am nervous that if that current one server fails, it would take me a long time to restore everything
from backup, easily many days, especially if I need to buy any replacement hardware. It is RAID1, so a single drive failure is easy to handle, but that's the only hardware redundancy for the current server.
New Plan:
Install Windows Server 2012 R2 Standard on a new modest machine (16GBR RAM, Core i7, 1TB RAID1 (may upgrade to 3 or 4 TB), 256 GB SSD boot drive, this had been my old personal computer)
Join that new server to the existing SBS domain (2008 R2/Exchange 2007), make it a DC, sync the users, etc.
Install Windows Server 2012 R2 Standard on a wimpy computer (4GB RAM Core i3 processor), leave it as a member server
Install Exchange Server 2013 on the wimpy new 2012 R2 Server (and nothing else, this will be dedicated to Exchange to make the most of such a wimpy machine)
Migrate the existing Exchange data from the old SBS Exchange 2007 server and account info to the new server
(or should I just create new accounts and copy the data from the user end through Outlook -- is that safer and cleaner than attempting any kind of server-level Exchange data migration?)
Demote the old SBS Server and promote the new 16GB server to primary DC. Now it's OK to take the old SBS server off the network.
Reformat the old SBS server and install Windows Server 2012 R2 on it too, and join it to the domain as a second DC (and possibly DCPROMO it to be the main server)
Install Exchange Server 2013 in a VM on the reformatted 2012 R2 Server box (so second instance on the domain for Exchange redundancy) and set it up to sync with the first Exchange Server 2013 via DAG OR set up another physical wimpy member server and install
it there. In any case, do NOT install Exchange directly on either DC.
Set up DFS Replication or a Failover Cluster (still need to research this, but I had planned on DFS, thinking Cluster required shared drive, but Ed corrected me on this) between the two DC's for redirected files and keep all my user data folders between
the two servers. We don't need automatic failover, like with a cluster, a manual switch would be acceptable, but if no additional cost or risk to clustering the two DC's, then the auto-failover protection that provides would be better than DFS.
I think this incorporates all of your points, Ed. Does this sound right now? What's your advice on #5 (how to best migrate user data)?
Thanks so much for all your help,
Colin

Exchange server 2007 Service Pack problems SBS 2008

I am Running Exchange server 2007 on Small Business server 2008 (SBS 2008). I tried to install SP2 but it fails both windows update and manually. Can anyone first advise me what version I'm currently running?
Help / about form Exchange Management Console displays:
Version 08.01.0436.000
And running repair on Exchange server from programs and features displays 2007 SP1 setup. So I believe SP2 to be next I have also ran SP3 but this fails.
Here is the end lines from a log:
[03/05/2014 08:54:13] [0] Setup will run the task 'uninstall-msipackage'
[03/05/2014 08:54:13] [1] Setup launched task 'uninstall-msipackage -logfile 'C:\ExchangeSetupLogs\ExchangeSetup.msilog' -ProductCode '24b2c164-de66-44fe-b468-a46d9d5e6b31' -PropertyValues 'BYPASS_CONFIGURED_CHECK=1 DEFAULTLANGUAGENAME=ENU''
[03/05/2014 08:54:13] [1] Beginning processing.
[03/05/2014 08:54:13] [1] Property 'PackageName' is 'EXCHANGESERVER.msi'.
[03/05/2014 08:54:13] [1] Removing MSI package with code '24b2c164-de66-44fe-b468-a46d9d5e6b31'.
[03/05/2014 09:09:01] [1] [ERROR] Unexpected Error
[03/05/2014 09:09:01] [1] [ERROR] Unable to remove product with code 24b2c164-de66-44fe-b468-a46d9d5e6b31. Fatal error during installation. Error code is 1603. Last error reported by the .msi package is 'Could not open key: UNKNOWN\Components\7ABFE44842C12B390AF18C3B9B1A1EE8\461C2B4266EDEF444B864AD6D9E5B613.
Verify that you have sufficient access to that key, or contact your support personnel. '.
[03/05/2014 09:09:01] [1] [ERROR] Fatal error during installation
[03/05/2014 09:09:01] [1] Ending processing.
[07/05/2014 19:45:17] [0] End of Setup
There is a registry key to match this and The administrator account used for setup has access to it i believe??? What does this log mean?

Hi,
This error indicated that your account missed registry permissions on: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\ 7ABFE44842C12B390AF18C3B9B1A1EE8\461C2B4266EDEF444B864AD6D9E5B613
Please check whether you have permission. You can also check whether the key have permissions inherited from the Parent Key or not.
After changing the permission, please run the setup again.
Best Regards.

Backup Issue of exchange server 2007 mailbox store

Dears
Exchange server 2007 with CCR clustering
I have got a problem with the backup of one of my mailbox store. Its going till the last and giveing the final error as follows:-
V-79-57344-65247 - A failure occurred reading an object.
Also the warning as follows:-
Backup- \\mailserver.domain\Microsoft Information Store\First Storage Group
WARNING: "\\mailserver.domain\Microsoft Information Store\First Storage Group\Database" is a corrupt file. This file cannot verify.
Backup V-79-57344-34108 - An unexpected error occurred when cleaning up snapshot volumes. Confirm that all snapped volumes are correctly resynchronized with the original volumes.
Does it mean my information store is really a corrupted file. It has been properly monted and logs are genearting.
Even when I checked the last full backedup log file from the management shell it clearly shows the backing up is properly happened on the log files.
When I checked the event log of Exchnage server I can see these logs:-
Event ID 401, 403 errors
The size of the problem store is 308 GB.
One of the other store with 46 GB is backing up without any issue

Hi,
If you have a space issue with the Exchange server, you can upgrade drives on active node and passive node one by one. It is not recommended to upgrade them at the same time.
For more information about upgrading Exchange 2007 CCR active node or passive node, here are some helpful threads for your reference.
Upgrade hard drives on passive node. Process and procedure
http://social.technet.microsoft.com/Forums/exchange/en-US/08b9e893-87c9-48c3-bab2-91027cc09949/upgrade-hard-drives-on-passive-node-process-and-procedure?forum=exchangesvravailabilityandisasterrecoverylegacy
Upgrading hard drives in exchange server
http://social.technet.microsoft.com/Forums/exchange/en-US/0e4514f9-76da-44d2-9dec-a3be5add79b1/upgrading-hard-drives-in-exchange-server?forum=exchangesvravailabilityandisasterrecoverylegacy
Hope it helps.
Best regards,
Amy
Amy Wang
TechNet Community Support

Exchange server 2007 stop receiving emails

i have a strange issue with our exchange 2007 server, and i hope any one can help me, each day i have one of our exchange servers can't receive emails, and all emails sent to users in this servers are queued in the sending email server, and i have to manually
restart the Microsoft exchange transport service in this server so that it's able to receive emails, i found an error in the server that always repeated with different parameters
the error is
Error ID: 4999
Error Source: MSExchange Common
Watson report about to be sent to dw20.exe for process id: 3508, with parameters: E12, c-RTL-AMD64, 08.02.0254.000, edgetransport, M.E.Transport, M.E.P.S.SmtpInServer.HandleConnection, System.NullReferenceException, 69f8, 08.02.0254.000. ErrorReportingEnabled:
False
i receive the same error each time the server stop responds but the parameters is changed each time (Process ID number always changed) like below
Watson report about to be sent to dw20.exe for process id: 3644, with parameters: E12, c-RTL-AMD64, 08.02.0254.000, edgetransport, M.E.Transport, M.E.P.S.SmtpInServer.HandleConnection, System.NullReferenceException, 69f8, 08.02.0254.000. ErrorReportingEnabled:
False
i hope any one can help me solving this problem
the server is windows server 2008
Exchange 2007 SP2 Server Rollup 5
McAfee Enterprise Antivirus is in the box
Backup Exec Agent is in the box Also
a lot of transport rules applied to our exchange organization
Mahmoud Sabry IT System Engineer

Hi
As per the information and details provided by you, Exchange server 2007 stop receiving emails, then please follow these steps: -
If you do have a 60 GB partition on the C: drive, one of the first signs of trouble is when the free space on C: drops below 2GB. Exchange 2007 stops receiving external
emails. This is caused by a condition known as Back Pressure.
Please check the following: -
Check the nslook up for correct MX record.
Run the exbpa and llok for any recent changes.
Check for the device in perimeter network which accepts connections on port 25 FW or any other anti spam device).
Try to run a telnet session from the firwall and then out side and drop email on the server.
I hope this information will be helpful for you.
Thanks and regards
Shweta@G

Move Exchange Server 2010 SP1 databases and log files to another partition

My company has been running Exchange Server 2010 SP1 on virtual machine for almost three years. My colleague created this virtual machine (Windows Server 2008 R2 SP1) before Exchange Server installation with following partitions:
C partition - for Windows Server 2008 R2 SP1 OS (size 40 GB)
E partition - for Exchange Server 2010 SP1 databases and logs (size 410 GB)
Those two partitions are on the same virtual hard disk "next to one another" so I can not extend C partition which gets filled up with IIS logs (when C partition free space is under 10 GB I am backing up these logs with backup software and afterwards
deleting them thus freeing up space on C partition). I have 2 databases (along with Public Folders) and size of these databases and their logs is around 235 GB.
Is it safe to move these databases and their logs to another partition which I would create on separate virtual hard disk for this purpose only and how much time this process might take since during this process databases
would be dismounted and inaccessible to all users? He made big blunder in my opinion but I have to solve this.

Yes, its safe to move the DB/Logs. You can follow the procedure mentioned in this article to do it via EMC or Shell... http://exchangeserverpro.com/move-exchange-2010-database-folder/
But it depends on various factors on how long it is going take, like size of the database/logs, server performance, storage performance etc...
Besides this, upgrade Exchange 2010 SP1 to SP3, SP1/SP2 aren't supported anymore! http://blogs.technet.com/b/rmilne/archive/2014/04/09/end-of-exchange-2010-sp2-support.aspx
Blog |
Get Your Exchange Powershell Tip of the Day from here

Provisiong of users from OIM to Exchange Server 2007

Hi,
I am trying to Provisioning the users from OIM 9.1.0.1 to Exchange server 2007. For this i used Exchange Server Connector 9.1.1.1.0. By using AD_Base_connector 9.1.1.0.0 i can
provisioned the user details. But while provisioning to the Exchange server 2007 i am getting the following error
ERROR [XELLERATE.WEBAPP],Class/Method: tcLookupFieldAct ion/lookupByColumn encounter some problems: lookup Error in OIM
And i am unable to get the LookUp detais for the MailBox in Design Console as well as in the ScheduleTasks in OIM Admin Console..
Can anybody help me in solving this issue.
Thanks & Regards
SRI

Hi suren,
i am using the Remote Manager. I enabled logs in log.properties in both OIM server and Remote Manager.
I am observing the following message in Remote Manager command prompt.
DEBUG,30 Mar 2010 01:12:44,437,[XELLERATE.REMOTEMANAGER],Class/Method: RMISSLCli
entSocketFactory/createSocket left.
and i am getting the error in Weblogic server command prompt.
Running ISADAM
Target Class = java.lang.String
Running GETATTRIBUTEHASH
Target Class = com.thortech.xl.util.adapters.tcUtilHashTableOperations
Running Set User Attributes
ERROR,30 Mar 2010 01:13:39,484,[XELLERATE.WEBAPP],Class/Method: tcLookupFieldAct
ion/lookupByColumn encounter some problems: lookup Error
can u help me in resolving this issue.
Thanks in Advance,
SRI

MimeMessage.reply() issue with MS Exchange Server 2007 Emails

I have an application that retrieves emails from an MS Exchange Server 2003 mailbox. The data from each message is read, validated and conditionally loaded to a table. If the message doesn't pass validation, a rejection email is sent back to the sender with an error message and a copy of the email. (We're using Java 1.5. However, I test with both 1.5 and 1.6.)
Also, if the message passes validation, positive notification is sent back to the sender.
Both processes use the method: javax.mail.Message.reply()It's coded as:
MimeMessage reply = (MimeMessage) message.reply(false);My organization is in the process of migrating to MS Exchange Server 2007. We've found that the reply() method no longer finds the sender method, thus unable to create a reply message. The error message we receive is:
javax.mail.SendFailedException: No recipient addresses
     at javax.mail.Transport.send0(Transport.java:110)
     at javax.mail.Transport.send(Transport.java:80)
     at org.ccci.gms.datacollector.DataCollector.sendReply(DataCollector.java:514)
     at org.ccci.gms.datacollector.DataCollector.processMessages(DataCollector.java:162)
     at org.ccci.gms.datacollector.DataCollector.main(DataCollector.java:101)After creating the MimeMessage object from the reply() method, I printed out the email header detail from both 2003 and 2007 messages. You'll note from below that the "To" or recipient address is missing from Server 2007.
MS Exchange 2003 works fine
From: [email protected]
To: [email protected]
Subject: Re: Report
In-Reply-To: <[email protected]>MS Exchange 2007 no longer works
From: [email protected]
Subject: Re: Reports
In-Reply-To: <[email protected]>I know I could just use the "addRecipient()" method to get around this problem. I wanted to know if anyone has encountered this issue. Please share the resolution. Any suggestions will be greatly appreciated.
Thanks,
LaelW

When the original message is accessed using IMAP, the reply method uses the information in the
IMAP ENVELOPE to determine where to send the reply. It first looks for the Reply-To address
in the ENVELOPE, then the From address.
Interestingly, when not using IMAP, the getFrom method returns the Sender header if the From
header is empty. The IMAP-specific code doesn't do that, although perhaps it should.
It would be interesting to compare the ENVELOPE data from the protocol trace in the two cases.
The ENVELOPE data will follow this syntax:
envelope     = "(" env-date SP env-subject SP env-from SP
          env-sender SP env-reply-to SP env-to SP env-cc SP
          env-bcc SP env-in-reply-to SP env-message-id ")"
So it's the first three address fields after the Subject that are relevant. If the From and Reply-To
fields are NIL, but the Sender field has a valid address, let me know. I should probably fix the
IMAP provider to fall back to the Sender field if the From field is missing.

M4E with N73 - MS Exchange server 2007

Hi Guys,
maybe I am stupid, but I can't seem to get this thing to work,
I have installed mail for exchange 2.3, finally the security setting is showing, I have approved the certificate but still I am getting the very general :
"Error in Exchange server. try again later."
to explain my steps:
1. configure the connection to use the HSDPA/Cellular link.
2. hostname: owa.domain.com , username and password.
server is Exchange server 2007 and configured behind an ISA server. OWA 2007 from a browser works fine.
please any assistance would be great, I don't even know how to approach it anymore.
thanks in advance,
Badsyntax (Simon)

Hi Imran,
As per my information Webcenter Suite 10.1.3.2 does not have any direct integration capability with MS Exchange Server due to DEEP LINK LIMITATION. Only possible work around is go for External Application SSO registration and then render that URL in IFRAME.
As far as WEBCENTER INTERACTION is concerned i think its seprately licensed and eventhough it's free you need extra Hardware to Install and Configure.
Regards,
Vindhyachal Sharma

Exchange Server 2007 sp1 to sp2 upgrade error

Similar Messages

Maybe you are looking for