Announcement

Collapse
No announcement yet.

Error activating SiteBuilder. (Error code 200), Please try again

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Error activating SiteBuilder. (Error code 200), Please try again

    Having an issue accessing SiteBuilder

    When I click "On" it says "working" and then I get the following error..

    "Error activating SiteBuilder. (Error code 200), Please try again."

    I searched the forum for this error code and turned up nothing. Any ideas on how to fix this?

    My webhost is 1and1
    Forum URL:
    http://s285730042.onlinehome.us/canada/



  • #2
    In your /config.php make sure that $config['report_all_php_errors'] is set to false and $config['no_template_notices'] is set to true.

    If it continues, then make sure the displaying of notices is turned off in PHP.
    Translations provided by Google.

    Wayne Luke
    The Rabid Badger - a vBulletin Cloud demonstration site.
    vBulletin 5 API - Full / Mobile
    Vote for your favorite feature requests and the bugs you want to see fixed.

    Comment


    • #3
      Checked my config.php file. Settings were already as you suggested.

      $config['report_all_php_errors'] = false;
      $config['no_template_notices'] = true;

      Still receiving the same error. How do I go about turning off displaying of notices in PHP?

      - - - Updated - - -

      Checked my Chrome developer console and found the following...

      vBulletin.loadingIndicator.show Counter: 1 Source: ajaxStart global.js:1
      activating sitebuilder failed! error:SyntaxError: Unexpected token < global.js:1
      activate-sitebuilder complete. global.js:1
      vBulletin.loadingIndicator.hide Counter: 0 Source: ajaxStop global.js:1

      Comment


      • #4
        Can you try Firefox?

        Are you using Chrome on a Mac?
        Translations provided by Google.

        Wayne Luke
        The Rabid Badger - a vBulletin Cloud demonstration site.
        vBulletin 5 API - Full / Mobile
        Vote for your favorite feature requests and the bugs you want to see fixed.

        Comment


        • #5
          Nope Chrome on a PC.

          Tried the Firebug console on Firefox. Here is the error I received.


          vBulletin.loadingIndicator.show Counter: 1 Source: ajaxStartPOST http://s285730042.onlinehome.us/cana...te-sitebuilder 200 OK [IMG]chrome://firebug/content/blank.gif[/IMG] 697ms
          activating sitebuilder failed! error:SyntaxError: JSON.parse: unexpected character
          activate-sitebuilder complete.
          vBulletin.loadingIndicator.hide Counter: 0 Source: ajaxStop


          - - - Updated - - -

          Click image for larger version

Name:	sitebuilder_error.jpg
Views:	1
Size:	71.2 KB
ID:	3690485

          Here is a screenshot of the error.

          Comment


          • #6
            This is your error:
            JSON.parse: unexpected character

            Make sure there are no invisible characters at the beginning of your /config.php file. You would need to save it as ASCII or ANSI format. Not UTF-8.
            Translations provided by Google.

            Wayne Luke
            The Rabid Badger - a vBulletin Cloud demonstration site.
            vBulletin 5 API - Full / Mobile
            Vote for your favorite feature requests and the bugs you want to see fixed.

            Comment


            • #7
              To follow up. I shamefully figured it out. It didnt work because my MySql version didnt meet the minimum requirements on 1And1 hosting.

              I reinstalled under HostGator with a hosting package that meets the minimum requirements and it works just fine.

              Sorry for confusion.

              Comment


              • #8
                Glad you got it sorted
                Aakif Nazir
                vBulletin Support Team

                Comment


                • #9
                  I get this same error... my version of mysql meets the requirements.
                  Reality Check!

                  Comment


                  • #10
                    I have the same problem you can not solve?
                    I can't activate site builder

                    Comment


                    • #11
                      I have all the minimum requirements met.
                      Still getting this error:
                      Error activating SiteBuilder. (Error code 200)

                      Anybody have a solution for this??

                      Comment


                      • #12
                        As per post 6:

                        Make sure there are no invisible characters at the beginning of your /config.php file. You would need to save it as ASCII or ANSI format. Not UTF-8.
                        Vote for:

                        - *Admin Settable Paid Subscription Reminder Timeframe*
                        -
                        *PM - Add ability to reply to originator only*
                        - Add Admin ability to auto-subscribe users to specific channel(s)
                        - Highlight the correct navigation tab when you are on a custom page
                        - "Quick Route" Interface...
                        - Allow to use custom icons for individual forums

                        Comment


                        • #13
                          I've checked, no change in config.php. I have the same problem too, can't access site builder

                          Comment


                          • #14
                            I discovered the same problem. I found that if I navigate directly to the forum and log in as Administrator Site Builder works. As soon as I click on a link on the Admin link, whether I log in to the control panel or not, then return to the forum page, I can no longer activate Site Builder and get this error.

                            Try logging out, closing the browser, then go directly to the forum page and log in, then see if Site Builder works.

                            Clicking on modcp link has the same result.

                            Same result with IE or Firefox, but slightly different error.


                            Comment

                            Related Topics

                            Collapse

                            Working...
                            X