Re: MDAC and SBS2003 SP1
- From: "Berry Janssen" <soeb555@xxxxxxxxxxx>
- Date: Tue, 2 Aug 2005 23:53:15 +0200
Hi Jenny,
Thank you very much for your excellent answer. I thoroughly checked all
three suggestions and here are my remarks:
I: In the system log I get event ID 10016, Source DCOM, "The
application-specific permission settings do not grant Local Launch
permissions for the COM server application with CLSID {xxxxx} to the user NT
AUTHORITY\System SID {xxxx}".
When I look up the CLSID in the registry hive HK_CR I find that it is the
STORE.EXE component that generates this error. When I start the Component
Services tool I cannot find the store.exe component under DCOM CONFIG.
II: The MSDART.DLL versions on my server are all the same although the
version number is 2.82.1830 and not as you stated.
III: The comchecker says version 2.82 SP2.
I hope you can help me with the DCOM problem.
Thanks again for your answer!
Berry Janssen
""Jenny wu [MSFT]"" <v-yanniw@xxxxxxxxxxxxxxxxxxxx> schreef in bericht
news:J%23TshOplFHA.3120@xxxxxxxxxxxxxxxxxxxxxxxx
> Hi Berry,
>
> Thanks for posting here.
>
> I am sorry for the delayed response due to weekend. Please understand that
> the newsgroups are staffed weekdays by Microsoft Support professionals to
> answer your systems and applications questions. Your understanding is
> greatly appreciated!
>
> For your description, I understand that the issue is:
> 1. When you install a new application that needs MSDART.DLL, you get an
> error: "The procedure entry point DefWindowProcI could not be located in
> the dynamic link library MSDART.DLL"
>
> 2. The different file version of MDAC.
>
> 3. The Veritas Backup Exec service doesn't start.
>
> If I am off base, please don't hesitate to let me know.
>
> Please follow my suggestion to try to resolve the issue:
> ==================
> I. This issue occurs because the default Component Object Model (COM)
> permissions are changed in Windows Server 2003 SP1. The new COM
> permissions
> restrict remote calls that are not authenticated. The COM program may work
> locally, but the remote calls that are not authenticated fail. By default,
> only members of the Administrators group have the Remote Activation
> permission and the Launch permissions. This change prevents user accounts
> that do not belong to the Administrators group from starting COM
> components.
> RESOLUTION:
>
> Before you follow the steps in this section that describe how to resolve
> this issue, you must first confirm that you are experiencing this
> permissions issue.
>
> A: Confirm that you are experiencing this permissions issue
>
> You can confirm that you are experiencing this permissions issue by
> turning
> on DCOM error logging. You can enable error logging by changing the
> registry and then restarting the DCOM process that you want to examine.
> The
> DCOM process that you want to examine determines whether you have to
> restart the computer. To turn on DCOM error logging, follow these steps:
>
> 1. Click Start, click Run, type regedit, and then click OK.
>
> 2. Locate the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Ole registry subkey.
>
> 3. Right-click the Ole value, point to New, and then click DWORD Value.
>
> 4. Type ActivationFailureLoggingLevel, and then press ENTER. Double-click
> ActivationFailureLoggingLevel, type 1 in the Value data box, and then
> click
> OK.
>
> 5. Right-click the Ole value, point to New, and then click DWORD Value.
>
> 6. Type CallFailureLoggingLevel, and then press ENTER. Double-click
> CallFailureLoggingLevel, type 1 in the Value data box, and then click OK.
>
> 7. Restart the DCOM program, and then examine the System log and the
> Application log for DCOM errors.
>
> The error messages in the event log contain information that you can use
> to
> help resolve the permissions issue.
>
> You can turn off DCOM error logging by changing the
> ActivationFailureLoggingLevel value and the CallFailureLoggingLevel value
> to zero.
>
> B. Resolve the permissions issue
> If you confirm that you are experiencing this permissions issue, resolve
> the permissions issue by following these steps:
>
> 1. Click Start, point to Administrative Tools, and then click Component
> Services.
>
> 2. Expand the Component Services\Computers container.
>
> 3. Right-click My Computer, and then click Properties.
>
> 4. On the COM Security tab, click Edit Limits in the Access Permissions
> area or in the Launch and Activation Permissions area. The area depends on
> where the issue occurs.
>
> 5. Click the account that is specified in the event log error, and then
> click Allow for the Remote Access permissions.
>
> 6. Click OK two times to accept the changes. Then, try to use the program
> that uses DCOM.
>
> This behavior is by design. Thank you for you understanding.
>
> For more detail info please refer to the KB article:
> Programs that use DCOM do not work correctly after you install Microsoft
> Windows Server 2003 Service Pack 1
> http://support.microsoft.com/default.aspx?scid=kb;en-us;892500
>
> Try to test, how about the result?
> ==================
>
> II. If not the situation, please try to find the version of all copies of
> the Msdart.dll file in your SBS server.
>
> This issue occurs when you have an incorrect version of the Msdart.dll
> file
> in your %windir%\System32 folder and you have the correct version in your
> %windir%\System32\Dllcache folder.
>
> WORKAROUND
>
> To work around this problem, you must replace the Msdart.dll (v2.71.9030)
> file in your %windir%\System32 with the correct Msdart.dll (v2.71.9031.4)
> file that is located in your %windir%\System32\Dllcache folder. To do
> this,
> follow these steps:
>
> 1. Click Start, click Run, type cmd, and then click OK.
> 2. Type the following command at the command prompt, and then press
> ENTER:copy %windir%\system32\dllcache\msdart.dll %windir%\system32
> *Note: Type y (yes) when you are prompted to overwrite the file.
>
> 3. Type exit, and then press ENTER to close the command prompt.
>
> *Note: The incorrect version of the Msdart.dll file may be loaded from a
> location that is different from %windir%\System32. You must search the
> computer for all copies of the Msdart.dll file and make sure that all
> copies are correct. The Msdart.dll file should only be located in the
> following folders:
>
> o %windir%\System32
> o %windir%\System32\Dllcache
> o %windir%\ServicePackFiles
>
> For more detail info please refer to the KB article:
> You receive a "The procedure entry point GetIUMS could not be located in
> dynamic link library msdart.dll" error message
> http://support.microsoft.com/default.aspx?scid=kb;en-us;889114
>
> How about the result?
> ==================
>
> III. If it is not your situation, you can try to find the version of MDAC
> of all copies of MDAC. The problem is either a corrupted or incomplete or
> bad version of MDAC.
>
> Please try to use the Component Checker tool to check which version of
> Microsoft Data Access Components (MDAC) is installed on a system. Follow
> the below steps to do:
>
> The most reliable way to determine which version of MDAC is installed is
> to
> compare the version number of each MDAC DLL file to a list of the DLL
> files
> that are shipped with each MDAC version. The Component Checker can help
> you
> to do this. It checks the files on the computer, compares them to a list
> from each version of MDAC, and reports the closest match.
>
> A. To install Component Checker, follow these steps:
>
> 1. Browse to the following Microsoft Web site:
> http://www.microsoft.com/downloads/details.aspx?FamilyId=8F0A8DF6-4A21-4B43-
> BF53-14332EF092C9&displaylang=en
>
> 2. Click the link to download Component Checker. When you are prompted by
> the browser, save Cc.exe (a self-extracting executable file) to the
> desktop.
>
> 4. On the desktop, double-click Cc.exe; this extracts the Component
> Checker
> files and installs to the default location, C:\Comcheck.
>
> B. To use Component Checker to check the MDAC version, follow these steps:
>
> 1. From the Start menu, click Run.
>
> 2. In the Open text box, type c:\comcheck\comcheck.exe and then click OK.
>
> 3. In the Component Checker - Choose Analysis Type dialog box, select
> Perform Analysis of your machine and automatically determine the release
> version, and then click OK.
>
> 4. The program attempts to identify the MDAC version on your computer by
> scanning all of the core MDAC files and registry settings. This process
> normally takes several minutes.
>
> When finished, you should receive the following message: The MDAC version
> that is closest to the version on your computer is 'XXXX'.
>
> 5. Click OK.
>
> 6. A summary of the Component Checker scan appears. Note that the Dir,
> FileDescription, and FileSize errors can be safely ignored.
>
> Then go in safe mode on the machine and manually replace the whole package
> included in the desired version of MDAC to try to resolve the issue.
>
> How about the result?
>
> I am currently standing by for an update from you and would like to know
> how things are going on your end. If you have any questions or concerns on
> the issue, please don''t hesitate to let me know.
>
> Have a nice day!
>
> Best Regards,
>
> Jenny Wu
> 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: "Berry Janssen" <soeb555@xxxxxxxxxxx>
>>Newsgroups: microsoft.public.windows.server.sbs
>>Subject: MDAC and SBS2003 SP1
>>Date: Sun, 31 Jul 2005 17:39:29 +0200
>>X-Priority: 3
>>X-MSMail-Priority: Normal
>>X-Newsreader: Microsoft Outlook Express 6.00.2900.2527
>>X-RFC2646: Format=Flowed; Original
>>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527
>>Lines: 26
>>Message-ID: <42ecf0af$0$6106$9a6e19ea@xxxxxxxxxxxxxxxxxxxxxxxxx>
>>Organization: Newshosting.com - Highest quality at a great price!
> www.newshosting.com
>>X-Complaints-To: abuse@xxxxxxxxxxxxxxx
>>Path:
> TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!newsfeed00.sul.t-online.de!t-onli
> ne.de!border2.nntp.dca.giganews.com!nntp.giganews.com!nx01.iad01.newshosting
> com!newshosting.com!post01.iad01!not-for-mail
>>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:140178
>>X-Tomcat-NG: microsoft.public.windows.server.sbs
>>
>>Hello all,
>>
>>Since I upgraded my SBS2003 server with W2003 SP1 and SBS2003 SP1 (all
>>according to the official update document from Microsoft) I am having
>>troubles with some applications.
>>
>>If I install a new application that needs MSDART.DLL I'm getting an error:
>>"The procedure entry point DefWindowProcI could not be located in the
>>dynamic link library MSDART.DLL"
>>
>>This has to do with MDAC. Now on the microsoft site it says that I have to
>>reinstall MDAC 2.8 SP1, but when I run ComChecker.exe it says that I have
>>MDAC 2.8 SP2. The funny thing is that I cannot find SP2 on the Microsoft
>>site. The version number of the MDAC dll's is 2.82.1830.0
>>
>>Also my Veritas Backup Exec service won't start anymore which I assume
>>have
>>the same cause, and my sharepoint website is not available anymore which
>>could be another problem according to the event log. But I will post this
> in
>>another message (topic: Sharepoint and SBS2003 SP1)
>>
>>Hope anyone can help!
>>Thanks in advance,
>>Berry
>>
>>
>>
>>
>
.
- Follow-Ups:
- Re: MDAC and SBS2003 SP1
- From: Jenny Wu (MSFT)
- Re: MDAC and SBS2003 SP1
- References:
- MDAC and SBS2003 SP1
- From: Berry Janssen
- RE: MDAC and SBS2003 SP1
- From: "Jenny wu [MSFT]"
- MDAC and SBS2003 SP1
- Prev by Date: Problems with ASP websites after Sp1 isa 2004 install
- Next by Date: Re: SBS 2003 Hangs with "Applying Computer Settings"
- Previous by thread: RE: MDAC and SBS2003 SP1
- Next by thread: Re: MDAC and SBS2003 SP1
- Index(es):
Relevant Pages
|
