Re: MDAC and SBS2003 SP1
- From: "Berry Janssen" <soeb555@xxxxxxxxxxx>
- Date: Thu, 11 Aug 2005 19:23:16 +0200
Hi Jenny,
My post did not get posted as I noticed, so here it is again. Sorry for the
delay.
"Berry Janssen" <soeb555@xxxxxxxxxxx> schreef in bericht news:...
> Jenny,
>
> I checked what process is causing the DCOM error. It is STORE.EXE (the
> microsoft Exchange Store) but I cannot find it's description in the
> Component Services tool and therefore I cannot change it's permissions.
>
> What I also noticed was that during SBS SP1 installation I get: "The
> procedure entry point DefWindowProcI could not be located in the dynamic
> link library MSDART.DLL". The same error I get when starting an MDAC based
> application. After two-thirds (2/3) of the service pack installation it
> says that service pack 1 encountered an error and that it should be
> corrected. When I look in the install log there is no error.
>
> I will mail you the logfiles.
>
> Berry Janssen
>
>
>
> "Jenny Wu (MSFT)" <Jenny Wu (MSFT)@discussions.microsoft.com> schreef in
> bericht news:33D11594-864A-4741-9787-8CC22AD4F22B@xxxxxxxxxxxxxxxx
>> Hi Berry,
>>
>> Thanks for your update! I appreciate your time and effort to test. The
>> Component Checker result is correct. For you have applied SBS sp1, that
>> inclues Windows 2003 SP1. After applied Windows 2003 SP1 the MDAC version
>> will update to 2.8 SP2.
>>
>> Based on my research, the issue may be caused by permissions. Please
>> follow
>> my steps to troubleshooting:
>>
>> Suggestion1: Grant the user permissions to start the COM component
>>
>> Grant the user permissions to start the COM component. To do this, follow
>> these steps:
>>
>> 1. Click Start, click Run, type regedit in the Open box, and then click
>> OK.
>> 2. Locate and then click the following registry
>> subkey:HKEY_CLASSES_ROOT\CLSID\CLSID value
>>
>> *Note: In this subkey, "CLSID value" is a placeholder for the CLSID
>> information that appears in the message.
>>
>> 3. In the right pane, double-click AppID.
>>
>> The Edit String dialog box appears. Leave this dialog box open and
>> continue
>> to the next step.
>>
>> 4. Click Start, click Run, type dcomcnfg in the Open box, and then click
>> OK.
>>
>> If a Windows Security Alert message prompts you to keep blocking the
>> Microsoft Management Console program, click to unblock the program.
>>
>> 5. In Component Services, double-click Component Services, double-click
>> Computers, double-click My Computer, and then click DCOM Config.
>>
>> 6. In the details pane, locate the program by using the friendly name.
>>
>> If the AppGUID identifier is listed instead of the friendly name, locate
>> the
>> program by using this identifier.
>>
>> 7. Right-click the program, and then click Properties.
>>
>> 8. Click the Security tab.
>>
>> 9. In the Launch and Activation Permissions area, click Customize, and
>> then
>> click Edit.
>>
>> 10. Click Add, type the user's account name, and then click OK.
>>
>> 11. While the user is selected, click to select the Allow check boxes for
>> the following items:
>>
>> . Local Launch
>> . Remote Launch
>> . Local Activation
>> . Remote Activation
>>
>> 12. Click OK two times.
>> 13. Quit Registry Editor.
>>
>> Suggestion 2: Grant the correct permissions to the Network Service
>> account
>>
>> To grant the correct permissions to the Network Service account, follow
>> these steps:
>>
>> 1. Click Start, click Run, type dcomcnfg in the Open box, and then click
>> OK.
>>
>> 2. In Component Services, double-click Component Services, and then
>> double-click Computers.
>>
>> 3. Right-click My Computer, and then click Properties.
>>
>> 4. Click the COM Security tab.
>>
>> 5. In the Launch and Activation Permissions area, click Edit Default.
>>
>> 6. Click Add, type Network Service, and then click OK.
>>
>> 7. While Network Service is selected, click to select the Allow check
>> boxes
>> for the following items:
>>
>> . Local Launch
>> . Remote Launch
>> . Local Activation
>> . Remote Activation
>>
>> Click OK two times.
>>
>> Try to test, how about the result?
>>
>> If the issue persists, please help me to collect some information to
>> further
>> analyze:
>>
>> 1. Please reproduce the issue and post related error event log in the
>> post.
>>
>> 2. Please give me the SBS SP1 installation log.
>>
>> If the log files are big, please add all files to a zip file and mail to
>> v-yanniw@xxxxxxxxxxxxx
>>
>>
>> For reference:
>>
>> Component Checker utility has been redesigned to provide XML support. The
>> new tool includes updated snapshots for MDAC 2.7 SP1 on Windows XP SP1
>> and
>> MDAC 2.8 SP2 on Windows Server 2003 SP1. The Component Checker tool is
>> designed to help you determine installed version information and diagnose
>> installation issues with the Microsoft Data Access Components (MDAC).
>> MDAC is
>> installed with numerous Microsoft products and can also be redistributed
>> using the redistribution program (mdac_typ.exe) that you can download
>> from
>> the MiSDN Data Access and Storage Developer Center. This version of
>> Component
>> Checker includes updated snapshots for MDAC 2.8 SP2 on Windows Server
>> 2003
>> SP1 and checks for the following versions of MDAC:
>>
>>
>> MDAC 2.1 SP2
>>
>> MDAC 2.5
>>
>> MDAC 2.5 SP1
>>
>> MDAC 2.5 SP2
>>
>> MDAC 2.5 SP3
>>
>> MDAC 2.6
>>
>> MDAC 2.6 SP1
>>
>> MDAC 2.6 SP2
>>
>> MDAC 2.6 SP2 Refresh
>>
>> MDAC 2.7
>>
>> MDAC 2.7 Refresh
>>
>> MDAC 2.7 SP1
>>
>> MDAC 2.7 SP1 Refresh
>>
>> MDAC 2.7 SP1 on Windows XP SP1
>>
>> MDAC 2.8
>>
>> MDAC 2.8 SP1 on Windows XP SP2
>>
>> MDAC 2.8 SP2 on Windows Server 2003 SP1
>>
>> More detail info:
>>
>> http://www.microsoft.com/downloads/details.aspx?FamilyId=8F0A8DF6-4A21-4B43-BF53-14332EF092C9&displaylang=en
>>
>> Hope above information helps.I am looking forward to you! if you have any
>> further concern or question about the issue, please feel free to let me
>> know.
>> We are always happy be assistance of you.
>>
>> 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.
>>
>> "Berry Janssen" wrote:
>>
>>> 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:
>
>
.
- Follow-Ups:
- Re: MDAC and SBS2003 SP1
- From: "Jenny wu [MSFT]"
- Re: MDAC and SBS2003 SP1
- Prev by Date: Re: Sharepoint and SBS2003 SP1
- Next by Date: Re: Installing WSUS with SQL
- Previous by thread: Re: MDAC and SBS2003 SP1
- Next by thread: Re: MDAC and SBS2003 SP1
- Index(es):
Relevant Pages
|
