Server CreateObject Failed

Last post 03-09-2006, 4:38 PM by rcroeder. 5 replies.
Sort Posts: Previous Next
  •  03-27-2005, 12:00 PM 5012

    Server CreateObject Failed

    Hi Adam.
     
    I have a Server License, I install CuteEditor but when I try to load any example page the result is:
    Server object
    error 'ASP 0177 : 800401f3'

    Server.CreateObject Failed

    /editor/include_CuteEditor.asp, line 1230

    Invalid ProgID.
    What is missing ? Can you help me??
    Thanks

  •  03-27-2005, 2:10 PM 5014 in reply to 5012

    Re: Server CreateObject Failed

  •  03-09-2006, 11:34 AM 16888 in reply to 5014

    Re: Server CreateObject Failed

    I am getting the same error and I need more information than this post linking to a generic microsoft message about this error.
    Here is the specific error. I have seen a couple of other inconclusive posts on this site. Please help us get this deployed.
    Server object error 'ASP 0177 : 800401f3'

    Server.CreateObject Failed

    /dbanksql/cuteeditor/CuteEditor_Files/include_CuteEditor.asp, line 861

    Invalid ProgID. For additional information specific to this message please visit the Microsoft Online Support site located at: http://www.microsoft.com/contentredirect.asp.

  •  03-09-2006, 3:17 PM 16899 in reply to 5012

    Re: Server CreateObject Failed

    What version of CuteSoft are you using or what is on line 1230 of the include_CuteEditor.asp file
     
    RC
  •  03-09-2006, 4:21 PM 16910 in reply to 16899

    Re: Server CreateObject Failed

    I am using the new domain version (5 I think), just downloaded a couple days ago. The line(s) where the errors are occurring is the server.createobject("msxml2.4.0"). I think that our production server only has msxml3 because I searched for this dll and found several version of msxml3. Before upgrading this, however, I want to make sure what is going on. I haven't heard anything  back from support yet.
  •  03-09-2006, 4:38 PM 16916 in reply to 16910

    Re: Server CreateObject Failed

    I figured that what was causing your problem.
     
    In the current code they are using
     
    set doc = server.CreateObject("MSXML2.DomDocument.4.0")
     
    You can use
     
    set doc = server.CreateObject("MSXML2.DomDocument")
     
    and you will need to change it through out several files
     
    or you could add something like this to every createobject but you will still have to keep tract of the version
     
    on error resume next
    set doc = server.CreateObject("MSXML2.DomDocument.4.0")
    if isobject(doc)=false then
        set doc = server.CreateObject("MSXML2.DomDocument.2.0")
    end if
    if isobject(doc)=false then
        set doc = server.CreateObject("MSXML2.DomDocument")
    end if
    on error goto 0
     
     
    Another way would be to define a constant in some include files that get loaded in every page. I do this to keep track of my global constants and paramters about a site.
     
    const XMLDOMVER = "MSXML2.DomDocument.3.0"
     
     
    and on the create object 
     
    set doc = server.CreateObject( XMLDOMVER)
     
    I think I like the third way better now that I think on it more. I will have to update my other post
     
    RC
View as RSS news feed in XML