Microsoft KB Archive/309262

From BetaArchive Wiki
Knowledge Base


Subscription Notifications Always Contain NetBIOS Names

Article ID: 309262

Article Last Modified on 2/20/2007



APPLIES TO

  • Microsoft SharePoint Portal Server 2001



This article was previously published under Q309262

SYMPTOMS

SharePoint Portal Server sends e-mail notification messages for document approval requests and subscription notifications. The URLs in the notification messages use the network basic input/output system (NetBIOS) name of the server by default, but you can modify SharePoint Portal Server to use the server's fully qualified domain name (FQDN) instead.

For additional information about how to modify SharePoint Portal Server to use the server's FQDN, click the article number below to view the article in the Microsoft Knowledge Base:

296602 How to Specify the Server Name That Is Used in E-mail Notification Messages


However, even after you update the urn:schemas-microsoft-com:publishing:ServerURL attribute to use a FQDN, the NetBIOS name may still be used in the subject of the e-mail message.

CAUSE

This problem can occur because SharePoint Portal Server reads the computer name of the server that SharePoint Portal Server is running on and uses that computer name to build the subject of the message. There is no code that reads the schema attribute to reflect that name in the subject of the message.

RESOLUTION

To resolve this problem, obtain the latest service pack for Microsoft SharePoint Portal Server 2001. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

312963How to Obtain the Latest SharePoint Portal Server 2001 Service Pack


The English version of this fix should have the following file attributes or later:

   Date          Time       Version          Size     File name     
   --------------------------------------------------------------

   31-JUL-2002   02:06:24   10.145.4629.30   28,672   Pkmntfy.exe
                

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in SharePoint Portal Server 2001 Service Pack 1.
This problem was first corrected in Microsoft SharePoint Portal Server 2001 Service Pack 2.

Keywords: kbhotfixserver kbqfe kbshareptportalsvr2001sp2fix kbbug kbfix KB309262