MMC 3.0 POP3 Snap-in Error - Please Help!
|
From: Gerard on 15 Jan 2008 06:47 Dear Shawn, Thank you for your prompt reply. Your time in helping me is greatly appreciated. I'll run down your questions below in this thread for others to see. I'll send a copy through the mail accompanied by some screenshots for your clarification. 1). We are running Windows 2003 SBS with Exchange with SP2 installed. 2). The issue began to occur when we installed the SP2, back in September 2007. The same error was given then, but as the previous settings for the POP3 connector still worked, there was no need to solve this matter sooner. We are now adding new colleagues to the POP3 connector, and this cannot be done due to this error. No hardware changes were made prior to or shortly after the install of the SP2. 3). The POP3 connectors gives an error in the generic error display style, when run from the MMC 3.0, where no option 3 is available (ATTACHED in e-mail: screenshot) When run from the Exchange System Manager we receive the error messagebox you refer to. Choosing option 3 has no visible effect, i.e. the error remains (ATTACHED in e-mail: screenshot) Furter to your request, I've attached the kb921096.log and the report from MPSRPT_SETUPPerf.exe (both zipped) to my e-mail to you. I hope you have enough information to set me on the right track on solving this issue. Best regards, Gerard. ""Shawn Shao [MSFT]"" wrote: > > Hi Gerard, > > Thank you for posting here. > > From your post, I understand that you also encountered the POP3 Connector > error described in KB921096. However, the update cannot be installed due to > some other error message. > > Before we go any further, I would appreciate your help in clarifying the > following questions: > > 1. What's the system version and Service Pack level? > 2. When did this issue begin to occur? Have any hardware or software > changes been made recently? > 3. Is the error message the following? Does this issue persist if we select > the third option? > > "MMC has detected an error in a snap-in, it is recommended that you shut > down and restart MMC > > O Report this error to Microsoft, and then shut down MMC > O Continue running and ignore errors with this snap-in for the rest of the > session > O Continue running and always ignore errors with this snap-in, regardless > of user or session" > > To check the installation process of KB921096, please help me collect the > following log files for further research: > > 1. KB921096.log > --------------- > 1. Click Start->Run, type "%windir%" without quotation marks and press > Enter. > 2. Locate a file named KB921096.log > > 2. MPS report > --------------- > a. Please download the MPSRPT_SETUPPerf.EXE from the following link and > then run this tool to gather some information from the problematic computer: > http://download.microsoft.com/download/b/b/1/bb139fcb-4aac-4fe5-a579-30b0bd9 > 15706/MPSRPT_SETUPPerf.EXE > > b. Double-click on the MPSRPT_SETUPPerf.EXE file. [Note] This process may > take some time; however, it will not have a negative effect on the > performance. > c. A CAB file will be generated in the > %systemroot%\MPSReports\Setup\Reports\Cab directory > called%COMPUTERNAME%_MPSReports.CAB. The CAB file will contain the reports > generated by the MPS Reporting Tool. > > You can zip these log files and send them as attachments to my mailbox > v-shshao(a)microsoft.com > > I am looking forward to your feedback. > > Best regards, > > Shawn Shao > Microsoft CSS Online Newsgroup Support > > Get Secure! - www.microsoft.com/security > > ===================================================== > This newsgroup only focuses on SBS technical issues. If you have issues > regarding other Microsoft products, you'd better post in the corresponding > newsgroups so that they can be resolved in an efficient and timely manner. > You can locate the newsgroup here: > http://www.microsoft.com/communities/newsgroups/en-us/default.aspx > > When opening a new thread via the web interface, we recommend you check the > "Notify me of replies" box to receive e-mail notifications when there are > any updates in your thread. When responding to posts via your newsreader, > please "Reply to Group" so that others may learn and benefit from your > issue. > > Microsoft engineers can only focus on one issue per thread. Although we > provide other information for your reference, we recommend you post > different incidents in different threads to keep the thread clean. In doing > so, it will ensure your issues are resolved in a timely manner. > > For urgent issues, you may want to contact Microsoft CSS directly. Please > check http://support.microsoft.com for regional support phone numbers. > > Any input or comments in this thread are highly appreciated. > ===================================================== > This posting is provided "AS IS" with no warranties, and confers no rights. > >
From: "Shawn Shao [MSFT]" on 16 Jan 2008 05:12 Hi Gerard, Thank you for your update. Based on the screenshots, it seems this issue is a little different from the original one. I have checked the KB921096.log and found the following message. 0.078: ServicePackNumber is Not Present 0.078: Fist Condition in ChkSBSSP.Section Failed As I know, ServicePackNumber under the following registry branch is used to identify the Service Pack level of SBS server. A value of "1" indicates that the server is at SP1. The value is not present if the service pack has not been applied. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SmallBusinessServer\"ServicePackNumber " Thus, this message can occur if SBS 2003 Service Pack 1 hasn't been installed. In our case, this Service Pack may be requested to install this update. As you may know, besides Windows Server 2003 SP1, there is also Windows Small Business Server 2003 Service Pack 1 (SBS SP1). They are different from each other. To install SBS SP1, you need to install the following service packs first: ----------------------- 1. Windows Server 2003 Service Pack 1 2. Windows SharePoint Services 2.0 Service Pack 1 3. Exchange Server 2003 Service Pack 1 4. Windows XP SP2 for Client Deployment Note: Windows Server 2003 SP2 includes Windows Server 2003 SP1. Here is an article described how to install SBS SP1: Downloading and Installing Windows Small Business Server 2003 Service Pack 1 http://download.microsoft.com/download/e/0/f/e0fee8ce-768d-41c0-8871-9bc48e0 b3fc3/ToDownLoadFilesandReadInstructions.htm Generally, we can install SBS SP1 before installing Windows Server 2003 SP2. However, we can also install SBS SP1 after the installation of Windows Server 2003 SP2. During the installation, just skip the Windows Server 2003 SP1 part. After installing SBS SP1, let's try to install this update again. If anything is unclear or there are any questions about the steps, please do not hesitate to let me know. I will be glad to help. Best regards, Shawn Shao Microsoft CSS Online Newsgroup Support Get Secure! - www.microsoft.com/security ===================================================== This newsgroup only focuses on SBS technical issues. If you have issues regarding other Microsoft products, you'd better post in the corresponding newsgroups so that they can be resolved in an efficient and timely manner. You can locate the newsgroup here: http://www.microsoft.com/communities/newsgroups/en-us/default.aspx When opening a new thread via the web interface, we recommend you check the "Notify me of replies" box to receive e-mail notifications when there are any updates in your thread. When responding to posts via your newsreader, please "Reply to Group" so that others may learn and benefit from your issue. Microsoft engineers can only focus on one issue per thread. Although we provide other information for your reference, we recommend you post different incidents in different threads to keep the thread clean. In doing so, it will ensure your issues are resolved in a timely manner. For urgent issues, you may want to contact Microsoft CSS directly. Please check http://support.microsoft.com for regional support phone numbers. Any input or comments in this thread are highly appreciated. ===================================================== This posting is provided "AS IS" with no warranties, and confers no rights.
From: Gerard on 23 Jan 2008 13:40 Hello Shawn, Thanks for the elaborate reply. It gave me a number of handles to try and solve this situation. Due to the server being in use during the daytime, I had to pick a quiet moment at night to follow your suggested steps. I made a thinking error, mistaking the various SP numbers in my original post. As system information shows 'Service Pack 2', I was under the assumption that everything was updated to this level. In the meantime, I've installed all service packs as described in your message and although everything seemed to go smoothly, when setup came to the networking part, it threw an error. It skipped this part and resumed install. Which means that everything is fully operational, EXCEPT the POP3 connector, which was the main reason to do all these steps. Not only is it not functioning, it is NOT present anymore. The icon has disappeared from the System Manager and Exchange Manager. All global routing rules that were present are also gone and are no longer applied when new mail arrives. Which means that all mail is collected by me, and I have to forward manually to my colleagues. Less than ideal, no need to add. A suggestion to retrieve the POP3 connector is greatly appreciated. Can I just get this from the original setup CD of SBS2003 ? Should you need any other information, please don't hesitate to ask, I'm very anxious to resolve this matter. Thanks and best regards, Gerard. ""Shawn Shao [MSFT]"" wrote: > > Hi Gerard, > > Thank you for your update. Based on the screenshots, it seems this issue is > a little different from the original one. > > I have checked the KB921096.log and found the following message. > > 0.078: ServicePackNumber is Not Present > 0.078: Fist Condition in ChkSBSSP.Section Failed > > As I know, ServicePackNumber under the following registry branch is used to > identify the Service Pack level of SBS server. A value of "1" indicates > that the server is at SP1. The value is not present if the service pack has > not been applied. > > HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SmallBusinessServer\"ServicePackNumber > " > > Thus, this message can occur if SBS 2003 Service Pack 1 hasn't been > installed. In our case, this Service Pack may be requested to install this > update. > > > As you may know, besides Windows Server 2003 SP1, there is also Windows > Small Business Server 2003 Service Pack 1 (SBS SP1). They are different > from each other. > > To install SBS SP1, you need to install the following service packs first: > ----------------------- > 1. Windows Server 2003 Service Pack 1 > 2. Windows SharePoint Services 2.0 Service Pack 1 > 3. Exchange Server 2003 Service Pack 1 > 4. Windows XP SP2 for Client Deployment > > Note: Windows Server 2003 SP2 includes Windows Server 2003 SP1. > > Here is an article described how to install SBS SP1: > > Downloading and Installing Windows Small Business Server 2003 Service Pack 1 > http://download.microsoft.com/download/e/0/f/e0fee8ce-768d-41c0-8871-9bc48e0 > b3fc3/ToDownLoadFilesandReadInstructions.htm > > Generally, we can install SBS SP1 before installing Windows Server 2003 > SP2. However, we can also install SBS SP1 after the installation of Windows > Server 2003 SP2. During the installation, just skip the Windows Server 2003 > SP1 part. > > After installing SBS SP1, let's try to install this update again. > > If anything is unclear or there are any questions about the steps, please > do not hesitate to let me know. I will be glad to help. > > Best regards, > > Shawn Shao > Microsoft CSS Online Newsgroup Support > > Get Secure! - www.microsoft.com/security > > ===================================================== > This newsgroup only focuses on SBS technical issues. If you have issues > regarding other Microsoft products, you'd better post in the corresponding > newsgroups so that they can be resolved in an efficient and timely manner. > You can locate the newsgroup here: > http://www.microsoft.com/communities/newsgroups/en-us/default.aspx > > When opening a new thread via the web interface, we recommend you check the > "Notify me of replies" box to receive e-mail notifications when there are > any updates in your thread. When responding to posts via your newsreader, > please "Reply to Group" so that others may learn and benefit from your > issue. > > Microsoft engineers can only focus on one issue per thread. Although we > provide other information for your reference, we recommend you post > different incidents in different threads to keep the thread clean. In doing > so, it will ensure your issues are resolved in a timely manner. > > For urgent issues, you may want to contact Microsoft CSS directly. Please > check http://support.microsoft.com for regional support phone numbers. > > Any input or comments in this thread are highly appreciated. > ===================================================== > This posting is provided "AS IS" with no warranties, and confers no rights. > >
From: Merv Porter [SBS-MVP] on 23 Jan 2008 14:34 You might try reinstalling the POP3 Connector... How to reinstall POP3 connector in SBS 2003 http://groups.google.com/group/microsoft.public.windows.server.sbs/browse_thread/thread/172607b7fd245069/eab90fdd2cf82b52?hl=en&lnk=st&q=sbs+reinstall+pop3+connector#eab90fdd2cf82b52 -- Merv Porter [SBS-MVP] ============================ "Gerard" <Gerard(a)discussions.microsoft.com> wrote in message news:52DAE739-8CA6-400D-B29F-56AF9B144EE8(a)microsoft.com... > Hello Shawn, > > Thanks for the elaborate reply. It gave me a number of handles to try and > solve this situation. Due to the server being in use during the daytime, I > had to pick a quiet moment at night to follow your suggested steps. > > I made a thinking error, mistaking the various SP numbers in my original > post. As system information shows 'Service Pack 2', I was under the > assumption that everything was updated to this level. > > In the meantime, I've installed all service packs as described in your > message and although everything seemed to go smoothly, when setup came to > the > networking part, it threw an error. It skipped this part and resumed > install. > > Which means that everything is fully operational, EXCEPT the POP3 > connector, > which was the main reason to do all these steps. > > Not only is it not functioning, it is NOT present anymore. The icon has > disappeared from the System Manager and Exchange Manager. All global > routing > rules that were present are also gone and are no longer applied when new > arrives. > > Which means that all mail is collected by me, and I have to forward > manually > to my colleagues. > > Less than ideal, no need to add. > > A suggestion to retrieve the POP3 connector is greatly appreciated. Can I > just get this from the original setup CD of SBS2003 ? > > Should you need any other information, please don't hesitate to ask, I'm > very anxious to resolve this matter. > > Thanks and best regards, > > Gerard. > > > > ""Shawn Shao [MSFT]"" wrote: > >> >> Hi Gerard, >> >> Thank you for your update. Based on the screenshots, it seems this issue >> is >> a little different from the original one. >> >> I have checked the KB921096.log and found the following message. >> >> 0.078: ServicePackNumber is Not Present >> 0.078: Fist Condition in ChkSBSSP.Section Failed >> >> As I know, ServicePackNumber under the following registry branch is used >> to >> identify the Service Pack level of SBS server. A value of "1" indicates >> that the server is at SP1. The value is not present if the service pack >> has >> not been applied. >> >> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SmallBusinessServer\"ServicePackNumber >> " >> >> Thus, this message can occur if SBS 2003 Service Pack 1 hasn't been >> installed. In our case, this Service Pack may be requested to install >> this >> update. >> >> >> As you may know, besides Windows Server 2003 SP1, there is also Windows >> Small Business Server 2003 Service Pack 1 (SBS SP1). They are different >> from each other. >> >> To install SBS SP1, you need to install the following service packs >> first: >> ----------------------- >> 1. Windows Server 2003 Service Pack 1 >> 2. Windows SharePoint Services 2.0 Service Pack 1 >> 3. Exchange Server 2003 Service Pack 1 >> 4. Windows XP SP2 for Client Deployment >> >> Note: Windows Server 2003 SP2 includes Windows Server 2003 SP1. >> >> Here is an article described how to install SBS SP1: >> >> Downloading and Installing Windows Small Business Server 2003 Service >> Pack 1 >> http://download.microsoft.com/download/e/0/f/e0fee8ce-768d-41c0-8871-9bc48e0 >> b3fc3/ToDownLoadFilesandReadInstructions.htm >> >> Generally, we can install SBS SP1 before installing Windows Server 2003 >> SP2. However, we can also install SBS SP1 after the installation of >> Windows >> Server 2003 SP2. During the installation, just skip the Windows Server >> 2003 >> SP1 part. >> >> After installing SBS SP1, let's try to install this update again. >> >> If anything is unclear or there are any questions about the steps, please >> do not hesitate to let me know. I will be glad to help. >> >> Best regards, >> >> Shawn Shao >> Microsoft CSS Online Newsgroup Support >> >> Get Secure! - www.microsoft.com/security >> >> ===================================================== >> This newsgroup only focuses on SBS technical issues. If you have issues >> regarding other Microsoft products, you'd better post in the >> corresponding >> newsgroups so that they can be resolved in an efficient and timely >> manner. >> You can locate the newsgroup here: >> http://www.microsoft.com/communities/newsgroups/en-us/default.aspx >> >> When opening a new thread via the web interface, we recommend you check >> the >> "Notify me of replies" box to receive e-mail notifications when there are >> any updates in your thread. When responding to posts via your newsreader, >> please "Reply to Group" so that others may learn and benefit from your >> issue. >> >> Microsoft engineers can only focus on one issue per thread. Although we >> provide other information for your reference, we recommend you post >> different incidents in different threads to keep the thread clean. In >> doing >> so, it will ensure your issues are resolved in a timely manner. >> >> For urgent issues, you may want to contact Microsoft CSS directly. Please >> check http://support.microsoft.com for regional support phone numbers. >> >> Any input or comments in this thread are highly appreciated. >> ===================================================== >> This posting is provided "AS IS" with no warranties, and confers no >> rights. >> >>
From: "Shawn Shao [MSFT]" on 24 Jan 2008 05:48 Hi, Thanks a lot for Merv's reinstall suggestion. It worth a try! If the issue remains after reinstalling POP3 connector, let's try to install KB921096 again. If there is any problem during the installation of POP3 connector or this update, feel free to post back and I will be glad to help. You can also send the latest KB921096.log & MPS report to me for further analyze. I look forward to hearing from you. Best regards, Shawn Shao Microsoft CSS Online Newsgroup Support Get Secure! - www.microsoft.com/security ===================================================== This newsgroup only focuses on SBS technical issues. If you have issues regarding other Microsoft products, you'd better post in the corresponding newsgroups so that they can be resolved in an efficient and timely manner. You can locate the newsgroup here: http://www.microsoft.com/communities/newsgroups/en-us/default.aspx When opening a new thread via the web interface, we recommend you check the "Notify me of replies" box to receive e- mail notifications when there are any updates in your thread. When responding to posts via your newsreader, please "Reply to Group" so that others may learn and benefit from your issue. Microsoft engineers can only focus on one issue per thread. Although we provide other information for your reference, we recommend you post different incidents in different threads to keep the thread clean. In doing so, it will ensure your issues are resolved in a timely manner. For urgent issues, you may want to contact Microsoft CSS directly. Please check http://support.microsoft.com for regional support phone numbers. Any input or comments in this thread are highly appreciated. ===================================================== This posting is provided "AS IS" with no warranties, and confers no rights.
First
|
Prev
|
Pages: 1 2 Prev: Reinstall WSUS - Missing Instance SERVER\MICROSOFT##SSEE Next: No profile data |