Wrox Programmer Forums

Need to download code?

View our list of code downloads.

| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read
Classic ASP Professional For advanced coder questions in ASP 3. NOT for ASP.NET 1.0, 1.1, or 2.0.
Welcome to the p2p.wrox.com Forums.

You are currently viewing the Classic ASP Professional section of the Wrox Programmer to Programmer discussions. This is a community of tens of thousands of software programmers and website developers including Wrox book authors and readers. As a guest, you can read any forum posting. By joining today you can post your own programming questions, respond to other developers’ questions, and eliminate the ads that are displayed to guests. Registration is fast, simple and absolutely free .
DRM-free e-books 300x50
Reply
 
Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old August 5th, 2003, 07:48 AM
Registered User
 
Join Date: Aug 2003
Location: , , .
Posts: 3
Thanks: 0
Thanked 0 Times in 0 Posts
Default ASP and Windows 2003 Server

Hi!

I just upgraded my server to Windows 2003.
When I run my homepage on every page that uses ASP code in conjunction with SQL 200 SP3a I get the same error:

Error "8007007f'

The code is:
set ConnObj = Server.CreateObject("ADODB.Connection")
Set daten_RstObj = Server.CreateObject("ADODB.Recordset")
ConnObj.Mode = adModeReadWrite
conn_str="dsn=DSN_FV_WEB;uid=sa;pwd=kuguv"
connObj.Open conn_str
strSQL = "SELECT * FROM Headline_Aktuell WHERE Type <> 'f' ORDER BY Datum DESC;"
daten_RstObj.Open strSQL,ConnObj,adLockOptimistic
daten_RstObj.MoveFirst

The error message indicates that "connObj.Open conn_str" is the line where the error occurs...

Does anybody know what to do????

When I boot the server on windows 2000 everything works fine...


TNX
Gerhard

Reply With Quote
  #2 (permalink)  
Old August 5th, 2003, 06:43 PM
Friend of Wrox
 
Join Date: Jun 2003
Location: Sydney, NSW, Australia.
Posts: 215
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Has you DSN been defined in 2003? What is the text of the error message?

regards
David Cameron
Reply With Quote
  #3 (permalink)  
Old August 6th, 2003, 09:11 AM
Registered User
 
Join Date: Aug 2003
Location: , , .
Posts: 3
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Hi!

I installed Windows 2003 Server on the same partition (Dual Boot).
Then I installed MS SQL 2000 Server in a seperate directory (not to overwrite the existing SQL Server for Windows 2000) with SP3a and rebuilt every database and the DSN´s.

The error message is simply:
Fehler "8007007f'

/n_banner.asp, line 57


Greets
Gerhard

Reply With Quote
  #4 (permalink)  
Old August 6th, 2003, 06:42 PM
Friend of Wrox
 
Join Date: Jun 2003
Location: Sydney, NSW, Australia.
Posts: 215
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Have you installed the latest version of MDAC?

regards
David Cameron
Reply With Quote
  #5 (permalink)  
Old August 7th, 2003, 06:01 AM
Registered User
 
Join Date: Aug 2003
Location: , , .
Posts: 3
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Quote:
quote:Originally posted by David Cameron
 Have you installed the latest version of MDAC?

regards
David Cameron
MDAC 2.7 SP1 installed, same problem...

Greets
Gerhard

Reply With Quote
  #6 (permalink)  
Old August 7th, 2003, 09:19 PM
Friend of Wrox
 
Join Date: Jun 2003
Location: Sydney, NSW, Australia.
Posts: 215
Thanks: 0
Thanked 0 Times in 0 Posts
Default

I'm out of ideas, sorry.

regards
David Cameron
Reply With Quote
  #7 (permalink)  
Old August 10th, 2003, 07:51 AM
Authorized User
 
Join Date: Jun 2003
Location: , , Switzerland.
Posts: 27
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Found on another forum :

Quote:
quote:
Woody Splawn
May 2 2003 20:11 I was working in SQL Server 2000 Developer on my stand alone XP machine and
the power went off. I rebooted my machine and selected Last known good
backup. When I came back into Windows and tried to run SQL Server I got an
error message of Unknown Error: 8007007F. I ran MDAC Component Checker and
it told me that it expected oledb32.dll 2.7.1.9030 but got 2.7.2.9031. I
copied 9030 to the proper location and things are working ok again.
http://www.microsoft.com/downloads/d...displaylang=en

This is the link to download the component checker.
HIH
dikkjo
Reply With Quote
  #8 (permalink)  
Old October 18th, 2003, 12:03 PM
Registered User
 
Join Date: Oct 2003
Location: , , .
Posts: 1
Thanks: 0
Thanked 0 Times in 0 Posts
Default

hi, i got the same error but i'm workin' in MySQL i can't find any reason that would 'cause it to appear so plz help me ...
I tried already to install all kinds of the MDAC versions and tried to remove SQL Server already and still gettin' the same error, what should i do? My OS is Windows 2003 Server I have MYSQL & SQL Server
Serivce workin' together but tried to make them Stop and I removed them too so they won't work at all and still the same :(, PLZ HELP!

Reply With Quote
  #9 (permalink)  
Old November 10th, 2003, 08:35 AM
Registered User
 
Join Date: Nov 2003
Location: , , .
Posts: 3
Thanks: 0
Thanked 0 Times in 0 Posts
Default

You can try to these steps:
1. Remove SQL Server files and registry keys manually. For more information,
please refer to the Microsoft knowledge Base article Q290991 'HOW TO:
Manually Remove SQL Srv. 2000 Default, Named or Virtual [sqlserver]'. The
web link of this article is:
http://support.microsoft.com/support.../q290/9/91.asp.
2. Try to install SQL Server 2000 again.
3. Then, you can get the latest version of MDAC under
http://www.microsoft.com/data.



Best regards,
Gregory Liénard

@iPower
Toekomstlaan 16i
B-2900 Schoten

Web: http://www.ipower.be

_______________________________________________
      MORE VISITORS WITH A PERMANENT
     TOPPOSITION AT THE SEARCH ENGINES

         http://www.Hit-Magnet.com
_______________________________________________
Reply With Quote
  #10 (permalink)  
Old March 23rd, 2004, 06:04 PM
Registered User
 
Join Date: Mar 2004
Location: , , .
Posts: 1
Thanks: 0
Thanked 0 Times in 0 Posts
Default

I had the same problem after upgrading to Windows 2003 Server. I called Microsoft and here is the fix:

Symptoms:
After upgrading from Windows 2000 to Windows 2003 attempting to access a database or data component will result in a '8007007f' or "The specified procedure could not be found" error.

Status:
This is a known issue with some installations of Windows 2003

Workaround:
Extract oledb32.dll from the zip file into these two directories. It's impo
rtant that it be done in this order:
1) C:\WINNT\system32\dllCache
2) C:\Program Files\Common Files\System\OLE DB
3) Reboot the server

Cause:
This issue is caused when the Windows 2003 installer did not update the oled
b32.dll file.

You can dowload the oledb32.dll file here: http://www.promiseweb.com/oledb32.zip

This is per Malcolm Stewart at Microsoft Developer Support

Reply With Quote
Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are Off
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Windows Server 2003 neil.abachi07 Windows Server 1 September 13th, 2007 02:11 PM
How to Instal CDONTS in Windows Server 2003 lakshmi_annayappa Classic ASP Professional 1 April 18th, 2007 01:22 AM
Windows 2003 Server R2 srutter BOOK: Professional Web Parts and Custom Controls ASP.NET ISBN: 0-7645-7860-X 4 February 25th, 2006 06:52 PM
Dot Net on Windows server 2003 khssnl General .NET 1 November 18th, 2005 07:28 AM
Cannot execute ASP in Windows 2003 Server rylemer Classic ASP Basics 1 March 4th, 2005 07:03 PM



All times are GMT -4. The time now is 11:22 PM.


Powered by vBulletin®
Copyright ©2000 - 2019, Jelsoft Enterprises Ltd.
© 2013 John Wiley & Sons, Inc.