We help IT Professionals succeed at work.

Check out our new AWS podcast with Certified Expert, Phil Phillips! Listen to "How to Execute a Seamless AWS Migration" on EE or on your favorite podcast platform. Listen Now

x

Database Result Wizard Error "Operation Failed"

dorman
dorman asked
on
Medium Priority
364 Views
Last Modified: 2013-12-24
After Install demo of Office 2003  with Frontpage 2002, and change any Database Result Wizard, all the results of the different database connections shows this error "The operation failed.  If this continues, please contact your administrator server" .  The server with the asp pages is Windows 2000 server. The problem has been reported for Frontpage 2003 under Q817029, but this solution does not work. Any Idea
Comment
Watch Question

Author

Commented:
From: http://www.frontpagewebmaster.com/m-185093/tm.htm

Ahhhh... I got it. I started comparing the ASP code from the Windows 2000 server with the code from the Windows Server 2003. I saw a reference to the fpdbrgn1.inc file. I compared the file from each server side by side and there were differences.

Here is the additional code that was in the Windows Server 2003 fpdbrgn1.inc file:

Set fp_dictParams = Server.CreateObject("Scripting.Dictionary")
Set fp_dictColTypes = Server.CreateObject("Scripting.Dictionary")
fp_iParam = 1
' there need to be at least 5 more characters in the string for there to be input parameters (::[_a-z]::)
Do While (Not fp_fError) And (fp_iCurrent + 5 < Len(fp_sQry) And Instr(fp_iCurrent, fp_sQry, "::") > 0)

Too much to post here, but after I copied the file from the Windows 2000 Server to the Windows Server 2003, the .asp page is working  

This works to me.

Don't know why the fpdbrgn1.inc page was changed for 2003, the server where the asp page is windows 2000 server  

Commented:
Dorman ,

i am so happy i stumbled across your comment for i had exactly the same problem.

Do you know how the fpdbrgn1.inc gets changed?

Thank you,

Christina

Author

Commented:
I think that FrontPage makes the change, This error appear after upgrade to Office 2003 and use FrontPage to modify any Database Result.

Now i have FrontPage 2003 and still working over a Windows 2000 server and every is fine.

Dorman

Author

Commented:
Corey,

Yes, I found the solution, thanks for refund my points.

Dorman
Unlock this solution with a free trial preview.
(No credit card required)
Get Preview
Unlock the solution to this question.
Thanks for using Experts Exchange.

Please provide your email to receive a free trial preview!

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.