Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
XCCC: You Cannot Schedule a Meeting and an 80005008 Error Occurs If the sAMAccountName Does Not Match the Windows 2000 User Logon Name
Article ID: 320002 - View products that this article applies to.
This article was previously published under Q320002
If you use Web Scheduler to schedule an online meeting while you are logged on with a Microsoft Windows NT Server 4.0 or Microsoft Exchange Server 5.5 mailbox, you may not be able to schedule the meeting, and an 80005008 error may occur. This problem may occur in a mixed Windows NT 4.0 and Microsoft Windows 2000 Server environment in which an Exchange 2000 Conferencing Server computer is installed.
This problem may occur if the Windows NT 4.0 sAMAccountName is not the same as the Windows 2000 logon name.
To resolve this problem, obtain the latest service pack for Microsoft Exchange 2000 Server. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/301378/EN-US/ )XGEN: How to Obtain the Latest Exchange 2000 Server Service Pack
The English version of this fix has the file attributes (or later) that are listed in the following table.
Collapse this tableExpand this table
IMPORTANT: You have to apply this fix on the Exchange 2000 server that has the Exchange Conferencing Service meeting pages, and also on the Exchange 2000 Conferencing server. This fix updates the Xconfmgr.exe file and the Xwebsched.dll file on the Exchange 2000 server and the Exchange 2000 Conferencing server. The Xconfmgr.exe file is updated on all of the Exchange 2000 Conferencing servers that the Conference Management Service (CMS) is installed on. The Xwebsched.dll file is updated on all of the Exchange 2000 Conferencing servers that the Internet Information Services (IIS) component is installed on, including any remote Exchange 2000 servers.
Microsoft has confirmed that this is a problem in Microsoft Exchange 2000 Server. This problem was first corrected in Microsoft Exchange 2000 Server Service Pack 3.