Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 898721 - Last Review: September 27, 2006 - Revision: 1.4
You receive a "Database Results Wizard Error" error message when you open or browse Database Results Wizard ASP pages or ASP.NET pages in FrontPage 2003
In Microsoft Office FrontPage 2003, you receive the following error message:
Database Results Wizard Error
The operation failed. If this continues, please contact your server administrator.
You issue occurs when the following conditions are true:
- You open or browse Database Results Wizard ASP pages or ASP.NET pages.
- The ASP pages or the ASP.NET pages are connected to a computer that is running Microsoft SQL Server.
If you have verbose error messages enabled in FrontPage 2003, you may receive the following error message:
Database Results Wizard Error
Invalid authorization specification.
This issue occurs when the ASP pages and the ASP.NET pages use Windows authentication through the Database Results Wizard to fetch data. The ASP pages and the ASP.NET pages should use SQL Server standard authentication through the Database Results Wizard to fetch data.
To resolve this issue, you must enable SQL Server standard authentication for the computer that is running SQL Server. To do this, follow these steps:
- On the Tools menu, click Site Settings, and then click the Database tab.
- Click the database connection that you want modify, and then click Modify.
- Click Advanced.
- Under Authorization, click Save this username and password in the data connection, and then type your user name and your password.
You may be able to configure a database connection by using a Universal Data Link (UDL) file to provide connection information. To do this, follow these steps:
- Start Notepad, and then type the following text:
-------------------- Start of UDL file --------------------
[oledb]
; Everything after this line is an OLE DB initstring
Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=Database_Name;Data Source=SQL_Server_Name
-------------------- End of UDL file -------------------- - Save the file to your desktop. Use a .udl file name extension.
- Open the Web site in FrontPage.
- Import the UDL file into your FrontPage Web site. Store the UDL file in the Fpdb folder.
- On the Tools menu, click Site Settings.
- Click the Database tab.
- Click Add.
- Click Custom definition.
- Click Browse.
- Locate the Fpdb folder in the Web site.
- Click Universal Data Link (*.udl) for the file type.
- Click the UDL file, and then click OK.
- Type a name for the database connection.
- Click OK.
- Click Verify to verify the connection.
- Click OK.
You should now be able to create ASP pages and ASP.NET that use this database connection.
Note When you use this workaround to test your ASP pages and your ASP.NET pages, you may receive the following error message:
Database Results Wizard Error
Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.
If you receive this error message, you cannot use the workaround for this issue. You must follow the steps in the "Resolution" section.
For more information, click the following article numbers to view the articles in the Microsoft Knowledge Base:
325877Â
(http://kbalertz.com/Feedback.aspx?kbNumber=325877/
)
How to control access to a database on a Web server in Windows Server 2003
313077Â
(http://kbalertz.com/Feedback.aspx?kbNumber=313077/
)
How to control access to a database on a Web server in Windows 2000
318287Â
(http://kbalertz.com/Feedback.aspx?kbNumber=318287/
)
What you need to use Active Server Pages (ASP) in FrontPage 2002
APPLIES TO
- Microsoft Office FrontPage 2003
| kbdatabase kbasp kbtshoot kbprb KB898721 |
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate