Yesterday I performed an upgrade on our Exchange Server 2003 Standard to Exchange 2003 Enterprise (OS is Win 2003 Standard). I Ordered the Exchange 2003 Enterprise Media from Microsoft and used the CD labeled "Microsoft Exchange 2003 Server Enterprise, August 2003". When I did the upgrade from Standard to Enterprise I used the "Reinstall" option and ran theran setup.exe in the \SETUP\I386 folder and selected Reinstall. Once the Install was completed I reinstaled Exchange Server SP2. After SP2 was installed I restart the server.After Server was restarted I looked in the Event Viewer>Application log and did not find Event ID: 1217. However, I found two Event ID: 1216 shown as follow:(First Entry)Event ID: 1216 Time: 2:10:39 PM The Exchange store 'First Storage Group\Mailbox Store (DC-SERVER)' is limited to 75 GB. The current physical size of this database (the .edb file and the .stm file) is 67 GB. If the physical size of this database minus its logical free space exceeds the limit of 75 GB, the database will be dismounted on a regular basis. (Second Entry)Event ID: 1216 Time: 2:10:39 PM The Exchange store 'First Storage Group\Public Folder Store (DC-SERVER)' is limited to 18 GB. The current physical size of this database (the .edb file and the .stm file) is <1 GB. If the physical size of this database minus its logical free space exceeds the limit of 18 GB, the database will be dismounted on a regular basis. Since we had Exchange 2003 Standard there is an entry in the registry for database size. I had to increase database size few times. Under HKLM\SYSTEM\CURRENTCONTROLSET\SERVICES\MSEXCHANGEIS\SeverName\PrivateSTORE{guid} there is an entry "Database Size Limit in Gb". Before the upgrade the database size was set to 70GB. so I went and changed to 80 and performed net stop msexchangeis and net start msexchangeis, but for some reason the no events were logged to Application indicating database size was increased. Not sure if this is needed or not or if it will make any difference.At this point I was not sure if the upgrade to Exchange 2003 Enterprise was done or completed correctly. So, I opened ESM and under Administrative Group>First Administrative Group>Servers>DC-Server it showed the Edition as Standard and the Version as "Version 6.5 (Build 7638.2 Service Pack 2" and modified data is 11/1/09. Not sure why it still shows as Standard and not Enterprise?I checked the following article http://support.microsoft.com/kb/240152/en-us for the key that points to either Exchange 2003 Standard or Enterprise and under HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Uninstall I am able to find the key: F95DE19F-CF69-4b03-81B6-9EC050D20D3B: Enterprise Full Packaged Product (FPP) . So the registry shows that I have Exchange Enterprise but ESM shows Standard.I did few more searched on the web and someone suggested I create a new Storage Group and a Mailbox Store. So, I went to ESM and under Administrative Group>First Administrative Group>Servers>ServerName I created a New Stroage Group called "Test Storage Group". I already have a storage group called "First Storage Group". Next I right clicked on Test Storage Group>New>Mailbox Store and I got the following error message "This storage group already contains the maximum number of stores allowed. ID no: c1034a7a Exchange System Manager". When I created the Test Stroage Group I created a new folder under C:\Program Files\Exchsrvr\2ndStorageGroup for Transaction Log location and System Path location. Hopefully Someone will help me in resolving this mess.Thanks,B

Hi,You are still getting the Standard Edition Event IDs and you are unable to create additional mailboxes, hence your upgrade has not been successful. How do you confirm that your upgrade was done properly. Do you see the version as Enterprise, No?I would re-run the Upgrade after confirming it is the right media. Refer: http://support.microsoft.com/default.aspx?id=170280. Then Refer for Version: http://www.petri.co.il/whats_my_exchange_2000_2003_version.htmLet us knowNitin Gupta (gupnit) | MVP - Exchange | http://www.nitingupta.in/blogs

I purchased the media directly from Microsoft...is it possiblethat they send me the wrong CD?After all I used the CD labeled "Microsoft Exchange 2003 Server Enterprise, August 2003" and selected Reinstall. I did however get a message during install that somefiles on the server are newer than the ones being installed so I picked the option to overwrite files on the server. Along with the purchase I got the following MediaMicrosoft Exchange 2003 Server Enterprise with Service Pack 2 - I used this CD to reinstall Service Pack 2Microsoft Exchange 2003 Server Enterprise With Outlook, October 2003 - I did not used this CD at all.After the upgrade I am getting conflicting version, in ESM it shows the version as Standard, but in the Registry it shows the key for Exchange 2003 Enterprise.

Can you reconfirm and check http://www.petri.co.il/whats_my_exchange_2000_2003_version.htmAlso you can have a look into this http://forums.msexchange.org/m_140017900/mpage_1/key_/tm.htm#140017913Raj

Per article http://www.petri.co.il/whats_my_exchange_2000_2003_version.htmMethod #1: it shows Version 6.5 (Build 7638.2 Service Pack 2)Method #2: in the ESM the Edition shows as "Standard".Method #3: I don't see Event ID 1217. Everytime I restart the Server I only see Event ID 1216 as posted in my original post.Method #4: I created a new storage group called "Test Storage Group" and when I attempted to create a Mailbox Store within that storage group I got the error message ""This storage group already contains the maximum number of stores allowed. ID no: c1034a7a Exchange System Manager".Method #5: Which is looking for entries in the registry regarding the keys for exchange version. I looked in HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Uninstall per http://support.microsoft.com/default.aspx/kb/240152/en-usand for Exchange 2003 I have the following key only: F95DE19F-CF69-4b03-81B6-9EC050D20D3B Which pers Mircosoft article is for Enterprise Full Packaged Product (FPP). Not sure if this make a difference but under Uninstall in the Registry I see first a list of keys that all start with "{", next entry for AddresBook, ATI DIsplay Driver, Branding, Connection Manager, Direct Animation, DirectDrawEX, DXM_Runtime, followed by the key for Exchange Enterpise F95DE19F-CF69-4b03-81B6-9EC050D20D3B with no "{".I no longer see the key 9161A261-6ABE-4668-BBFA-AD06B3F642CF: Standard Full Packaged Product (FPP) listed.When I did the upgrade from Standard to Enterprise I did run the setup.exe from within i386 and did select "Reinstall" option.The Media I recevied from Microsoft (ordered last month) contained the CDs listed below. I first Installed CD #1 then installed CD #3 and restarted the server. During the install from CD#1 I did however get a messagethat somefiles on the server are newer than the ones being installed from the CD, so I picked the option to overwrite files on the server with ones listed on CD.CD #1 Microsoft Exchange 2003 Server Enterprise, August 2003 - Servers Server Application Part No: 395-03025 CD #2 Microsoft Exchange 2003 Server Enterprise (Outlook Standard 2003) (Product Key Required) - October 2003 Servers Server Application Part No. 395-03025 CD #3 Microsoft Exchange Server 2003 Service Pack 2 (For Standard and Enterprise) December 2005 Part No. 395-03025

Have you seen:http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/Q_21715286.html?"There are 2 keys in the registry that tell what version of Exchange it is running:a) HKLM\Software\Microsoft\Microsoft Integration\<Guid>\SuiteIDb) HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall<Guid>Upon re-install another key was created under HKLM/Software/Microsoft/Microsoft IntegrationThe original key(standard version) continues to override the re-install(enterprise version) which is why Exchange continues to believe that it is standard edition. Once you remove the original key and re-run re-install, the server will then run as a enterprise product. If you just remove the key and restart the server, it will still state that it is a standard editionin system manageryou had mentioned earlier "both keys for the standard version and for the enterprise version are present.""

Under HKLM\Software\Microsoft\Microsoft Integration\<Guid>\SuiteID I see both Standard Editiona and Enterprise Edition keys listed.HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall I only see the Enterprise Key listed as I stated before. No Standard Edition key.From this article http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/Q_21715286.htmlonly suggestions were given and the post did not complete. I don't want to keep reinstalling or cause any damage.Maybe I should talk the Microsoft Support Gurus (even if it is going to cost some money) and see if they have a solution for this mess but I have a feeling they would just tell me to reinstall.

Yes, I agree. If there is any doubt, its always a good idea to call Microsoft support.

As I research this more...When I upgrade from Exchange 2003 Standard to Exchange 2003 Enterprise do i need to use a different Serial key or will my existing key for Exchange 2003 Standard continue to work.I looked under Under HKLM\Software\Microsoft\Microsoft Integration and as I mentioned before I have the following Entries:HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Integration\9161A261-6ABE-4668-BBFA-AD06B3F642CFHKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Integration\F95DE19F-CF69-4b03-81B6-9EC050D20D3BBoth Keys show same PID2.0, PID3.0 (Serial key), and same InstallFrom directory.When I did the reinstall using Exchange Enterprise 2003 I did not get prompted for new serial key.

Everything looks ok to me in terms of what you did and the media. Press the Button !Nitin Gupta (gupnit) | MVP - Exchange | http://www.nitingupta.in/blogs

Hi,Please first go into registry:HKLM\SYSTEM\CURRENTCONTROLSET\SERVICES\MSEXCHANGEIS\SeverName\PrivateSTORE{guid} and check whether Database Size Limit in Gb registry key is set or not.If it was set, please back up the registry and then delete it. After that, please restart the Microsoft Exchange System Attendant and Information storeservice and check this issue.ThanksAllen

OK...I deleted the Database Size Limit in Gb from registry and restarted the entire server. Once restart was completed I see the following entries: Event ID: 1216 Source: Description: The Exchange store 'First Storage Group\Mailbox Store (PADC-SERVER)' is limited to 18 GB. The current physical size of this database (the .edb file and the .stm file) is 68 GB. If the physical size of this database minus its logical free space exceeds the limit of 18 GB, the database will be dismounted on a regular basis. Followed by the event belowEvent ID: 9865 Source: MSExchangeIS Mailbox Description:Exchange store 'First Storage Group\Mailbox Store (PADC-SERVER)': The current physical size of this database (the .edb file and the .stm file) is 68 GB. This database has exceeded the size limit of 18 GB. However, the logical free space in this database has not yet been evaluated. Therefore, it is possible that this database contains enough free space to bring its logical size below the maximum size limit. If the logical database size exceeds the maximum size limit, it will be dismounted on a regular basis. ------------- I am guessing that deleting the Database Size Limit in Gb did not help. Also, and FYI...when I look in ESM the version still shows as Standard and not Enterprise. Anyother ideas....

I would look back at that link I posted earlier and/or contact Microsoft support if you are stuck.

Ok...I called Microsoft and opened a Service Request for this issue...The only thing that they could find is that something happened during the install...the log files shows Enterprise version than shows an unknown version. Not sure if SP2 install did something to reverse the installation.13:28:23] Setup configuration information: -- ID:62227 --[13:28:23] This is a(n) Enterprise version of Microsoft Exchange Server -- ID:62232 --[13:28:23] This is not an evaluation copy of Microsoft Exchange Server; it will not expire -- ID:62234 --[13:28:23] InstallSourceDir = e:\setup\i386\exchange -- ID:62228 --[13:46:28] Setup configuration information: -- ID:62227 --[13:46:28] This is a(n) unknown version of Microsoft Exchange Server -- ID:62232 --[13:46:28] This is not an evaluation copy of Microsoft Exchange Server; it will not expire -- ID:62234 --[13:46:28] InstallSourceDir = e:\setup\i386\exchange -- ID:62228 --Anyway...I am going to reinstall the Exchange Enterprise 2003 on Friday and will post the outcome. This time I will make sure to check the version before installing the SP2 incase it caused the problem.

Hi,Thanks for your devoted time on this issue and hope to get your good news.Allen

Ok....with Microsoft Tech on the phone we deleted the entery for Standard under HKLM\Software\Microsoft\Microsoft Integration\, and also we delete the Database Size Limit in Gb from registry. I ran the reinstall fo Exchange Enterprise 2003 with Microsoft Support on the phone, once the reinstall was completed I opened ESM and still showed Standard version and not Enterprise. We checked the Event log and no Event ID 1217, it still shows Event ID 1216. I restarted the Server and looked again in ESM and continued to show Standard, also still no event ID 1217 in Event log and only 1216 shows up.We reinstalled Exchange SP2 and still nothing.The Tech from Microsoft will give me a call on Monday after researching the issue further....However, could Symantec Antivirus (V 10) that is installed on the server cause a problem with Exchange 2003 Enterprise being installed? Maybe Symantec is preventing certain files from getting updated...etc. Also, when Exchange Server was setup the Symantec Server Group/Symantec Console was also installed on the server and it is managing Antivirus software for other machines on the Network (this was done before I started working for the company). Can I just go in to Symantec File System Auto Protect and Exclude Excange Server Directories from the auto protect or exclude the entire C drive for now and try one more reinstall of Exchange 2003 Enterprise.Thanks,B

Well. the Exchangedirectories should be excluded regardless from any AV scans:http://support.microsoft.com/kb/823166Overview of Exchange Server 2003 and antivirus softwareIt wont hurt to re-run setup of course. By the way, when you run setup, do you stop all Exchange and 3rd party services before running it?

What third party services I should be stopping? I have nothing on the server other than Exchange and Symantec Antivirus 10.I don't stop the exchanger service before the install, because i noticed that during the reinstall process they are stopped first and the reinstall continues.

Anti-Virus or anti-spam or any backup agentsservice is typically something I would stop during any upgrade or application of a service pack / hotifx etc...It wouldnt hurt to manuallystop all the Exchange Services as well before running setup. I always did that with Exchange 2003. Sometimes hotfixes wouldnt apply correctly until I did that.

Just an update....I disabled Norton Antivirus and performed a reinstall, but still no luck. ESM still shows standard and still see event id 1216.I was told by Microsoft Support that the last option would be to delete binaries...etc and perform disaster recovery Exchange Enterprise CD. I guess with this process all active directory and exchange settings will remain but files related to exchange will be copied from Exchange Enterprise CD.

How about the Exchange Services? Did you stop them as well before running setup?Another option to the disasterrecovery switch is to bring up a new server and move mailboxes and public folders to it and then remove the 1st server and flatten it and reinstall Exchange clean and move mailboxes and folders back.What you are seeing is really unusual though. Are you sure its really an Enterprise install on that CD? Have you installed Exchange on another clean server - maybe in test lab just to confirm that its the Enterprise Edition?

I did stop the Exchange Services as well.As far as the CD I purchased it from Microsoft and it is labeled Enterprise. I have not installed the CD in a Test Server...maybe I should try that.However, everytime I did a resinstall I look in the Install Log and it shows Enterprise Version. Once I install SP2 the Install log shows "unknown version"....

OK...I setup a test server and did installation from the Exchange 2003 Enterprise CD. Once the install was completed I opened ESM and the version showed as "Enterprise", so the CD seemed to be ok.After I installed Exchange 2003 Ent on Test Server I went ahead and tried to reinstall again on Test Server to see if I can find anything during the reinstall process that I can compare to my real server. The one thing I found between the reinstall on the Test Server and my Actual Server is that on the Actual Server during the reinstall there was a red x next to "Microsoft Exchange Messaging and Collaboration Services".During the upgrade from MS Exchange 2003 Standard to MS Exchange 2003 Enterprise are "Microsoft Exchange Messaging and Collaboration Services" installed or they are skipped as indicated with a red x.I went back and checked the event logs for the first attempt to upgrade on my real server and found the following: Event ID: 1002Source: MSExchange SetupCategory: Microsoft Exchange SetupExchange Server component Microsoft Exchange Messaging and Collaboration Services failed. Error: 0xc107041d - 0xc007041d - The service did not respond to the start or control request in a timely fashion. (EXIFS) The above error appears every time I attempted to run the upgrade on my real server.Thanks.

Yea, I think that is the smoking gun.Can you uninstall the AV services completely, reboot and try running it again?Confirm the windows management instrumentation service is enabled and running as well.If you still have that ticket open with Microsoft, I would let them know about that error message.

During one of my reinstall the MS Engineer was looking at the same screen but he did not question it...I think he mentioned something about being normal but cannot remember. Anyway, I have a call with them today and I will mention that.

Okthe problem seemed to be with Microsoft Exchange Messaging and Collaboration Services since during the reinstall it was showing a red x. Also, from Event ID 1002 as shown below the EXIFS was the main problem. I mentioned this issue again to the last MS Engineer I spoke with and it happens that today he also had a customer with similar problem on SBS 2003 but he said it is most likely the same issue I am having. So he asked to go to C:\Windows\System32\Drivers and rename the following files exifs.sys and exifssmsg.dll. After renaming both files I ran the Reinstall of MS Exchange 2003 Enterprise and everything was ok.the ESM now shows Enterprise and I see Event ID 1217. During my past 3 reinstalls the event log showed error below but I did not notice and MS Support I spoke with first did not notice as well.the strange thing is that during reinstall no error message or anything appeared to indicate it just showed a red x not Messaging and Collaboration Services. Event ID: 1002Source: MSExchange SetupCategory: Microsoft Exchange SetupExchange Server component Microsoft Exchange Messaging and Collaboration Services failed. Error: 0xc107041d - 0xc007041d - The service did not respond to the start or control request in a timely fashion. (EXIFS)Hope this will help others who will run into similar problems.

Excellent! Congratulations.

Ok…the problem seemed to be with Microsoft Exchange Messaging and Collaboration Services since during the reinstall it was showing a red x. Also, from Event ID 1002 as shown below the EXIFS was the main problem. I mentioned this issue again to the last MS Engineer I spoke with and it happens that today he also had a customer with similar problem on SBS 2003 but he said it is most likely the same issue I am having. So he asked to go to C:\Windows\System32\Drivers and rename the following files exifs.sys and exifssmsg.dll. After renaming both files I ran the Reinstall of MS Exchange 2003 Enterprise and everything was ok….the ESM now shows Enterprise and I see Event ID 1217. During my past 3 reinstalls the event log showed error below but I did not notice and MS Support I spoke with first did not notice as well….the strange thing is that during reinstall no error message or anything appeared to indicate it just showed a red x not Messaging and Collaboration Services. Event ID: 1002Source: MSExchange SetupCategory: Microsoft Exchange SetupExchange Server component Microsoft Exchange Messaging and Collaboration Services failed. Error: 0xc107041d - 0xc007041d - The service did not respond to the start or control request in a timely fashion. (EXIFS)Hope this will help others who will run into similar problems. Hi Bluem1,Thanks for posting the fix. This whole thread just saved our bacon tonight.The only extra thing that needs to be posted here with the fix is that when prompted during the re-install to overwrite existing newer files with the older ones, answer YES.Cheers,Mike.

Bluem1, Having the exact same issue you describe. And we even did what you did, created a test machine and did the install over to see if it was indeed the 2003 Enterprise Media. I am going to try renaming the files mentioned above this evening and seeing if it fixes our issue. I am pretty sure it is since the circumstances are identical. D. Noll

Bluem1 and all, I couldn't rename the files to make the upgrade to work although I was having the identical problem with EXIFS. So I turned off starting EXIFS with regedit, and turned to manual all the exchange services and rebooted. Installed 2003 Enterprise Exchange and service pack 2 with nothing Exchange running. Doing that updated the EXIFS services startup back to booting, so I turned all the appropriate Exchange services back to automatic, rebooted server and from the Exchange Manager it showed that I did indeed have Enterprise running. But... the registry entries for the database sized did not get changed. So I went in to regedit again, changed the values from 76 to 8000 and restarted the store. Then restarted the message store service and there is was, EVENT 1217. So I had a couple extras steps but it worked. Thanks for helping point out the issue, it helped immensely.

Bluem1,So glad you got this issue sorted, issues like these really tighten my shorts. Two questions:1) Did you do this upgrade on a live Exchange database?2) I have purchased Exch2010 and need to downgrade to Exchange 2003 Enterprise (we have std now). Microsoft is not issuing the Exchange 2003 Enterprise 2003 SP2 CD's any longer... any chance I could ask you to burn or upload your copies? I'm desperate. Cheers,Astarr