Microsoft KB Archive/828893

= You receive a client cannot list the server's data source error message when you add a system data source to a Web site in FrontPage 2003 =

Article ID: 828893

Article Last Modified on 10/23/2006

-

APPLIES TO


 * Microsoft Office FrontPage 2003

-





Important This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows Registry



SYMPTOMS
In Microsoft Office FrontPage 2003, when you use Web Settings on the Tools menu to add a system data source on a Web server as a database connection to your Web, if you click Browse to locate a data source, you receive the following error message:

Server error: This web server does not allow a client to list the server's data sources. Contact your system administrator for more information.



CAUSE
This problem may occur if the value 0 has been assigned to the following registry key:

The value 0 makes the list of system data source names (DSNs) unavailable.



RESOLUTION
Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

To resolve this problem, change the value of the  key to 1. To do this, follow these steps.

Note After you complete the following procedure, all client users can view all DSNs. You may not want all client users to be able view all DSNs.  Click Start, click Run, type regedit, and then click OK. Expand the following registry key:

 In the right pane, click  . On the Edit menu, click String, type 1, and then click OK . Quit Registry Editor.</ol>

<div class="workaround_section">

WORKAROUND
To work around this problem, follow these steps: <ol> On the client computer, start FrontPage 2003.</li> In the Getting Started pane, click Create a new page or site.</li> In the New pane, click One page Web site.</li> In the Web Site Templates dialog box, in the Specify the location of the new Web site box, type the location on the Web page, and then click OK.

Alternatively, you can click Browse, and then find the location of the new Web page.</li> In the Folder list, double-click Default.htm.</li> On the Tools menu, click Site Settings, and then click the Database tab.</li> Click Add, click Custom definition, and then click Advanced.</li> In the Connection string box, type the Data Source Name (DSN) that you want to use, and then click OK.

For example, type a Data Source Name that is similar to the following:

DSN=Northwind;DRIVER=(Microsoft Access Driver (*.mdb))

</li> In the New Database Connection dialog box, click OK, and then in the Web Settings dialog box, click Verify.</li> Click Apply, and then click OK.</li></ol>

<div class="status_section">

STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section of this article.

<div class="moreinformation_section">

MORE INFORMATION
When you create a database connection in FrontPage 2003, you can typically use Browse to locate the system data source that you want to use. However, sometimes when many Webs use the same server, and many system DSNs exist, you may not want to permit everyone who is working on a Web page to view all the system data sources on the server. To prevent users from browsing DSNs in FrontPage 2003, you can set the following registry key to 0:

Despite this, you can still type a connection string yourself by using the Advanced Connection Properties as described in the &quot;Workaround&quot; section of this article.

Additional query words: FP2003

Keywords: kbconfig kberrmsg kbprb KB828893

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.