Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
0

ASP.NET database connection failure

New Here ,
May 16, 2007 May 16, 2007

Copy link to clipboard

Copied

I'm trying set up a database connection between an ASP.NET C# site and my SQL server database using DW CS3. I'm getting the generic Unauthorized error code. ("HTTP Error Code 401 Unauthorized").

I've tried to create connections to the SQL server using both a SQL server connection and also using the OLE DB connection. When I use the OLE DB connection I've tried using the "Build" wizard button. The wizard has a "Test Connection" on the "Connection" tab. When I test the connection here, it says that I the connection is successful. However, when I test using the connection string dialog box, I get the Unauthorized error. The following is the connection information. I know the information is correct because I am able to use MS Visual Web Developer to connect to the DB using the same information (actually I'm using the SQL server connection rather than the OLE connection in VWD).

I've given the itembank_user all permissions in the DB. Is there something I'm missing here, or is there some bug in DW CS3's ASP.NET connection. Have others of you been able to create ASP.NET connections using DW3?

"Provider=SQLOLEDB.1;
Password=itembank_pw;
Persist Security Info=True;
User ID=itembank_user;
Initial Catalog=ItemBank;
Data Source=dpsat01"

Thanks much for any help.
Steve
TOPICS
Server side applications

Views

386
Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Correct answer

Deleted User
May 21, 2007 May 21, 2007
Best thing is go to Microsoft and download for FREE. I know Microsoft and free is usually mutually exclusive, but get Visual Web Developer Express 2005. This is a WYSIWYG style editor that used .NET 2.0.

MS is also putting out Web Expression as a tool for .NET 2.0, and replaces FrontPage. To be honest Dreamweaver even CS3 is not very good for .NET, a market I think Adobe missed or maybe thought why compete with MS in this area, not what they thought.

Good luck, I've used Dreamweaver since ver...

Votes

Translate
New Here ,
May 17, 2007 May 17, 2007

Copy link to clipboard

Copied

Okay. I've fixed the problem. I had .NET 2.0 installed rather than 1.1.

This does pose a bit of a problem in that my organization is quickly moving to 2.0 (and maybe 3.0). I saw on other threads from 2006 that 2.0 wasn't supported at that time. Has a patch been developed for this or is DW just abandoning .NET development?

Steve

Votes

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Guest
May 21, 2007 May 21, 2007

Copy link to clipboard

Copied

Best thing is go to Microsoft and download for FREE. I know Microsoft and free is usually mutually exclusive, but get Visual Web Developer Express 2005. This is a WYSIWYG style editor that used .NET 2.0.

MS is also putting out Web Expression as a tool for .NET 2.0, and replaces FrontPage. To be honest Dreamweaver even CS3 is not very good for .NET, a market I think Adobe missed or maybe thought why compete with MS in this area, not what they thought.

Good luck, I've used Dreamweaver since version 2 and I've also used both the other, they're easy to pick up once you've used Dreamweaver

Votes

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
May 21, 2007 May 21, 2007

Copy link to clipboard

Copied

LATEST
Thanks for the information. I too have used Dreamweaver for many years, and have grown very accoustomed to the interface. Visual Web Developer Express is a bit different, but I think the problem is as much being unfamiliar with ASP.NET as it is with the software.
Steve

Votes

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines