Article ID: 913677
Article Last Modified on 12/5/2007
APPLIES TO
- Microsoft COM+ 1.5, when used with:
- Microsoft Windows Server 2003 Service Pack 1
SYMPTOMS
When you try to start a Microsoft COM+ application on a computer that is running Microsoft Windows Server 2003 with Service Pack 1, you may receive an error message that is similar to the following:
CAUSE
This problem occurs because you use a fully qualified domain name (FQDN) that has more than 16 characters when you configure the account under which the COM+ application runs.
RESOLUTION
Service pack information
To resolve this problem, obtain the latest service pack for Windows Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
889100 How to obtain the latest service pack for Windows Server 2003
Hotfix information
A supported hotfix is now available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix.
To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:
Note If additional issues occur or any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. To create a separate service request, visit the following Microsoft Web site:
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Windows Server 2003 service pack or COM+ 1.5 hotfix rollup package that contains this hotfix.
To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
Prerequisites
You must have Windows Server 2003 installed to apply this hotfix.
Restart requirement
You must restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace any other hotfixes.
File information
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Windows Server 2003 SP1, Itanium architecture
| File name | File version | File size | Date | Time | Platform | SP requirement | Service branch |
|---|---|---|---|---|---|---|---|
| Ole32.dll | 5.2.3790.2628 | 3,999,744 | 28-Jan-2006 | 02:58 | IA-64 | SP1 | Not applicable |
| Rpcss.dll | 5.2.3790.2628 | 859,136 | 28-Jan-2006 | 02:58 | IA-64 | SP1 | Not applicable |
| Wole32.dll | 5.2.3790.2628 | 1,247,744 | 28-Jan-2006 | 02:58 | x86 | SP1 | WOW |
Windows Server 2003 SP1, x64
| File name | File version | File size | Date | Time | Platform | SP requirement | Service branch |
|---|---|---|---|---|---|---|---|
| Ole32.dll | 5.2.3790.2628 | 2,547,200 | 28-Jan-2006 | 02:58 | x64 | SP1 | Not applicable |
| Rpcss.dll | 5.2.3790.2628 | 697,856 | 28-Jan-2006 | 02:58 | x64 | SP1 | Not applicable |
| Wole32.dll | 5.2.3790.2628 | 1,247,744 | 28-Jan-2006 | 02:58 | x86 | SP1 | WOW |
Windows Server 2003 SP1, x86
| File name | File version | File size | Date | Time | SP requirement |
|---|---|---|---|---|---|
| Ole32.dll | 5.2.3790.2628 | 1,247,744 | 28-Jan-2006 | 03:37 | SP1 |
| Rpcss.dll | 5.2.3790.2628 | 421,888 | 28-Jan-2006 | 03:37 | SP1 |
WORKAROUND
To work around this problem, do not use a FQDN when you configure the account under which the COM+ application runs. Instead, type the domain and the user name in the form domain\username.
To view the account under which the COM+ application runs, follow these steps:
- Click Start, click Run, type Dcomcnfg.exe, and then click OK.
- Expand Component Services, expand Computers, expand the computer that you want, and then expand COM+ Applications.
- Right-click the COM+ application you want, and then click Properties.
- On the Identity tab, note the account information in the User box.
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Windows Server 2003 Service Pack 2.
MORE INFORMATION
After you apply this hotfix, the User box on the Identity tab has a 512-character limit. You can type the domain and the user name in the form domain\username, or you can use a FQDN.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
Additional query words: 0x80080005
Keywords: kbwinserv2003sp2fix kbwinserv2003presp2fix kbfix kbbug kbpubtypekc kbhotfixserver kbqfe KB913677
