Forum Replies Created

Viewing 10 replies - 1 through 10 (of 10 total)
  • A normal part of db restore is to create an empty db on the new server with the same name as the old database. Then import the db file into the new database.

    I know this process works as I just did it.

    example commands (mySql command window)

    CREATE DATABASE oldBlog;
    GRANT USAGE ON oldBlog.* to db_user@localhost IDENTIFIED BY ‘db_passwd’;
    GRANT ALL ON oldBlog.* TO db_user@localhost IDENTIFIED BY ‘db_passwd’;

    Then from a command prompt (in the bin directory is easiest) type:

    mysql -u username -p dbname < blogSQLbackupfile.sql

    (This assumes not compressed, file is in the same directory as where you are executing the command)

    I do not use MyPhpAdmin so I don’t know if you need to also create an empty DB before running the import tool or if it will do it for you.

    hth

    O

    IMHO their support leaves a lot to be desired but if you have time or are experienced they are a good economic host.

    A little off topic but related sort of. The thing that gives me the hardest time is making the DNS glue records because the interface is so poor. I mention it here just in case any one else is stuck on them.

    Simply:

    A glue record is an A record in your own domain file that points to a DNS server inside that domain.

    On 1&1 (after moving the domain to them) you need to create a subdomain (i.e. dns.your-domain.com) then wait for it to get fully created. Once created you go the the EDIT dns settings menu and click “other IP” then set the dns servers IP there.

    Now you can go back to your root domain (your-domain.com) and point the DNS record from 1&1 or your old host to your dns.your-domain.com address. Your domain will be back up as soon as the information propagates with all your old records and manageable by you directly now.

    Thread Starter fangfoo

    (@fangfoo)

    Thread Starter fangfoo

    (@fangfoo)

    Yeah when I hit that second url page (on my server) draws blank. Hmmm, I’ll keep digging.

    Thread Starter fangfoo

    (@fangfoo)

    No I am past all those types of errors. My last thread shows how to configure successfully PHP/IIS for 2003.
    Take for example in MS SQL when I create a new empty DB the very next thing I do is imprint it with a structure, either manually or via a script.
    How does that occur with WP? I’ve set WP to look at the localhost and logon with a username and password but now all pages php simply load blank.
    After the 5 minute wiki config what is the next step? Should I get a logon box at the default wp url on my box? Do I need to point to another php file in the wpadmin directoy and run that to continue? Is there a log the wp php creates so I can see if it is having issues hitting MySQL?
    Any ideas/pointers are appreciated.

    Thread Starter fangfoo

    (@fangfoo)

    Yes it’s all local. Simply I have:
    Empty MySQL DB with user (with all rights for now) for WP
    PHP 5 installed and working in IIS
    MySQL up and running without error
    WP unzipped into it’s own directory
    WP ini file modified with MySQL bd/user info
    What should happen next? Pretty sure blank pages indicate something is wrong.

    Thread Starter fangfoo

    (@fangfoo)

    Saw that thanks (it’s in a thread a bit down from the top here on page 1). I’ve already completed that step. Thing is now the index.php page just draws blank. Figure that meanst a) myqsql db isn’t correct or b) I’m not doing the next step correctly. I’m leaning towards a).

    Thread Starter fangfoo

    (@fangfoo)

    Don’t forget that in 2 to uncomment out:
    cgi.force_redirect = 0
    And verify it is set to 0 not 1 or you will get a warning redirect page.

    Thread Starter fangfoo

    (@fangfoo)

    Found this (note existing ISAPI issue):
    romanysaad at aol dot com
    15-Jul-2004 03:36
    I setup 5.0.0 Release with Windows 2003 Web Edition in the same exact manner as bitboy_cn did and… SUCCESS!
    Also, I received the same error when running with the ISAPI module… only CGI worked 100% properly with no access violation message.
    bitboy_cn at hotmail dot com
    14-Jul-2004 02:23
    Install PHP 5.0.0 Release (Windows Binary in ZIP format) on Windows Server 2003/IIS 6.0 with CGI mode
    1. Unzip the binary to a specified folder, for example, c:\php
    2. Copy php.ini-dist to %SYSTEMROOT%, rename it to php.ini, and amend any settings needed as described in this manual
    3. !!IMPORTANT!! In Internet Information Service Manager (MMC), add a Web Service Extension, name it PHP (or anything else you like), add required file (in this case) c:\php\php-cgi.exe (NOT php.exe or php-win.exe), and enable it.
    4. Add .php file mapping to your site with php-cgi.exe too.
    Done!
    p.s.
    If configure PHP 5.0.0 Release in ISAPI mode on this platform, there is a line added to each page bottom on output said something like “PHP has encountered an Access Violation at 017A73CD”. It’s a bug?or server environment issue? I’m still studying.

    Thread Starter fangfoo

    (@fangfoo)

    Ok it’s a PHP error. Anyone else running PHP 5 on 2003? I’m looking to confirm permissions. Not getting far at the PHP boards, it’s a quiet Sunday there heh.

Viewing 10 replies - 1 through 10 (of 10 total)