SBS 2003 R2 - Long Log In Times - Exchange Failure
|
From: e.bellamy on 9 Jan 2007 05:59 Hello there! We have server where login times have increased dramatically in the past week to approximately 5 minutes before defaulting to the workstation profile. All workstations are running XP Pro SP2. The Server is SBS 2003 R2. Once logged in, all shared network drives from SBS work fine. Exchange runs for a period of time and then cutrs out. A Workstation retart is then required to reconnect. Queue waiting for 15 mons login again! The error log displays the following: Source Event ID Last Occurrence Total Occurrences WinMgmt 10 09/01/2007 05:35 273 * Event filter with query "SELECT * FROM __InstanceDeletionEvent WITHIN 600 WHERE TargetInstance isa "Win32_PnPEntity"" could not be (re)activated in namespace "//./root/CIMV2" because of error 0x8004106c. Events may not be delivered through this filter until the problem is corrected. Source Event ID Last Occurrence Total Occurrences Application Error 1000 09/01/2007 03:46 10 * Faulting application wmiprvse.exe, version 5.2.3790.1830, faulting module provDisk.dll, version 8.50.0.141, fault address 0x000089d8. Source Event ID Last Occurrence Total Occurrences MSExchangeSA 9099 08/01/2007 19:28 4 * The MAD Monitoring thread was unable to read the state of the services, error '0x800706be'. For more information, click http://www.microsoft.com/contentredirect.asp. Source Event ID Last Occurrence Total Occurrences POP3 Connector 1053 08/01/2007 17:45 3 * The delivery process for message <id: {E1C5E144-BB46-42EE-AF5E-888F2702ED6A}> finished with one or more errors. There are a few posts regarding this already, but most point toward completing an SP1 update. Being on R2, I'm assuming that this isn't the case! Any ideas or experience in this matter? Many thanks
From: Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP] on 10 Jan 2007 02:28 First off post up ipconfig /all from the server and the workstation.. the long log ins are usually DNS related. e.bellamy(a)fast247.biz wrote: > Hello there! > > We have server where login times have increased dramatically in the > past week to approximately 5 minutes before defaulting to the > workstation profile. All workstations are running XP Pro SP2. The > Server is SBS 2003 R2. Once logged in, all shared network drives from > SBS work fine. Exchange runs for a period of time and then cutrs out. A > Workstation retart is then required to reconnect. Queue waiting for 15 > mons login again! > > The error log displays the following: > > Source Event ID Last Occurrence Total Occurrences > WinMgmt 10 09/01/2007 05:35 273 * > Event filter with query "SELECT * FROM __InstanceDeletionEvent WITHIN > 600 WHERE TargetInstance isa "Win32_PnPEntity"" could not be > (re)activated in namespace "//./root/CIMV2" because of error > 0x8004106c. Events may not be delivered through this filter until the > problem is corrected. > > Source Event ID Last Occurrence Total Occurrences > Application Error 1000 09/01/2007 03:46 10 * > Faulting application wmiprvse.exe, version 5.2.3790.1830, faulting > module provDisk.dll, version 8.50.0.141, fault address 0x000089d8. > > Source Event ID Last Occurrence Total Occurrences > MSExchangeSA 9099 08/01/2007 19:28 4 * > The MAD Monitoring thread was unable to read the state of the services, > error '0x800706be'. For more information, click > http://www.microsoft.com/contentredirect.asp. > > Source Event ID Last Occurrence Total Occurrences > POP3 Connector 1053 08/01/2007 17:45 3 * > The delivery process for message <id: > {E1C5E144-BB46-42EE-AF5E-888F2702ED6A}> finished with one or more > errors. > > There are a few posts regarding this already, but most point toward > completing an SP1 update. Being on R2, I'm assuming that this isn't the > case! Any ideas or experience in this matter? > > Many thanks >
From: Terence Liu [MSFT] on 10 Jan 2007 02:48 Hello Bellamy, Thanks for posting here. From your problem description, I understand this issue to be: the client takes long time to log on to the SBS server domain and your Exchange failure. If I am off base, please do not hesitate to let me know. Please understand that our newsgroup is an issue based service, meaning we usually respond to one question/issue per post. This will lessen the confusion for both of us, as well as ensure that our results are accurate and not a result of a test for a different question. Therefore, I will work with you on the first question in this post (the client log on issue). Regarding the additional question (Exchange failure), I will follow it when we resolve the first issue. Log on slow is probably refer to incorrect DNS settings on the clients. The SBS server internal IP address should be used as the DNS server on the clients rather than the ISP DNS servers. The SBS server can then forward DNS requests to the ISP DNS servers for Internet access. So I suggest you to re-run the CEICW wizard to configure internet access. For more information, please refer to the following information. 825763 How to configure Internet access in Windows Small Business Server 2003 http://support.microsoft.com/?id=825763 The DHCP service will be configured automatically after you run CEICW. The default scope option of DHCP service is as followings after running CEICW. 003 Router SBS internal NIC IP (if you have 2 NIC installed on SBS server) 006 DNS Servers SBS internal NIC IP 015 DNS Domain Name Your Domain Name 044 WINS/NBNS Servers SBS internal NIC IP 046 WINS/NBT Node Type 0x8 You could check the following settings to confirm network configuration. On SBS server: External NIC: IP: assigned by your ISP or your hardware router Gateway: your ISP or your Hardware router IP DNS: SBS INTERNAL NIC IP as the only entry Internal NIC: IP: Fixed IP Gateway: None DNS: SBS INTERNAL NIC IP as the only entry In the DNS console (dnsmgmt.msc), right click your ServerName and click properties. In the Forwarders tab, your ISP DNS server IP should be inputted there. On workstation: IP: Assigned by DHCP on SBS Gateway: SBS internal NIC IP DNS: SBS INTERNAL NIC IP as the only entry Then try to log on clients again, is it fine? Note: By the way, try to test your Exchange issue. If the issue persists, please kindly help me collect some information for further investigation: 1. Do all clients have the slow log on issue? 2. Please send me the MPS report both on your SBS server and one of the problematic workstation. a. Visit http://download.microsoft.com/download/b/b/1/bb139fcb-4aac-4fe5-a579-30b0bd9 15706/MPSRPT_NETWORK.EXE. to download the file. b. Run the MPSRPT_NETWORK.EXE on the server and one of the client workstation box. c. Wait for 10~15 minutes. d. Open Windows explorer, navigate to %SYSTEMROOT%\MPSReports\Network\Reports\cab\ e. Send the .cab file directly to me at v-terliu(a)microsoft.com 3. Gather userenv.Log a. On one of the problematic machines, use Registry Editor to add the following registry value (or modify it, if the value already exists): [HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Winlogon] Value: UserEnvDebugLevel Value Type: REG_DWORD Value Data: 10002 (Hexadecimal) b. Restart the machine, log on with the problematic user account, and make sure the issue is reproduced. It is better to delete the userenv.log file if it exists before restarting the computer. c. The log file is written to the %Systemroot%\Debug\UserMode\Userenv.log file. Please send the file to me at v-terliu(a)microsoft.com. Note: To disable logging, change the registry value to 0. For more information please refer to the following KB article. How to Enable User Environment Event Logging http://support.microsoft.com/?id=221833 If you have any questions or concerns related to this issue, please let me know. I appreciate your time and look forward to hearing from you. Hope these steps will give you some help. Thanks and have a nice day! Best regards, Terence Liu(MSFT) 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: e.bellamy(a)fast247.biz | Newsgroups: microsoft.public.windows.server.sbs | Subject: SBS 2003 R2 - Long Log In Times - Exchange Failure | Date: 9 Jan 2007 02:59:59 -0800 | Organization: http://groups.google.com | Lines: 43 | Message-ID: <1168340399.001407.153810(a)11g2000cwr.googlegroups.com> | NNTP-Posting-Host: 87.127.21.4 | Mime-Version: 1.0 | Content-Type: text/plain; charset="iso-8859-1" | X-Trace: posting.google.com 1168340415 16380 127.0.0.1 (9 Jan 2007 11:00:15 GMT) | X-Complaints-To: groups-abuse(a)google.com | NNTP-Posting-Date: Tue, 9 Jan 2007 11:00:15 +0000 (UTC) | User-Agent: G2/1.0 | X-HTTP-UserAgent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.0.8) Gecko/20061025 Firefox/1.5.0.8,gzip(gfe),gzip(gfe) | Complaints-To: groups-abuse(a)google.com | Injection-Info: 11g2000cwr.googlegroups.com; posting-host=87.127.21.4; | posting-account=Cx8cCg0AAAAW3czvf9wKV_bEM2oxmBh0 | Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTFEEDS01.phx.gbl!news-out. cwix.com!newsfeed.cwix.com!newscon02.news.prodigy.net!prodigy.net!news.glorb .com!postnews.google.com!11g2000cwr.googlegroups.com!not-for-mail | Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:9074 | X-Tomcat-NG: microsoft.public.windows.server.sbs | | Hello there! | | We have server where login times have increased dramatically in the | past week to approximately 5 minutes before defaulting to the | workstation profile. All workstations are running XP Pro SP2. The | Server is SBS 2003 R2. Once logged in, all shared network drives from | SBS work fine. Exchange runs for a period of time and then cutrs out. A | Workstation retart is then required to reconnect. Queue waiting for 15 | mons login again! | | The error log displays the following: | | Source Event ID Last Occurrence Total Occurrences | WinMgmt 10 09/01/2007 05:35 273 * | Event filter with query "SELECT * FROM __InstanceDeletionEvent WITHIN | 600 WHERE TargetInstance isa "Win32_PnPEntity"" could not be | (re)activated in namespace "//./root/CIMV2" because of error | 0x8004106c. Events may not be delivered through this filter until the | problem is corrected. | | Source Event ID Last Occurrence Total Occurrences | Application Error 1000 09/01/2007 03:46 10 * | Faulting application wmiprvse.exe, version 5.2.3790.1830, faulting | module provDisk.dll, version 8.50.0.141, fault address 0x000089d8. | | Source Event ID Last Occurrence Total Occurrences | MSExchangeSA 9099 08/01/2007 19:28 4 * | The MAD Monitoring thread was unable to read the state of the services, | error '0x800706be'. For more information, click | http://www.microsoft.com/contentredirect.asp. | | Source Event ID Last Occurrence Total Occurrences | POP3 Connector 1053 08/01/2007 17:45 3 * | The delivery process for message <id: | {E1C5E144-BB46-42EE-AF5E-888F2702ED6A}> finished with one or more | errors. | | There are a few posts regarding this already, but most point toward | completing an SP1 update. Being on R2, I'm assuming that this isn't the | case! Any ideas or experience in this matter? | | Many thanks | |
|
Pages: 1 Prev: Backup fails suspect VSS problem Next: Issues with remote desktop |