Exchange 2007 fails to generate OAB. Error ID 9330 and 9334.

Hello,
I'm having issues generating/updating an OAB on my Exchange 2007. The event viewer is reporting the following errors:
Event Type: Error
Event Source: MSExchangeSA
Event Category: OAL Generator
Event ID: 9330
Date: 1/30/2014
Time: 2:07:46 PM
User: N/A
Computer: SERVER
Description:
OALGen encountered error 80040115 (internal ID 50004ef) accessing Active Directory DC-SERVER for ''.
- /o=Company Name/cn=addrlists/cn=oabs/cn=Offline Address Book
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Event Type: Error
Event Source: MSExchangeSA
Event Category: OAL Generator
Event ID: 9334
Date: 1/30/2014
Time: 2:07:46 PM
User: N/A
Computer: SERVER
Description:
OALGen encountered error 80040115 while initializing the offline address list generation process. No offline address lists have been generated. Please check the event log for more information.
- /o=Company Name/cn=addrlists/cn=oabs/cn=Offline Address Book
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
I've tried everything I have found from other similar posts without success. I have created a new Offline Address Book, I can ping and resolve DNS to Primary Domain Controller, etc
I don't know what else to do. Any help is greatly appreciated. Thanks!

The OAB is set to both web and public folder distribution.
The mailbox server does have the OAB folder and it contains a subfolder with the GUID of the default OAB, not for the new OAB I created. The same thing for the CAS server.
I ran the cmdlet with no problems. The Event viewer showed the following errors for the new OAB I created:
Event Type: Warning
Event Source: MSExchangeFDS
Event Category: General
Event ID: 1021
Date: 1/30/2014
Time: 5:32:43 PM
User: N/A
Computer: CAS-SERVER
Description:
Process MSExchangeFDS.exe (PID=2672). Could not find directory \\CAS-SERVER\ExchangeOAB\e52a1595-d9b9-45ad-a786-2e909de7ccb7. This is normal if the directory has never been generated. Otherwise, make sure this directory
and share has read permission for the "Exchange Servers" group.
That is the GUID of the new OAB that was not generated.

Similar Messages

Creating multiple mailboxes on Exchange 2007 fails

Hi All,
We have a problem to create multiple mailboxes simultaneously on Exchange 2007 using the OIM Exchange connector. Only one of the mailboxes is created when multiple powershell scripts are launched at the same time. This problem only occurs in the production environment and not on the Exchange 2007 test server. Therefore it's likely to be an Exchange 2007 server setting causing the other powershell processes and mailboxes to fail. Has anyone else experienced this problem?
Thanks,
Albin

hi.
have you managed to solve this issue? we have a similar problem when updating some exchange mailbox variables through powershell cmds via OIM. if we run several cmds simultaneously, or right after each other, only the first one is run. tried googling it, but no luck so far.
thanks,
tinba

Migration from 2003 - 2010, OAB errors on client, and OAB virtual directory does not contain any files.

Migration from 2003 - 2010, OAB errors on client, and OAB virtual directory does not contain any files.

Hi,
Please re-create the Outlook profile to have a try. If the issue persists, we can do the further checks in Exchange server.
Please make sure you have changed the OAB generation server to Exchange 2010 and enable Web distribution on the Exchange 2010 Client Access server:
Move-OfflineAddressBook "Default Offline Address List" -Server <MBX2010>
If all configurations are correct, please check whether there is any folder in the following path in Exchange sever 2010:
a. OAB generation in Mailbox:
\\Program Files\Microsoft\Exchange Server\V14\ExchangeOAB
b. OAB distribution in Client Access:
\\Program Files\Microsoft\Exchange Server\V14\ClientAccess\OAB
Thanks,
Winnie Liang
TechNet Community Support

Exchange 2013 - Import-TransportRuleCollection from Exchange 2007 failing

I am in the middle of a Exchange 2007 SP3 to Exchange 2013 Sp1/CU4 migration and am importing transport rules and it's failing.
[PS] C:\Windows\system32>Import-TransportRuleCollection -FileData C:\2007TransportRules.xml -Verbose
Cannot process argument transformation on parameter 'FileData'. Cannot convert value "C:\2007TransportRules.xml" to type "System.Byte[]". Error: "Cannot convert value "C:\2007TransportRules.xml" to type "System.Byte".
Error: "Input string was not in a correct format.""
    + CategoryInfo          : InvalidData: (:) [Import-TransportRuleCollection], ParameterBindin...mationException
    + FullyQualifiedErrorId : ParameterArgumentTransformationError,Import-TransportRuleCollection
    + PSComputerName        : ex2013-mb1.MYDOMAIN.local
Before you ask, I am still on SP1/CU4 because CU5 and CU6 are so buggy I refuse to install them. And that's probably not the fix anyway... WHEN IS CU7 coming out?

I've seen an official list but, rules that were Edge transport rules are the first ones that come to mind. After the import you can look in the EAC and it should show you any rules that have errors or you can stare and compare the rules to your 2007 environment
to determine if any weren't imported.
DJ Grijalva | MCITP: EMA 2007/2010 SPA 2010 | www.persistentcerebro.com

Exchange 2007 Out of Office Certificate Error

Hello,
I have an Exchange 2007 Server and for some odd reason this week, we have been having issues enabling Out of Office in Outlook. It is some sort of issue with the Autodiscover service, but despite reading forum post after forum post, nothing has worked for
me. At first when we would go into Outlook and click on Out of Office, it would freeze and then say the server is unavailable. I realized that it was trying to resolve a URL so I added a manual A record in the DNS server pointing to the local IP of the server
and it fixed the issue, kind of. Now when we click on Out of Office Assistant, we get a security certificate error and it is driving my users crazy. I have updated the SRV record and many things, still unable to get it to work.
Any help would be super!!
Thanks!

Hi,
1.First of all please check the name what you are using for autodiscover service is available on SAN certificate.
2.Please check the name resolution is happening for autodiscover namespace.
I.e if you try to resolve autodisccover.mydomain.com (or) mail.mydomain.com in your problematic PC it should have to resolved in to cas server ip address or in some scenarios it will get resolved in to LB
3.Then please check whether you have properly set the autodiscover internal URL in all the cas servers.
It might be like below
https:\\autodiscover.mydomain.com\autodiscover\autodiscover.xml
(or)
https:\\mail.mydomain.com\autodiscover\autodiscover.xml
4.Then please check for the web services url in all the cas servers and that is the major thing which will make the availability services (i.e OOF,free busy lookup) to work perfectly .
5.In the problematic please uncheck the internet proxy exceptions.
6.You cane use test email configuration to check whether the outlook client is fetching up the proper url for autodisocver and ews .
7.test-outlookwebservices (we can use this command to check the fuctionality of autodiscover for an problematic user account)
8.Please check the root certificates in the problematic client to check whether it is a expired or not .Root certificates is nothing but the one which will come by default with OS .
9.If all the above is set as perfect but still you are facing the issue.Please follow the below one and this may be not required.
Please export the san certificate from exchnage to pfx file which should have to include the certificate key by using MMC.Then import the pfx file in to problematic client .Let us see what happens .
Same on my side i am having few questions about your environment .
1.Are you facing any certificate errors in OWA .Because why i am asking please check the installed SAN certificate in exchange is valid and or it is not expired ?
2.what is the problematic client operating system veriosn?
Please reply me if you have any issues .
Regards
S.Nithyanandham

Provisioning to Exchange 2007 failing

Hi All,
I have installed the Exchange 2007 connector to create the mailbox of the users in the Exchange 2007. This requires Remote manager as well so did the configuration of the remote manager as per the guide.
Now when i try to provision the user to Exchange 2007 after it is successfully provisioned into AD.
The users mailbox is not created.
The Exchange provisioning task performs the following tasks.
1. first it check if the mailbox is already present in the Exchange.
2. If it is not present then it execute the scripts createmailboxexchange2007.vbs script using the remote manager.
3. It then again checks if the mailbox is created.
At this check it is giving the basically the information:
"DEBUG,09 Nov 2009 14:01:19,977,[OIMCP.MEXC],com.thortech.xl.integration.Exchange.tcExchangeTasks : checkMailboxCreation : No value for homeMDB fetched
INFO,09 Nov 2009 14:01:19,978,[OIMCP.MEXC],com.thortech.xl.integration.Exchange.tcExchangeTasks : checkMailboxCreation : Unable to execute the Power Shell command"
So basically it is not able to fetch the homeMDB as it was unable to execute the Power shell command.
I am not getting any logs on the Remote manager side but i guess the remote manager is not able to execute the power shell command.
Any ideas??

I would also check if you can call the .vbs script from a stand-alone Java program and if you really want to troubleshoot, from an RMI server that you build yourself (takes 15 mins). OIM remote manager is an RMI server. One issue could be JDK permissions (http://java.sun.com/javase/6/docs/technotes/guides/security/permissions.html), the default in the JDK you're using may not allow execution of scripts.
If the permissions are ok, I can't think of anything else. Maybe the same JDK on OIM and remote manager? It shouldn't matter but it could.

Test fails after php install: "Error executing file" and "no protocol"

With version 10.1.3.3.0, after installing the php extension, a simple test file fails with the log message of:
>>
Error executing file:/pgmdev/phpApp1/phpProj1/public_html/test1.php
Reason: no protocol: /pgmdev/test1.php
<<
Contents of test1.php:
<html>
<head>
<title>PHP Test: test1.php</title>
</head>
<body>
<?php phpinfo(); ?>
</body>
</html>
Any suggestions?

Additional info:
This is on a Fedora 8 box that is running Oracle XE and ZendCore php just fine. Running the test.php page from /var/www/html produces the expected results, so apache is running as it should. The ZendCore control panel functions as well.

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.

Exchange 2007 SP3 Search Problems

I reset all the search indices on my mailbox databases. Event viewer has told me the crawl is complete and everything checks out when I do “test-exchangeSearch”
from PS. However, the index folders are considerably smaller than the original ones, (1.3GB vs 7GB) and only about 1% of database size. Multiple users can prove to me that searches are incomplete and not returning reliable results when just doing basic folder
searches from Outlook 2007. help!
Ian

After speaking with a senior MS Engineer, if you already have SP3 applied and tried to reinstall the search as I outlined above, you have corrupt your Exchange install and the ONLY option is to rebuild the box. After reinstalling Windows and Exchange, the
proper procedure to get search working perfectly is outlined below:
4. If you haven’t already,
upgrade toExchange Server 2007 Service Pack 3.
Exchange 2007 SP3 includes several major Search-related fixes and upgrades MSSearch 3.0 to MSSearch 3.1. This is a highly significant
upgrade.
5. Update to the latest available Rollup Update.
There are some very significant search fixes in the Rollup Updates for Exchange 2007 SP3. Some of these fixes are absolutely essential to install.
For example, Exchange 2007 SP3 Rollup Update 2 includes a fix that allows Exchange server to index emails even when the attachment cannot
be parsed – this is the number one call generator for Exchange 2007 search support cases.
To restate, upgrade to the very latest available Exchange 2007 SP3 rollup update, as there are many more search fixes available in the latest
rollup updates.
6.
Install IFilters and register them – follow ALL the steps below.
Install Filter Pack 1.0, which allows Exchange 2007 to index Office 2007 documents:
2007 Office System Converter: Microsoft Filter Pack
http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=20109
7. Install the hotfix which addresses a known issue when search crawls a .vsd file.
960502 Description of the 2007 Office system hotfix package (Offfiltx.msp, Visfilter.msp): December 16, 2008
http://support.microsoft.com/default.aspx?scid=kb;EN-US;960502
Additional Information on the hotfix:
960166 Error message when a search process crawls a .vsd file on a Windows 64-bit operating system that is running the 2007 Office Filter
Pack: "The filtering process has been terminated"
http://support.microsoft.com/default.aspx?scid=kb;EN-US;960166
8.
Register the Filter Pack 1.0 IFilters. This is a manual process with Exchange 2007 but we have created a script to automate the process.:
944516 How to register Filter Pack IFilters with Exchange Server 2007
http://support.microsoft.com/default.aspx?scid=kb;EN-US;944516
9. Install Filter Pack 2.0 which allows Exchange to index Office 2010 attachments as well as some additional file types.
Download details: Microsoft Office 2010 Filter Packs
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=5CD4DCD7-D3E6-4970-875E-ABA93459FBEE&displaylang=en
10. Register IFilters 2.0 with Exchange 2007.
How to Register IFilters 2.0 with Exchange 2007 and Exchange 2010
http://technet.microsoft.com/en-us/library/ff354976(EXCHG.80).aspx
11. Disable signature verification for the Exchange 2007 search services by putting 127.0.0.1 crl.microsoft.com in the HOSTS file.
Certificate Revocation List
When the Microsoft .NET Framework 2.0 loads a managed assembly, the managed assembly calls the CryptoAPI function to verify the Authenticode signature
on the assembly files. The CryptoAPI function checks a Certificate Revocation List
(CRL) that is available at http://crl.microsoft.com
. This action requires an Internet connection.
The
Microsoft Search Indexer service (Microsoft.Exchange.Search.ExSearch.exe)
is a managed assembly that is loaded by Microsoft .NET Framework 2.0. After installing Exchange 2007 SP3, if the Exchange server or DNS cannot resolve
http://crl.microsoft.com for any reason
the outgoing HTTP requests may be dropped and an error message is not returned. This delay causes the CRL to time out and cached CRLs will expire. This affects the Microsoft Search Indexer service in such a way that any new email fails to be indexed.
Instructions to Modify HOSTS file on the Exchange 2007 Server
Add the following:
127.0.0.1 crl.microsoft.com – here are the instructions:
a. Go Start – Programs and choose Command Prompt and choose Run as Administrator.
b. Within the Command Prompt, change to this directory (the drive will be the one where you installed the OS):
C:\Windows\System32\drivers\etc\hosts
c. Add the following entry to the HOSTS file:
127.0.0.1 crl.microsoft.com
d. Save the HOSTS file.
13.
Rebuild Indexes
using ResetSearchIndexes.ps1
How to Rebuild the Full-Text Index Catalog
http://technet.microsoft.com/en-us/library/aa995966(EXCHG.80).aspx
a. Go Start – Programs and choose Exchange Management Shell and choose Run as Administrator.
b. Change to this directory (the drive will be the one where you installed Exchange 2007):
C:\Program Files\Microsoft\Exchange Server\Scripts
c. It is suggested that you rebuild indexes for one or a few databases at a time – use the following command to rebuild the indexes for 1
databases called dbname1 and dbname2:
.\ResetSearchIndex.ps1 –force dbname1 dbname2
d. It is suggested not to run the following command unless you have 1 Exchange 2007 server only in your environment because it will cause
all databases on all Exchange 2007 (and all Exchange 2010 servers, if there are any) to be reindexed at that same time:
.\ResetSearchIndex.ps1 –force all
14.
Monitor the Application Event Log for Event ID 110 for a particular database.
This will indicate the new index is complete for that database.
15. After receiving Event ID 110 for a database, check to see if the size of the CatalogData folder for that database is the expected
5% to 10% of the database size. If the size of the CatalogData folder is significantly smaller than that or if the size is a few kb or a few mb, go
to Step 17.
16. After you have received Event ID 110 and the size of the CatalogData folder is normal, test searching in Outlook online mode
and OWA to make sure search is working.
<strike>
</strike>
Ian

Outlook 14.4.8 not synchronizing with Exchange 2007 anymore (shows "downloading" but no new messages shown in inbox"

Outlook 14.4.8 on iMAC Retina and Yosemite 10.10.2 is not synchronizing with Exchange 2007 anymore (shows "downloading" but no new messages shown in inbox".
Accessing Mails with Webbrowser and from Windows Outlook is working correctly.
All Macs (also the ones with OS 10.6.8) do not anymore show any new messages in inbox.
Restarted Server, tried to disable autodiscover on macs and deleting/adding account and repairing database does not fix the problem. Also restarted server several times.
We have the same problem on 2 imacs retina with yosemite and on 2 mac pro with 10.6.8 and different office 2011 versions.
i tried to configure the exchange account in apple mail on yosemite and it also states "connected" and does list some folders but no new mails are getting in.
Windows clients and outlook on them works and syncs fine, and also when connecting via webbrowser at owa it must be a mac-specific/webdav issue.
exchange 2007 Sp3 Version 8.3 (bild 83.6) and Update Rollup 15 for sp3 (automatic updates "HIGH" for server and clients)
there is one update popping up again and again even after everytime successull installation: Windows Mlicious Software Removal Tool x64 - October 2010.
i tried to configure a new user with empty mailbox and configured it with microsoft mail (mac - yosemite) as exchange and was able to send a mail from there (even if quite delayed).
but there are not coming in any mails.
same exchange accounts triggered by imap do work and also via owa.
Exchange Accounts in Outlook for MAC and also in Mail (Yosemite) do show the folder structures but there is no mails showing up. I can send mails from the exchange accounts created but they seem to be processed with a delay of like 15minutes and outlook
is giving error "end of file reached" but messages are send after some time.
Does seem like EWS is extremely slow, to slow perhaps to sync and therefore ending in timeout.
Also i cannot reach the server from externally over ssl https 443. if testing port 443 of exchange from outside the port seems closed even firewall settings of sbs 2008 and sonicwall ports are correctly open.
could it be there is something in regarding webdav which is very slow and leading to timeouts ?
in application log i do have the following two information events every few minute:
The Exchange Web Services started successfully. Event ID 1
and
Process STORE.EXE (PID=3688). Exchange Active Directory Provider has discovered the following servers with the following characteristics:
(Server name | Roles | Enabled | Reachability | Synchronized | GC capable | PDC | SACL right | Critical Data | Netlogon | OS Version)
In-site:
SERVER.org.local CDG 1 7 7 1 0 1 1 7 1
Out-of-site:
Errors in Application log:
The Open Procedure for service "BITS" in DLL "C:\Windows\system32\bitsperf.dll" failed. Performance data for this service will not be available. The first four bytes (DWORD) of the Data section
The entry <C:\WSUS\WSUSCONTENT\CONTENTFOLDERACLSCHECK.TXT> in the hash map cannot be updated.
An exception Microsoft.Exchange.Data.Storage.ConversionFailedException occurred while converting message Imap4Message 69447
Also outlook 2011 clients are asked by time to time to reenter pwds and errors like "connection is closed. 13"
Faulting application taskeng.exe, version 6.0.6002.18342, time stamp 0x4cd34898, faulting module ntdll.dll, version 6.0.6002.18881, time stamp 0x51da3d16, exception code 0xc000071b, fault offset 0x0000000000082445, process id 0x3288
Certificate Services Client Provider pautoenr.dll raised an exception. Exception code 3221225477.
Backup Exec:
FULL_BACKUP -- The job failed with the following error: A failure occurred querying the Writer status.
Volume Shadow Copy Service error: A critical component required by the Volume Shadow Copy service is not registered. This might happened if an error occurred during Windows setup or during installation of a Shadow Copy provider. The
error returned from CoCreateInstance
Exchange VSS Writer (instance 2d932ef8-6319-4ab8-a45f-1242480b44ad:15) failed with error code 1295 when processing the backup completion event.

Hi,
Since Outlook running on Windows works well, it seems an issue on the Mac side. I suggest ask Mac for help so that you can get more professional suggestions.
More information for your reference:
Please try to verify whether there is any expired certificate from the computer personal store.
If it is the case, please remove them.
Thanks
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Mavis Huang
TechNet Community Support

FPGA Code Generation fails with error codes 7 and -1

Hi all,
I have been having a weird issue with my LV FPGA compilation in the last couple of days, no matter what I try to compile LV fails to generate the FPGA code files and returns with errors 7 and -1 and complains that the file is not found. This happens no matter what I am trying to compile even a VI with just a while loop. I followed the discussion forum here without any luck, also followed the NI article here and that did not help either. The error codes always get generated at the start of the Generating Intermediate files step #7 (out of 7).
Attached to this post is a screenshot of the error I am getting (error -1 just says internal error and to contact NI support), bellow is basically the error I get for error code 7
An internal software error has occurred. Please contact National Instruments technical support at ni.com/support with the following information:
Error 7 occurred at Read from Text File in nirviGetInstantiation_cRIO-IDSel_Timer.vi->nirviGetInstantiation_cRIO-IDSel_Timer.vi.ProxyCaller
Possible reason(s):
LabVIEW: File not found. The file might have been moved or deleted, or the file path might be incorrectly formatted for the operating system. For example, use \ as path separators on Windows, : on Mac OS X, and / on Linux. Verify that the path is correct using the command prompt or file explorer.
=========================
NI-488: Nonexistent GPIB interface.
C:\NIFPGA\compilation\cRioController_8-SlotFPGA_FPGA-TriggerTest_C06156E2\IDSel_Timer.vhd
I tried to do some digging to see what could possibly be happening, and I noticed that LV is looking for the vhdl files in the wrong folder (see the line highlighted in red above), when generating the vhdl files, LV will place them inside the "source_files" folder under the compilation project, but for some reason it is trying to find them under the root folder not inside the source_files folder!!!
Does anyone have any idea why LV would be looking for these files in the wrong subfolder?
Thank you,
Aws
Attachments:
Code Generation Errors.png ‏35 KB

Hi Aws_Khudhair,
What version of LabVIEW are you using? And what version of the FPGA module? From what I found, it seems as though this is primarily an issue with LabVIEW 8.6 and 8.6.1.
http://digital.ni.com/public.nsf/allkb/A711119FE89E39E78625754E00075E92
This forum also discusses a similar issue:
http://forums.ni.com/t5/Real-Time-Measurement-and/FPGA-compile-errors-after-generating-intemediate-f...
It may also be worth repairing/reinstalling the FPGA Module and the Xilinx compile tools.
Catherine B.
Applications Engineer
National Instruments

Exchange 2007 to 2013 Migration Outlook Anywhere keeps asking password

Hi all,
i'm migrating an Exchange 2007 Server with all roles installed on a Windows Server 2008 R2 to 2 Exchange 2013 SP1 Servers (1 Cas and 1 Mailbox) installed on Windows Server 2012 R2.
I installed Exchange 2007 SP3 RU13 for coexistance and everything was ok until i switched to the new 2013 CAS.
After that the client using Outlook Anywhere started asking for password.
I configured the Outlook Anywhere with these settings:
Exchange 2007:
OA Hostname mail.domain.com
Client Authentication NTLM
IISAuthenticathion Basic, NTLM
SSL Required True
Exchange 2013
OA Hostname mail.domain.com
Client Authentication NTLM (Both internal and external)
IISAuthentication Basic, NTLM
SSL Required True (both internal and external)
Before switching to 2013 Cas everything works smoothly and the Outlook clients receive NTLM as HTTP Proxy authentication.
After switching to 2013 Cas, test users migrated on 2013 Mailbox Server are ok, but Outlook users on Exchange 2007 Server get Basic as HTTP Proxy authentication and continue asking for credentials.
In the Exchange 2007 server i configured the host file to resolve servername and servername.domain.local with the ipv4 address to avoid issues regarding IPv6 with OA in Exchange 2007.
Using Microsoft Connectivity Test i receive the error "RPC Proxy can't be pinged - The remote server returned an error:
(500) Internal Server Error"
Any Ideas?
Thanks for your Help

Run this and post the result
https://testconnectivity.microsoft.com/
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.

SBS 2003 to Server 2008/Exchange 2007

We are in the process of moving our location and are in need of moving
from SBS to something with more CALs. I want to make this as seemless
as possible for the end-users.
We are currently on SBS 2003.
My plan:
Purchase new 64 bit server with Server 2008 and Exchange 2007.
Add new server to existing domain.
Move/migrate exchange from SBS to new server.
Make sure the user info and and Group profiles move to the new server
(not sure how to do that)
Remove the SBS, and promote the new 2008 to DC.
Possibly rename the 2008 to the same name and IP as the old SBS (so
outlook users do not have to change anything)
Would that be the correct route? If so, what am I missing? (Looks
easy on paper)
Thanks,
Mike

hi
here is a lead
Start by installing Windows Server 2008 on the server you’re intending on using for mail. In our example we installed all the Exchange functionality on a single server – in practice you’ll probably want to separate out the Hub and Storage
functions, and use a separate Edge server for mail traffic and user access to mail. There’s no problem with connecting to the network while you’re doing the install – Windows Server 2008 installs as a workgroup server – and you’ll
automatically be delivered the latest drivers and the most up to date OS patches. You’ll also need to give the server an appropriate fixed IP address, as it’s going to become a key component of the network infrastructure.on the role and feature-based
install model introduced with Windows Server 2003 and enhanced in Windows Server 2003 R2. Make sure you use these tools to install Internet Information Server – as Exchange 2007 will use it for Outlook Web Access and Exchange ActiveSync. Exchange 2007
requires that servers have the PowerShell management scripting environment and the
.NET framework. We’d also recommend installing Terminal Services as part of any Windows Server installation, as using Remote Desktop to access the new server and the existing SBS 2003 domain controller will let you handle much of the
migration process from the comfort of your desk.Once Windows Server 2008 has been installed, take out the install DVD and shut the server down. As you’re going to be adding a Windows Server 2008 machine to what’s really a Windows Server 2003 network,
you need to upgrade the Active Directory schema on our SBS 2003 server. This will allow you to manage the Windows Server 2008 machine from the SBS 2003 machine. You may need to update your version of Remote Desktop to one that supports the latest versions
of the RDP protocol.Put the Windows Server 2008 DVD in your SBS 2003 machine’s DVD drive (a network accessible DVD drive is suitable, especially if access to any machine room is limited, and you’re using Remote Desktop to manage
the server). Open a command line and change directory to SOURCES\ADPREP. You need to use ADPREP.EXE to update the Active Directory schema. Start by typing the following command to update the Active Directory forest.adprep.exe /forestprep.This will
begin the process of updating the schema. Be prepared to wait some time, especially if you’re working with SBS 2003 rather than SBS 2003 R2. Once the forest schema has been updated you can update the domain schema. Type the following command:adprep.exe
/domainprep.You’re now ready to bring the new Windows Server 2008 machine into your existing domain. Turn on the server, and then log in as a local administrator. Again, you can use Remote Desktop to work with the server, so you don’t need
to sit in the machine room.to the existing SBS-managed domain. Once the server is part of the domain, you will to promote it from a member server to a domain controller. Launch DCPROMO
using the Start menu search bar to find the program. Choose to add a domain controller to an existing domain. You’ll need to use the credentials of an existing domain administrator to start the process.Make the server a Global Catalog server.
If you’re going to be keeping the existing SBS 2003 system there’s no need to make the new server a DNS server. DCPROMO will then add the requisite Active Directory Domain Services to your Windows Server 2008 machine. This can take some time, especially
if you’re working with a large SBS-managed network with more than 50 users. Once the DCPROMO process is complete you’ll need to restart the server. You can now log in as a domain administrator.Now you can start the process of installing Exchange
2007 on the new server. There’s one key issue that needs to be dealt with first. Exchange 2007 needs to install on a server that’s a Schema Master.
One of the limitations of SBS 2003 is that the SBS server needs to own all five of the FSMO
roles. The Flexible Single Master Operations are key domain management tasks, and in a standard Active Directory implementation, these roles can be parcelled out across several servers. Microsoft’s restrictions on SBS can be overcome –
as the SBS licence allows FSMO roles to be temporarily transferred to other servers for the purpose of server migration and major hardware upgrades. You can continue to run SBS for up to seven days (there is an option to install an update that extends this
to 21 days) with the FSMO roles on other servers. Don’t let the migration drag on as after that point, the server will reboot every hour, until the roles are transferred back.You’ll need to be logged in to your SBS server to move the Schema Master
to the Windows Server 2008 machine. Start by registering SCHMMGMT.DLL. This allows you to use the Windows Schema Master management tools to transfer the Schema Master role to the Windows Server 2008 machine. Open a command line and type the following command.regsvr32
schmmgmt.dll
You’ll next need to open the Windows Management Console. Once you’ve done this, by typing
mmc at a command prompt or from the Run option on the start menu, you can load the Active Directory Schema management snap-in. From the File menu click Add/Remove Snap-in. This opens a dialog box where you can choose to add the appropriate
tools. Choose Active Directory Schema. This will load the schema management tools, which you can use to move the Schema Master to a new machine.In the Schema Manager console, right click on Active Directory Schema and then choose Change Domain Controller.
You’ll see a list of available servers. Choose the new Windows Server 2008 machine, and then click Change to move the Schema Master role to your new Exchange machine. Right click Active Directory Schema again, and choose Operations Master. This allows
you to make the new server the operations master for the FSMO role we’ve just transferred.
Now you can start the Exchange 2007 installation. Log on to the server, and load the Exchange 2007 DVD; using an Exchange 2007 SP1 DVD reduces the amount of time you’ll need to set aside for downloading and installing uploads. Choose the appropriate Exchange
installation for your network needs – a typical install with Hub Transport, Client Access and Mailbox roles should be sufficient for most small networks. Once Exchange has installed, restart the Windows Server 2008 machine and then open the Exchange
Management console to confirm that your install completed successfully.You will now have added your new Exchange server to the existing SBS Exchange network. On the SBS server open the Exchange System Manager.Expand the Administrative Groups tab to see the
available administrative groups. Your new server should have added itself as Exchange Administrative Group (FYDIBOHF23SPDLT). Do not move it out of this Administrative Group or the associated routing group, Exchange Routing Group (DWBGZMFD01QNBJR) –
these are required to allow Exchange 2007 to interoperate with Exchange 2003. (As a side note, there’s definitely a sense of humour in the Exchange team at Microsoft, as the default administrative group and routing group names are both Caesar Ciphers
of EXCHANGE12ROCKS).If you’re planning to run the two servers together, you can now move the Schema Master FSMO role back to the SBS server; if you’re not, you now have seven days to finish your complete server migration before the reboots start.
To move the role back use the Active Directory Schema MMC snap-in and change both Domain Controller and Operations Master to point to your SBS server.Now you can start to move mailboxes between the two servers. This is where things can start to take time,
so schedule mailbox moves for evenings and weekends – and make sure that you’ve backed up all the existing mailboxes before you start the migration.
You’ll also need to make sure that both servers have the same mailbox size limits – otherwise large mailboxes will fail to move successfully. If you’re unable to make moves at night, you can do them during working hours –
but users will be unable to connect to the Exchange server while their mailboxes are being transferred (remember to warn them in advance). Any mail that’s been delivered to the server during a mailbox transfer will be queued and delivered once the mailbox
is on the new server.
The actual process of moving mailboxes from the SBS Exchange 2003 server to Exchange 2007 is relatively simple. Log on to your Exchange 2007 server, and open the Exchange Management Console. Expand Recipient Configuration, and select the Mailbox
view. This lets you see the organisation’s mailboxes, along with where they’re currently stored. A pane on the right gives you various Actions you can perform on the mailboxes. These include the Move Mailbox wizard.
This wizard is the simplest way of moving mailboxes between servers – and, along with the underlying move – Mailbox PowerShell commandlet, is the only supported way of moving mail to an Exchange 2007 server. If you’re moving a large set of
mailboxes it’s worth writing a PowerShell script to handle the move for you.
Use the Move Mailbox wizard to move either an individual mailbox or groups of mailboxes (shift-click to select several at once). As the wizard is multi-threaded it can handle up to four mailbox moves at once. First select the target database, and then choose
the move options. You can choose to abort the move if corrupted messages exist, as well as choosing the appropriate Active Directory servers. You can also schedule the moves for out of hours – so you don’t have to be on site for a move to take
place – as well as making sure that any moves that haven’t taken place inside a set time limit are cancelled. The wizard will check mailbox quotas before making a move to make sure that the system limits allow the mailbox to transfer to a new server.
Once a move’s started you’ll see a progress bar showing the status of the move, with descriptive text for the current step in the move process. When a move completes there’s a summary screen with the results. There’s also an XML
format report you can use for further analysis.
We found that a large 4GB mailbox took about 3 hours to move, over a gigabit network. In practice, most mailboxes are a lot smaller, so expect to be able to move many more SBS mailboxes in a single overnight session. Once the mailboxes have been moved, your
Outlook users will automatically be switched to the new Exchange server. There’s no need to change anything on the desktop – the Exchange organisation will handle the changes for you. There’s one exception; if you have used a self-certified
certificate for the SBS Exchange server, you may need to delete it from all client devices (including Windows Mobile) so they can connect – especially if you’re using the same external DNS name.While Outlook handles the changes gracefully, things
aren’t so easy for users working with ActiveSync connections to mobile devices or for secure IMAP and POP3
connections. Mobile users will need to perform a manual sync on their phone (they’ll get a message in ActiveSync reminding them to do this) and accept the server policies before mail will start arriving. POP3 and IMAP connections will only continue
to work if you make sure that your new mail server has the same external CNAME as the old SBS install. If you’re not using the same DNS name, you’ll need to recreate connections for external mail clients.
Naeem Bhatti MCITP EA, MCITP, MCTS Exchange 2007 MCSE security,MCSE AD, MCSE in Messaging, MCDST SBS2003 and SBS2008 Specialist

Cannot uninstall Exchange 2007

When I try to uninstall Exchange 2007 I get the following error under the Mailbox Role.
The virtual directory 'ExchWeb' already exists under 'server.domain.com/Default Web Site' Parameter Name: VirtualDirectoryName.
I actually tried removing the ExchWeb virtual directory on the Exchange 07 server but that didn't help. I haven't been able to find anything else on the internet regarding this issue.
Vincent Sprague

Hi,
From error "Exchange server "server" was not found. Please make sure you have typed it in correctly", I recommend you check if the Exchange 2007 server is under the CN=Servers container in ADSIEDIT.
If it is there, based on the situation, you couldn't uninstall Exchange 2007 Mailbox role via Add/Remove Programs or using Setup.com /mode:uninstall /role:<server roles to remove> command. The last resort is to uninstall Exchange 2007 Mailbox role
using ADSIEDIT, the method using ADSIEDIT should be only be used carefully.
If it isn't there, maybe the suggestion mentioned in the following thread can help you.
Unable to uninstall Exchange 2007 SP2 'Exchange server was not found.' - manual uninstall time?
http://social.technet.microsoft.com/Forums/exchange/en-US/fbea8afb-3d50-4ed1-b2f5-9bd28f648815/unable-to-uninstall-exchange-2007-sp2-exchange-server-was-not-found-manual-uninstall-time?forum=exchangesvrgenerallegacy
Here is an article about how to remove Exchange 2007 from a computer for your reference.
How to remove Exchange 2007 from a computer:
http://support.microsoft.com/kb/927464
Best regards,
Belinda
Belinda Ma
TechNet Community Support

PNTLEASE.fmx form failed to generate

Hello
Ebs: 12.1.3
Db:11.2.0.2
Os:win 2003 R2 (32 Bit)
The PNTLEASE.fmx form failed to generate
I am getting following error message while generating forms from adadmin:
The following Oracle Forms objects did not generate successfully:
pn      forms/US        PNTLEASE.fmx
I have also try to generate above form manually, but failed to generate with error code: 30119
Your help will be appreciated.
Thank you !
Regards
Syed

Hi Hussein
Thanks for your reply
PNTLEASE.fmx from generated manually after rebooting of OS
yesterday, I got following compilation errors
Compiling WHEN-VALIDATE-ITEM trigger on SHOW_ZERO_AMOUNTS item in PAYMENT_QF_BLK data block...
Compilation error on WHEN-VALIDATE-ITEM trigger on SHOW_ZERO_AMOUNTS item in PAYMENT_QF_BLK data block:
PL/SQL ERROR 302 at line 1, column 25
component 'SHOW_ZERO_AMOUNTS' must be declared
PL/SQL ERROR 0 at line 1, column 1
Statement ignored
Compiling WHEN-CHECKBOX-CHANGED trigger on SHOW_ZERO_AMOUNTS item in PAYMENT_QF_BLK data block...
Compilation error on WHEN-CHECKBOX-CHANGED trigger on SHOW_ZERO_AMOUNTS item in PAYMENT_QF_BLK data block:
PL/SQL ERROR 302 at line 1, column 25
component 'SHOW_ZERO_AMOUNTS' must be declared
PL/SQL ERROR 0 at line 1, column 1
Statement ignored
Now, No compilation errors in PNTLEASE.err file
Compiling WHEN-VALIDATE-ITEM trigger on SHOW_ZERO_AMOUNTS item in PAYMENT_QF_BLK data block...
   No compilation errors.
Compiling WHEN-CHECKBOX-CHANGED trigger on SHOW_ZERO_AMOUNTS item in PAYMENT_QF_BLK data block...
   No compilation errors.
FRM-30351: No list elements defined for list item.
List INCLUDE_IN_VAR_RENT
FRM-30351: No list elements defined for list item.
List SOURCE_MODULE
FRM-30351: No list elements defined for list item.
List INCLUDE_IN_VAR_RENT_MIR
Created form file S:\oradev\DEV\apps\apps_st\appl\au\12.0.0\forms\US\PNTLEASE.fmx
Many Thanks
Regards,
Syed

Exchange 2007 fails to generate OAB. Error ID 9330 and 9334.

Similar Messages

Maybe you are looking for