Exchange 2003 Reclaim White Space

Hello Everybody,
I have exchange 2003 Enterprise and I want to reclaim the white space . To do that I have to do and offline def fragmentation or I can do it online but I have to have at least 110 % of the
free space of my database. Lets assume that I have a partition on 1 Tb and the priv1.edb .is 400 how much free space should I have on the server to run the online defragmentation and reclaim the white space.
Or please provide me with the alternate solution to reclaim the space.
http://www.arabitpro.com

Using the solution above, while not having any downtime for the user, has some drawback because moving the mailboxes to another store break the single instance storage. ( http://support.microsoft.com/kb/175481)
so depending on the users activity you might end up with using more space than with the orignal DB after defrag. Plus, you need to be very familiar with the removal DB process of the first DB installed on the server.
I assume that you are looking at this because of storage space on the server.
FYI, the online defragmentation only reclaim the unused space in your DB (space from deleted users, item past the retention date, etc...) it does not reclaim the PHYSICAL space. After a succesfull online defrag, any new items create in the DB will using
exisiting space, once that space is consumed then the edb file will start to grow.
note as well, that you should be sure that the online defrag as complete before running the eseutil /d (to reclaim the maximum space)
If you can organize the downtime for your users if would recommend you to do the defrag. if you worry that the space available on the machine is not enough then run it on another machine by following this article "
244525
(http://support.microsoft.com/kb/244525/ )
How to run Eseutil on a computer without Exchange Server
If you have a machine with better cpu/IO than your exchange server it will quickier.
and you can also then do a simulation (from a backup copy of the edb) to give an adequate estimation of the downtime.
If you think that is too much, just like andy was saying , let it be. as long as you have white space in your DB the edb file will not grow (the .stm might but that is another story).

Similar Messages

Mailbox Database Size/White Space Reduction in a DAG

I have several large databases in which I'm moving mailboxes off of in an attempt to prevent my LUNs from running out of disk space. As well, I have several mailboxes of users who have left the company. My questions are as follows:
1. When I run remove-mailbox -id "some mailbox" -permanent $true, the mailbox is deleted from Exchange relatively instantly. Will Exchange recoup the white space that is left behind after the mailbox has been deleted so that the
database shrinks in size? Or will it just start writing over the white space rather than growing the size of the database?
2. Perataining to mailboxes that have been moved, if "Keep Deleted Mailboxes for" is set to 4 days on the database that holds mailboxes that I'm moving off, will the database hold onto the mailbox (even though it has successfully been moved to
another database) for the duration of the "Keep Deleted Mailboxes for" setting? Or will the mailbox be hard deleted after the move completes successfully?
3. As part of Online Maintenance, will Exchange defrag a databse and decrease the white space, thereby shrinking the database size or will I have to take it offline to do that?
4. What are the procedures to perform an Offline Defrag of an Exchange Databse? How risky is this?

Hello,
To answer your questions:
1.   When and online database defrag completes a pass on the database it will reclaim this as whitespace in the database. It will not however reclaim space on the disk by shrinking the .edb file. An offline defrag is required for that.
2.   Moved mailbox will not be hard deleted until the 4 day retention period has past, unless you manually purge them using Remove-StoreMailbox.
3.   Related to the answer for number 1. Exchange will fill whitespace as mailboxes grow, but it will not reclaim disk space.
4.   In a DAG you will you need to dismount the mailbox database and run eseutil /d against the active database copy. This is a relatively low risk procedure, but requires databases to be offline thus interrupting mailbox access. It can also
take quite along time depending on the database size. The rate of defrag estimated by MS is 9 GB/hr. Here is a reference:
http://support.microsoft.com/kb/192185/en-us
For these types of situations my preference (If disk space allows) is to move all mailboxes to a fresh database then delete the database with excessive white space

Exchange datastore - white space?

I have around 300 user mailboxes on our Exchange 2010 mailbox server. All mailboxes are stored on a single data store which is approximately 1TB in size. The organisation recently signed up to a third party cloud messaging provider (Mimecast). One
of the services provided by Mimecast is mailbox archive and journaling. The Mimecast archiving process has complete and I can now see all emails (in all mailboxes) over 90 days old are no longer stored on our Exchange server, instead they're now in the Mimecast
cloud. The actual disk size of the data store is still around 1TB and we have been informed by Mimecast we would need to perform an offline defrag of the data store to reclaim the white space. I suspect an offline defrag could take several days on a data store
of this size and would have a huge impact on the business. Rather than dismounting the data store I was thinking of creating a new data store and migrating the mailboxes to this in order to reduce disruption. Once all mailboxes were migrated I would delete
the old data store. Does this sound like a viable solution?

I have around 300 user mailboxes on our Exchange 2010 mailbox server. All mailboxes are stored on a single data store which is approximately 1TB in size. The organisation recently signed up to a third party cloud messaging provider (Mimecast).
One of the services provided by Mimecast is mailbox archive and journaling. The Mimecast archiving process has complete and I can now see all emails (in all mailboxes) over 90 days old are no longer stored on our Exchange server, instead they're now in the
Mimecast cloud. The actual disk size of the data store is still around 1TB and we have been informed by Mimecast we would need to perform an offline defrag of the data store to reclaim the white space. I suspect an offline defrag could take several days on
a data store of this size and would have a huge impact on the business. Rather than dismounting the data store I was thinking of creating a new data store and migrating the mailboxes to this in order to reduce disruption. Once all mailboxes were migrated I
would delete the old data store. Does this sound like a viable solution?
Yep and the recommended one!
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Exchange 2003 DB Defrag - ESEUTIL estimates

I'll spare the details but we have to keep a remaining Exchange 2003 database around until we get a new voicemail solution - all user mailboxes have been migrated to 2010. The problem is I can't dismount the database to run eseutil /ms until our maintenance
window hits in two weeks and I'd like to get a better idea if I can perform the defrag then or if I need to get a longer maintenance window for this particular task.
The situation is as follows:
DB Size: 750GB
Whitespace: 733GB (based on event 1221)
Used Space: 17GB
Based on the 9GB/hour eseutil rate (could be slower based on our hardware) this could be a worst case of 3.5 days or best case 2 hours if it only processes the used space. Can anyone confirm if the entire DB (whitespace + used space) needs to be
defragged or just the used DB space when eseutil runs?

It should be really faster if it has that much white space... however considering its Exchange 2003 Enterprise Edition, why can't you crate a new DB and move the mailboxes across the DBs and delete the old DB....
Blog |
Get Your Exchange Powershell Tip of the Day from here

Exchange 2003 - 2010. Moving public folders one at a time

Hi all,
I'm in the process of decomisioning our old Exchange 2003 server (long overdue after what has been a relativly smooth and trouble free transition to 2010). As the first step in the decomisioning process, I'm looking to move the public folders from the 2003
box to the 2010 box. From my understanding there are a couple of ways to achieve this (please correct me if I'm wrong). The first is to add the Exchange 2010 server as a new replication partner, allow for replication of the PFs to occur, and then remove the
2003 partner from the replication partnership. The other option is to use MoveAllReplicas.ps1.
I opted for the first option, but the problem I have is that the initial replication process started to generate a very large number of transaction logs on the Exchange 2010 server, to the point I was slightly conccerned I was going to run out of space on
the volume (our server is backed up nightly at which point the transaction logs are normally flushed).Whilst I know I could potentially increase the size of the volume or turn on cicular logging for the duration of the migration (neither of which is appealing
as it will involve down time), I was wondering if there was a way to move a smaller set of Public folders one at a time with a powershell command, or is it an all or nothing operation? My other option may be to replicate a small subset of folders everyday,
but that just a little painful as there are a large number of child folders with in the structure. Any other suggestions welcome!
Many thanks,
Rob

Hi,
If your Public Folder Database is large, you can use tool like Exfolders or ESM to add replica folder by folder.
A related article for your reference.
http://careexchange.in/moving-public-folders-from-exchange-2003-to-exchange-2010/
Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or
suitability of any software or information found there. Please make sure that you completely understand the risk before retrieving any suggestions from the above link.
And it is recommended to replicate public folders off business hours.
Best regards,
Belinda Ma
TechNet Community Support

Relay issue from Unix across Exchange 2003 OWA server in Exchange 2010 environment

Hi,
I'm trying to resolve an issue. We have one Exchange 2003 server left in our environment. The rest is now Exchange 2010. We are working to decommission this server. Monitoring the SMTP logs, I am working with the various groups to get the traffic
off this server and onto the Exchange 2010 environment.
The issue we are finding is with a work flow. This Java app for eBis sends email to users. This is done correctly through Exchange 2010 and gets delivered from our HUB/CAS servers to the target user mailbox. This email has several links the user must click
for approving or rejecting requests. Upon clicking Approve, a new email window opens (we use Outlook 2010). The TO address is in the format of [email protected] Upon clicking Send, our Exchange 2010 HUB/CAS servers accept the
email, because one of our send connectors has, as address space, *.domain.corp. However, the email address being used it not an alias on any Exchange 2010 mailbox, so it appears Exchange 2010 is sending this email on to the Exchange 2003 server, which
also is an SMTP server. I *think* this server is looking at the address after @ to determine where to send it (ebisserver.domain.corp, which is valid in our DNS), and sends it on to that server, where the java "listener" program intercepts
the mail, processes it and then saves it to a file somewhere.
We are at a loss as to how to get Exchange 2010 to do this instead of Exchange 2003... once this traffic is eliminted from Exchange 2003, I can proceed with decommission of this server. Any help troubleshooting this issue is appreciated.

The only reason the Exchange 2010 server would route outbound mail through an Exchange 2003 server is that you have an SMTP Connector defined on the Exchange 2003 server that has a more specific domain than you have on the Exchange 2010 server. You
should be able to see all your Send Connectors (an SMTP Connector on Exchange 2003 looks like a Send Connector in Exchange 2010) by running Get-SendConnector.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

How to remove white spaces from XML content using Coldfusion?

Hi,
Can anybody help me in removing white spaces in between the tags from the below XML content using coldfusion?
XML content:
<?xml version="1.0" encoding="UTF-8"?> <chart showdates="true" today="08/12/2009"> <phases> <phase color="CCFFCC" name="Funded"/> <phase color="CDCD67" name="Concept"/> <phase color="99CCFF" name="Feasibility"/> <phase color="0099FF" name="Development"/> <phase color="0099FF" name="Development"/> <phase color="CC99FF" name="Close-out"/> <phase color="909090" name="Sustaining"/> </phases><program name=""> <project enddate=" 30/03/2007 " id="43250" startdate=" 28/02/2006 "> <version enddate=" 30/03/2007 " number=" 1" startdate=" 28/02/2006 "> <phase color="CCFFCC" currentdate="23/03/2006" name="Project Start" plandate="28/02/2006" type="phase"/> <phase color="99CCFF" currentdate="04/04/2006" name="Feasibility Closure" plandate="31/05/2006" type="phase"/> <phase color="0099FF" currentdate="29/03/2007" name="Commercialization" plandate="30/12/2006" type="phase"/> <phase color="CC99FF" currentdate="30/03/2007" name="Project Closed" plandate="30/03/2007" type="phase"/> <phase color="909090" currentdate="" name="Obsolescence" plandate="" type="phase"/> </version> </project> </program> </chart>
Output I am expecting is like below,
<?xml version="1.0" encoding="UTF-8"?><chart showdates="true" today="08/12/2009"><phases><phase color="CCFFCC" name="Funded"/><phase color="CDCD67" name="Concept"/><phase color="99CCFF" name="Feasibility"/><phase color="0099FF" name="Development"/><phase color="0099FF" name="Development"/><phase color="CC99FF" name="Close-out"/><phase color="909090" name="Sustaining"/></phases><program name=""><project enddate=" 30/03/2007 " id="43250" startdate=" 28/02/2006 "><version enddate=" 30/03/2007 " number=" 1" startdate=" 28/02/2006 "><phase color="CCFFCC" currentdate="23/03/2006" name="Project Start" plandate="28/02/2006" type="phase"/><phase color="99CCFF" currentdate="04/04/2006" name="Feasibility Closure" plandate="31/05/2006" type="phase"/><phase color="0099FF" currentdate="29/03/2007" name="Commercialization" plandate="30/12/2006" type="phase"/><phase color="CC99FF" currentdate="30/03/2007" name="Project Closed" plandate="30/03/2007" type="phase"/><phase color="909090" currentdate="" name="Obsolescence" plandate="" type="phase"/></version> </project></program></chart>
Thanks in advance,
Regards,
Manoz.

Daverms,
Thanks for the quick turn around..
I have applied the solution what you suggested above (<cfprocessingdrirective suppresswhitespaces="yes"), still whitespaces are existing in my output.
The output what I am getting is,
(blue color part is my output & red color indicates whitespaces)
<?xml version="1.0" encoding="UTF-8"?>
<chart showdates="true" today="09/12/2009">
<phases>
<phase color="CCFFCC" name="Funded"/>
<phase color="CDCD67" name="Concept"/>
<phase color="99CCFF" name="Feasibility"/>
<phase color="0099FF" name="Development"/>
<phase color="0099FF" name="Development"/>
<phase color="CC99FF" name="Close-out"/>
<phase color="909090" name="Sustaining"/>
</phases>
<program name="">
<project enddate=" 01/01/2010 " id="12059" startdate=" 20/06/2003 ">
<version enddate=" 01/01/2010 " number=" 1" startdate=" 20/06/2003 ">
        <phase color="CCFFCC" currentdate="20/06/2003" name="Project Start" plandate="20/06/2003" type="phase"/>
        <phase color="CDCD67" currentdate="" name="Concept Closure" plandate="" type="phase"/>
        <phase color="99CCFF" currentdate="20/06/2003" name="Feasibility Closure" plandate="20/06/2003" type="phase"/>
        <phase color="F0FF00" currentdate="" name="Alpha Test" plandate="" type="milestone"/>
        <phase color="F0FF00" currentdate="26/07/2004" name="Beta Test" plandate="31/05/2004" type="milestone"/>
        <phase color="0099FF" currentdate="29/06/2005" name="Commercialization" plandate="08/12/2004" type="phase"/>
        <phase color="CC99FF" currentdate="24/02/2006" name="Project Closed" plandate="01/01/2010" type="phase"/>
        </version>
<subproject enddate=" 16/10/2008 " id="11809" name="espWatcher Pricing Toolkit" startdate=" 01/08/2003 ">
<version enddate=" 16/10/2008 " number=" 1" startdate=" 01/08/2003 ">
        <phase color="CCFFCC" currentdate="01/08/2003" name="Project Start" plandate="01/08/2003" type="phase"/>
        <phase color="99CCFF" currentdate="" name="Feasibility Closure" plandate="" type="phase"/>
        <phase color="0099FF" currentdate="15/06/2005" name="Commercialization" plandate="08/12/2004" type="phase"/>
        <phase color="CC99FF" currentdate="16/10/2008" name="Project Closed" plandate="16/10/2008" type="phase"/>
        </version>
</subproject>
<subproject enddate=" 31/12/2070 " id="35704" name="espWatcher version 2 (2005)" startdate=" 01/01/2005 ">
<version enddate=" 31/12/2070 " number=" 1" startdate=" 01/01/2005 ">
        <phase color="CCFFCC" currentdate="01/01/2005" name="Project Start" plandate="01/01/2005" type="phase"/>
        <phase color="99CCFF" currentdate="01/07/2005" name="Feasibility Closure" plandate="01/07/2005" type="phase"/>
        <phase color="0099FF" currentdate="31/03/2006" name="Commercialization" plandate="31/03/2006" type="phase"/>
        <phase color="CC99FF" currentdate="31/12/2070" name="Project Closed" plandate="31/12/2070" type="phase"/>
        </version>
</subproject>
</project>
</program>
</chart>
However this solution removes most of the whitespaces, I want exact output as flash file is expecting so..
Where ever I am calling the CF functions, there I am getting the whitespaces. like below cases.
startdate="#getProjectStartDate(sProjectIdList)#" -> output I am getting for this statement is -> " 12/09/2009 "
Please assist me...
Regards,
Manoz.

JDeveloper Error: White spaces are required between publicId and systemId.

I'm using JDeveloper 10.1.3.1.0.
This error is occurring in a BPEL process project.
With one particular web service I have, adding a Partner Link to the BPEL generates the following compile error:
Error: White spaces are required between publicId and systemId.
I can add Partner links from other web services and the BPEL will compile fine. The main difference I can see is that this web service supports WS-Addressing.
I have found one other reference to a similar (but not exactly the same) problem elsewhere in these forums but the fix is not really applicable. All of the wsdl files pass the "Validate WSDL" operation, and I don't see anything wrong with them.
When the error occurs and I select "Go To Source" it points back to the first line of the bpel file.
Can anyone help me out on this?
This is the wsdl for the web service, wsademo.wsdl:
<?xml version="1.0" encoding="UTF-8"?>
<definitions name="wsademo"
targetNamespace="http://localhost:11001/wsademo.wsdl"
xmlns:tns="http://localhost:11001/wsademo.wsdl"
xmlns:SOAP-ENV="http://www.w3.org/2003/05/soap-envelope"
xmlns:SOAP-ENC="http://www.w3.org/2003/05/soap-encoding"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing"
xmlns:ns="http://localhost:11001/wsademo.wsdl"
xmlns:SOAP="http://schemas.xmlsoap.org/wsdl/soap12/"
xmlns:MIME="http://schemas.xmlsoap.org/wsdl/mime/"
xmlns:DIME="http://schemas.xmlsoap.org/ws/2002/04/dime/wsdl/"
xmlns:WSDL="http://schemas.xmlsoap.org/wsdl/"
xmlns="http://schemas.xmlsoap.org/wsdl/">
<types>
<schema targetNamespace="http://localhost:11001/wsademo.wsdl"
xmlns:SOAP-ENV="http://www.w3.org/2003/05/soap-envelope"
xmlns:SOAP-ENC="http://www.w3.org/2003/05/soap-encoding"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing"
xmlns:ns="http://localhost:11001/wsademo.wsdl"
xmlns="http://www.w3.org/2001/XMLSchema"
elementFormDefault="unqualified"
attributeFormDefault="unqualified">
<import namespace="http://schemas.xmlsoap.org/ws/2004/08/addressing"/>
<import namespace="http://www.w3.org/2003/05/soap-encoding"/>

<element name="wsademoResult">
<complexType>
<sequence>
<element name="out" type="xsd:string" minOccurs="0" maxOccurs="1" nillable="true"/>
</sequence>
</complexType>
</element>

<element name="wsademo">
<complexType>
<sequence>
<element name="in" type="xsd:string" minOccurs="0" maxOccurs="1" nillable="true"/>
</sequence>
</complexType>
</element>

<element name="wsademoResult">
<complexType>
<sequence>
<element name="out" type="xsd:string" minOccurs="0" maxOccurs="1" nillable="true"/>
</sequence>
</complexType>
</element>
</schema>
</types>
<message name="wsademoResult">
<part name="parameters" element="ns:wsademoResult"/>
</message>
<message name="wsademo">
<part name="parameters" element="ns:wsademo"/>
</message>
<message name="wsademoResult">
<part name="parameters" element="ns:wsademoResult"/>
</message>
<message name="wsademoHeader">
<part name="MessageID" element="wsa:MessageID"/>
<part name="RelatesTo" element="wsa:RelatesTo"/>
<part name="From" element="wsa:From"/>
<part name="ReplyTo" element="wsa:ReplyTo"/>
<part name="FaultTo" element="wsa:FaultTo"/>
<part name="To" element="wsa:To"/>
<part name="Action" element="wsa:Action"/>
</message>
<portType name="wsademoPort">
<operation name="wsademoResult">
<documentation>accepts a string value from a relayed response</documentation>
<input message="tns:wsademoResult"/>
</operation>
<operation name="wsademo">
<documentation>echos a string value and relays the response to the wsa replyTo address (if present)</documentation>
<input message="tns:wsademo"/>
<output message="tns:wsademoResult"/>
</operation>
</portType>
<binding name="wsademo" type="tns:wsademoPort">
<SOAP:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<operation name="wsademoResult">
<SOAP:operation soapAction="urn:wsademo/wsademoPort/wsademoResult"/>
<input>
<SOAP:body parts="parameters" use="literal"/>
<SOAP:header use="literal" message="tns:wsademoHeader" part="Action"/>
<SOAP:header use="literal" message="tns:wsademoHeader" part="To"/>
<SOAP:header use="literal" message="tns:wsademoHeader" part="FaultTo"/>
<SOAP:header use="literal" message="tns:wsademoHeader" part="ReplyTo"/>
<SOAP:header use="literal" message="tns:wsademoHeader" part="From"/>
<SOAP:header use="literal" message="tns:wsademoHeader" part="RelatesTo"/>
<SOAP:header use="literal" message="tns:wsademoHeader" part="MessageID"/>
</input>
</operation>
<operation name="wsademo">
<SOAP:operation soapAction="urn:wsademo/wsademoPort/wsademo"/>
<input>
<SOAP:body parts="parameters" use="literal"/>
<SOAP:header use="literal" message="tns:wsademoHeader" part="Action"/>
<SOAP:header use="literal" message="tns:wsademoHeader" part="To"/>
<SOAP:header use="literal" message="tns:wsademoHeader" part="FaultTo"/>
<SOAP:header use="literal" message="tns:wsademoHeader" part="ReplyTo"/>
<SOAP:header use="literal" message="tns:wsademoHeader" part="From"/>
<SOAP:header use="literal" message="tns:wsademoHeader" part="RelatesTo"/>
<SOAP:header use="literal" message="tns:wsademoHeader" part="MessageID"/>
</input>
<output>
<SOAP:body parts="parameters" use="literal"/>
<SOAP:header use="literal" message="tns:wsademoHeader" part="Action"/>
<SOAP:header use="literal" message="tns:wsademoHeader" part="To"/>
<SOAP:header use="literal" message="tns:wsademoHeader" part="FaultTo"/>
<SOAP:header use="literal" message="tns:wsademoHeader" part="ReplyTo"/>
<SOAP:header use="literal" message="tns:wsademoHeader" part="From"/>
<SOAP:header use="literal" message="tns:wsademoHeader" part="RelatesTo"/>
<SOAP:header use="literal" message="tns:wsademoHeader" part="MessageID"/>
</output>
</operation>
</binding>
<service name="wsademo">
<documentation>demonstrates WS-Addressing capabilities</documentation>
<port name="wsademo" binding="tns:wsademo">
<SOAP:address location="http://localhost:11001"/>
</port>
</service>
</definitions>
This is the wsdl that is generated by JDeveloper that contains the PartnerLinks and refernce back to the original wsdl file, wsademoRef.wsdl:
<definitions
name="wsademo"
targetNamespace="http://localhost:11001/wsademo.wsdl"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:tns="http://localhost:11001/wsademo.wsdl"
xmlns:bpws="http://schemas.xmlsoap.org/ws/2003/03/business-process/"
xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
>
<import namespace="http://localhost:11001/wsademo.wsdl" location="wsademo.wsdl"/>
<plnk:partnerLinkType name="wsademoPort_PL">
<plnk:role name="wsademoPort_Role">
<plnk:portType name="tns:wsademoPort"/>
</plnk:role>
</plnk:partnerLinkType>
</definitions>
And finally the is the BPEL, WSAtest3.bpel:
<?xml version="1.0" encoding="UTF-8"?>

<process name="WsaTest3" targetNamespace="http://xmlns.oracle.com/WsaTest3"
xmlns="http://schemas.xmlsoap.org/ws/2003/03/business-process/"
xmlns:xp20="http://www.oracle.com/XSL/Transform/java/oracle.tip.pc.services.functions.Xpath20"
xmlns:bpws="http://schemas.xmlsoap.org/ws/2003/03/business-process/"
xmlns:ns1="http://localhost:11001/wsademo.wsdl"
xmlns:ldap="http://schemas.oracle.com/xpath/extension/ldap"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:ns2="http://localhost:80/Service.wsdl"
xmlns:client="http://xmlns.oracle.com/WsaTest3"
xmlns:bpelx="http://schemas.oracle.com/bpel/extension/"
xmlns:ora="http://schemas.oracle.com/xpath/extension"
xmlns:orcl="http://www.oracle.com/XSL/Transform/java/oracle.tip.pc.services.functions.ExtFunc">

<partnerLinks>

<partnerLink name="client" partnerLinkType="client:WsaTest3"
myRole="WsaTest3Provider"/>
<partnerLink name="wsademo" partnerLinkType="ns1:wsademoPort_PL"
myRole="wsademoPort_Role" partnerRole="wsademoPort_Role"/>
</partnerLinks>

<variables>

<variable name="inputVariable" messageType="client:WsaTest3RequestMessage"/>

<variable name="outputVariable"
messageType="client:WsaTest3ResponseMessage"/>
<variable name="Invoke_1_wsademo_InputVariable" messageType="ns1:wsademo"/>
<variable name="Invoke_1_wsademo_OutputVariable"
messageType="ns1:wsademoResult"/>
</variables>

<sequence name="main">

<receive name="receiveInput" partnerLink="client" portType="client:WsaTest3"
operation="process" variable="inputVariable" createInstance="yes"/>

<assign name="Assign_1">
<copy>
<from variable="inputVariable" part="payload"
query="/client:WsaTest3ProcessRequest/client:input"/>
<to variable="Invoke_1_wsademo_InputVariable" part="parameters"/>
</copy>
</assign>
<invoke name="Invoke_1" partnerLink="wsademo" portType="ns1:wsademoPort"
operation="wsademo" inputVariable="Invoke_1_wsademo_InputVariable"
outputVariable="Invoke_1_wsademo_OutputVariable"/>
<assign name="Assign_2">
<copy>
<from variable="Invoke_1_wsademo_OutputVariable" part="parameters"/>
<to variable="outputVariable" part="payload"
query="/client:WsaTest3ProcessResponse/client:result"/>
</copy>
</assign>
<reply name="replyOutput" partnerLink="client" portType="client:WsaTest3"
operation="process" variable="outputVariable"/>
</sequence>
</process>
-Wayne Stielau
Open Text Corporation
Irvine, CA

I have discovered two issues.
1. JDeveloper does not seem to like the SOAP 1.2 envelope and encoding namespaces. Is this a known limitation? Changed them to 1.1.
2. JDeveloper does not like the double definition of wsaDemoResult.
When these two items are changed, the bpel compiles clean. Now I've got to get the message header to populate correctly. There are no values assigned, only namespace definitions. This is the SOAP packet that is received at the web service.
<?xml version="1.0" encoding="UTF-8"?>
<env:Envelope
xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<env:Header>
<MessageID xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing"/>
<From xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing"/>
<RelatesTo xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing"/>
<Action xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing"/>
<ReplyTo xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing"/>
<To xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing"/>
<FaultTo xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing"/>
</env:Header>
<env:Body>
<wsademo xmlns="http://localhost:11001/wsademo.wsdl">
<in xmlns="">hello</in>
</wsademo>
</env:Body>
</env:Envelope>

11004 error SBS Exchange 2003 SP2 with POP connector. Exchange version 6.5 7638.1

Hello
I am getting loads of errors displayed in Event Viewer Application log like:-
Event ID 1035
A error occurred in connecting to the <xxx.xxxxxx.co.uk> POP3 server for user <[email protected]>. The error is 11004. The server may be down for maintenance
or your server is not connected to the Internet.
Event ID 1023
The downloading process for mailbox <[email protected] [mail.XXXXXXXXXXXXX.co.uk]> was ended with one or more errors.
The Server has 3GB memory and 64GB free disk space on the parttiion supporting Exchange
Can anyone suggest a troubleshooting scheme?

Is this machine running SBS? Is this an error that's logged by the kludgy POP3 connector? If so, that connector isn't part of Exchange -- it's something the SBS folks added. You'll have to ask our question in a SBS forum.
Keep in mind that a POP3 server will lock the mailbox if the messages are being checked by another client (unlike Exchange which allows multiple POP3 sessions). That would cause those 1035 errors to be logged by Exchange.
When you combine the 1035 with the 1023 events it looks more like connectivity problems than an Exchange problem. You might want to use a network monitor and see if the connection's being dropped.
In any case, good luck with Exchange 2003. It's no longer supported -- but I don't think your problem is related to Exchange but to the SBS add-on software.
--- Rich Matheisen MCSE&I, Exchange MVP

White space management gone on reboot

I have a strange problem here. Anytime we reboot our server,
the setting we have selected (on) for white space management in the
CF admin disappears. We can re-enable it easily of course, this is
just a mystery we would like to solve. Any ideas?
Server Details
Server Product ColdFusion MX
Version 7,0,2,142559
Edition Standard
Operating System Windows 2003
OS Version 5.2

I have noticed that numerous settings in my cold fusion
administrator are reset each time The server is rebooted or the
Cold Fusion service is restarted. These include white space
management, global script protection, and specific settings that
are needed to individual dsn settings. These can not all be
resolved by adding processing directives to the application.cfm. Is
this issue related to the fact that my only interaction with my
server is through a terminal services (RDP) connection?

IPhone 3G won't sync calendar with Exchange 2003

Hi - can't see this exact problem elsewhere hence the post...
I have iPhone 3G syncing with OWA from Exchange 2003 just fine with mail and contacts. Calendar is totally blank though. If I create a new appointment on iPhone then it shows up in Exchange - great! If I do it the other way round then I get nothing on iPhone - unless I invite myself in which case it does! But then if I delete the email invitation then the entry disappears. I could live with that (just about) but not but being able to sync my calendar history is a big problem for me.
By the way I can't sync my calendar history via iTunes to Outlook because the sync component crashes!
Can anyone shed any light?

Hi man, I got the same problem with my iPhone, but it has been solved..
First, You need the Outlook 2003 or 2007 only, if you have a earlier version of this it isn't work.
Second, You sould need to create a new PST file whit the Outlook Version 2003 or 2007, the file format must be on Unicode Format, no Outlook (97-2000) format, with this file format the import of calendar doesn't gonna be work.
Third, You now have a PST whit Outlook 2003 or 2007 Version, you need to manually put your events on the calendar, Why? Cause if you just move it on the new calendar it gonna create and old instance of the event not a new instance, That's why iTunes doesn´t sync the calendar.
I done all these and actually I can sync the calendar with my iphone.

IPhone 4S IOS5 problems sync Calendar with Exchange 2003

One of my users is having problems sync Calendar with a brand new iPhone 4S running IOS5 and our Exchange 2003 Server. If an item is updated in Outlook it will not reflect it in the iPhone or viceversa. New items show up in both, only the updates in notes or changing some text in the subject or other elements in one side is not updated in the other side. Any help will be greatly appreciate.

Hi man, I got the same problem with my iPhone, but it has been solved..
First, You need the Outlook 2003 or 2007 only, if you have a earlier version of this it isn't work.
Second, You sould need to create a new PST file whit the Outlook Version 2003 or 2007, the file format must be on Unicode Format, no Outlook (97-2000) format, with this file format the import of calendar doesn't gonna be work.
Third, You now have a PST whit Outlook 2003 or 2007 Version, you need to manually put your events on the calendar, Why? Cause if you just move it on the new calendar it gonna create and old instance of the event not a new instance, That's why iTunes doesn´t sync the calendar.
I done all these and actually I can sync the calendar with my iphone.

Exchange 2003 to 2010 Migration Mailbox Migration "Object not found"

I am introducing an Exchange 2010 Server to a single server Exchange 2003 organization. I have HT, CAS and MB roles installed already on 2010 w/ SP1. Prepped the Schema, AD, Domain and LegacyExchangePermissions by using the setup.com of the SP1
installation files.
Right now, when I try to initiate a New Local Move Request on 2010 EMC for a mailbox on Exchange 2003, I get an error for all the users saying "Object not found" with a white X in a red circle. I'm not sure what to do at this point to get Exchange 2010
recognize the 2003 mailboxes. Any ideas?
Thank you,
-S

Tim,
Here is what I'm getting from ExBPA:
Error Offline address book replica not found Organization CGU Didn't find a replica of folder 'OAB Version 4' for offline address book 'Default Offline Address List'. Either a replica doesn't exist, or this folder hasn't been created yet. If an OAB generation
attempt has not yet been made, you can ignore this error.
Error Couldn't find any writeable domain controllers Admin Group Exchange Administrative Group (FYDIBOHF23SPDLT) There were no writeable domain controllers found in Active Directory site 'Default-First-Site-Name'. At least one writeable domain controller
is required for Exchange to function properly.
Error Database backup critical Admin Group Exchange Administrative Group (FYDIBOHF23SPDLT) Database 'Public Folder Database' on server EXCH-2010 has never had a full online backup.
====
And this is what happens if I put go ahead with the move request
Summary: 1 item(s). 0 succeeded, 1 failed.
Elapsed time: 00:00:00
Test User
Failed
Error:
Mailbox database "EXCH-01\First Storage Group\Mailbox Store (EXCH-01)" doesn't exist.
Click here for help...
http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.140).aspx?v=14.1.218.11&t=exchgf1&e=ms.exch.err.Ex23B42B
Exchange Management Shell command attempted:
'cgucpa.com/Users/Test User' | New-MoveRequest -TargetDatabase 'Mailbox Database'
Elapsed Time: 00:00:00
Thank you for your help,
-S

Exchange 2003 SMTP resolves to incorrect MX record for Outbound emails

Starting October 2007, we have encountered numerous incidents where users complaint that they can not send emails to randomly with Relayed Denied error.
First we thought the problem is with the receipient servers, but after reviewing the SMTP log intensively, I have noticed that the SMTP service on Exchange Server 2003 SP2 tries to send out emails to wrong IP Addresses (instead of sending out to listed IP of MX record, it tries to send to primary domain IP address).
To test further, we have changed the DNS server of the Exchange Server to public DNS service provided by the ISPs and still received same result.
If the user tries to send the email again (from the bounced back message), it some times goes through.
Has anyone know what the problem is?
Have checked the server configuration, DNS configuration, ran all updates, and yet still same result. Is one of the Microsoft Updates causing this issue?

Here is the official explanation i got from MS, sounds like it is doing what they expect it to do.
Problem Description
When Exchange 2003 sends e-mail to the Internet using DNS to resolve external domain names a DNS query is done for the remote domain's MX records. In the event that the initial MX query returns a "server failure", Exchange 2003 will fall back to a DNS A record query. If this query is, in turn, successful and there is an A record for the domain in question that happens to be listening on port 25, Exchange will make a connection to that server. However, if this server does not relay, or accept e-mail for the intended domain a NDR will be generated with a 5.7.1, or
5.5.0 error message.
There are several domains that have A records that point to IP addresses that accept connections on port 25, but do not relay for the same name space:
Eg: Mindspring.com; Earthlink.net
Resolution
Resolve the DNS resolution problems that are causing occasional MX record failures.
Examples:
1. The Exchange server has multiple default gateways set on a multi-homed server.
This is not a recommended configuration and can cause a number of unexpected network problems. If the internal DNS server the internal NIC points to cannot resolve external DNS queries, this problem can occur.
Action: remove the default gateway from one of the NICs.
This doesn’t applies to us, as we don’t use Internal DNS
2. If the Exchange server points to multiple DNS servers on TCP/IP properties, or on the SMTP Virtual Server properties, verify that each of these DNS servers will return MX records properly. If one of the DNS servers does not return DNS records consistently, rectify this problem.
Action: remove this DNS server from the external DNS tab.
Workaround:
Bypass DNS by creating a SMTP connector with address space of <domain.com> and forward to smart host as the IP address the MX/A points to.
Exchange Query Explained
1. If Exchange finds the MX record(s) for a remote domain (through DNS query) it will not fall back to an A record query in the event the MX record (more precisely, the A record the MX record points to) is temporarily not responding on port 25. Instead, Exchange will try another MX record if one exists. If no other MX records exist and none are responding on port 25, the queue will go into a retry state for this remote domain. When that retry state has expired, Exchange will again attempt to resolve MX records for this domain, and so on.
2. Exchange will fall back to an A record query for the remote domain in the event that no MX record can be found. This is not to say that the MX record does not exist - only that when Exchange issued a DNS query for the remote domain the DNS response was "server failure", which basically means no MX was found. So, the MX record may indeed exist, but Exchange simply could not find it through DNS resolution.
3. Exchange then queries the A record and this happens to return a result. If the A record is listening on port 25, but does not accept mail for <domain.com> then we will get the NDR with 550 5.7.1 unable to relay (or some variation of this NDR error code) when Exchange connects and attempts to send the e-mail.
So, the intermittent nature of the problem is caused by a failure to find the MX record and a success in finding A record. This can happen for a variety of reasons, but it boils down to flakey DNS resolution.
For example:
a. A bad DNS server listed as a forwader on the DNS server.
b. A bad DNS server on the TCP/IP properties.
c. A bad DNS server on the SMTP VS (external DNS servers)
d. Multiple default gateways on Exchange (ie. multiple NICs on different networks, each NIC having a default GW)
A netmon on Exchange will show the failed MX lookup and successful A record lookup; however, it may not be conclusive unless the "bad" DNS server is listed in the netmon trace. For example, if Exchange points to internal DNS server(s) for name resolution and these DNS servers service these DNS queries by Exchange, you may need a netmon on the DNS server(s) as well to determine which DNS server/Forwarder/etc is at fault.
Regards,
Shahul Hameed Dasthagir
Support Engineer | Enterprise Communications Support

Exchange 2003 Outlook Webaccess support?

Hello,
I am able to access our companies Outlook Webaccess portal in Safari on a Mac but when trying to access it on the iPhone it seems to spin its wheels forever and gets very hot just after I enter the user/pass?
The screen just stays white and I guess its thinking hard on something but never gets any further. If this worked like it does on a Mac then I wouldn't need to wait for full Exchange support
Anyone able to access Outlook Webaccess from Exchange 2003?
Thanks, Tom

I have the same problem. I can access the mobile outlook website but not the regular one. Forwarding email as recommended in the thread you listed will not work for me as my emails have confidential information in them.
I did get the exchange access to work one day a few weeks ago and have not gotten it to work since then. Not sure what I did but I have been unable to reproduce it.
The problem has something to do with authentication because if I hit the mobile site and then try to hit the normal site, I can't hit the mobile site again unless turn the phone off/on. It messes something up in the authentication so it hangs until I reboot the phone.

Exchange 2003 Reclaim White Space

Similar Messages

Maybe you are looking for