1. Please take a little time for this simple survey! Thank you for participating!
    Dismiss Notice
  2. Dear Pleskians, please read this carefully! New attachments and other rules Thank you!
    Dismiss Notice
  3. Dear Pleskians, I really hope that you will share your opinion in this Special topic for chatter about Plesk in the Clouds. Thank you!
    Dismiss Notice

Upgrade to 10.4.4 hangs.

Discussion in 'Plesk 10.x for Windows Issues, Fixes, How-To' started by tino, Feb 14, 2012.

  1. tino

    tino Basic Pleskian

    24
    23%
    Joined:
    Mar 6, 2008
    Messages:
    70
    Likes Received:
    0
    If I try to upgrade Plesk 10.3.1 to 10.4.4 on Windows 2003, the upgrade procedure hangs.

    I checked process explorer, and see that wmic is trying to get the IP addresses of the machine.
    This is in fact a Virtuozzo Virtual Machine. Could this be the culprit?

    I can kill the wmic process in process explorer, but I'm not sure if I can ignore the error this incurs;
    FATAL_ERROR: Unable to get IP address

    The wmic command does run fine on my machine;

    C:\>wmic path win32_NetworkAdapterConfiguration get IPaddress
    IPAddress

    {"1.2.3.4", "1.2.3.5"}
    {"10.0.0.14"}

    Any ideas?

    Tino
     
    Last edited: Feb 14, 2012
  2. shall

    shall Regular Pleskian

    26
    57%
    Joined:
    Apr 2, 2007
    Messages:
    226
    Likes Received:
    0
    I'm having the exact same problem. It's hanging at that command and won't proceed any further. I waited 2 hours the first time before killing it and starting over, then 20 minutes the next couple times, and now I've been waiting another half hour or so. The KB article Parallels posted doesnt make sense - I never see that point!
     
  3. tino

    tino Basic Pleskian

    24
    23%
    Joined:
    Mar 6, 2008
    Messages:
    70
    Likes Received:
    0
    The KB article does point in the proper direction to where the process fails. Yet, the step mentioned in the KB article (where the installer queries the system for available memory by means of WMI) is not the step where the installer is choking on in my (and your) case.
    Hence, we cannot simply kill the wmic process since the step gathers crucial information for the upgrade process.

    Would be nice if this could be fixed. This is a blocker for our 10.4 deployment on Windows.

    Tino
     
  4. IgorG

    IgorG Forums Analyst Staff Member

    49
    24%
    Joined:
    Oct 27, 2009
    Messages:
    24,572
    Likes Received:
    1,243
    Location:
    Novosibirsk, Russia
  5. tino

    tino Basic Pleskian

    24
    23%
    Joined:
    Mar 6, 2008
    Messages:
    70
    Likes Received:
    0
    These are the (interesting) results of the pre-upgrade checker;
    (Only the parts that did not end up with an 'OK')

    I'll try to fix these 'problems' first, and then try to run the upgrade again.

    Thanks for the info. Hope this will work!

    Tino
     
  6. tino

    tino Basic Pleskian

    24
    23%
    Joined:
    Mar 6, 2008
    Messages:
    70
    Likes Received:
    0
    - Step 3: The latest autoinstaller stalls at the same point; so ai --console hangs at the same point.
    - Step 7: This is, according to the KB article a bug. I checked the email addresses, and it appears so.
    - Step 12: No problems whatsoever.
    - Step 15: Post upgrade, so no show stopper...

    So this didn't solve anything...

    Any other ideas?
     
  7. shall

    shall Regular Pleskian

    26
    57%
    Joined:
    Apr 2, 2007
    Messages:
    226
    Likes Received:
    0
    I was finally able to get this to progress past the initial state detection by killing the "win32_NetworkAdapterConfiguration get IPaddress" process. It gets to this point within a couple seconds of clicking the 'upgrade' link and doesn't stay more than 2 seconds, so it's critical that you have ProcExp running and branched down to the correct process before starting the upgrade, or you'll miss it.
     
  8. MitchellK

    MitchellK New Pleskian

    19
    35%
    Joined:
    Aug 27, 2009
    Messages:
    6
    Likes Received:
    0
    Shell,
    I'm experiencing this problem as well, but when I try to kill the WMIC process, I get the "FATAL_ERROR: Unable to get IP address" error message. Did you just ignore this message or were you able to bypass this. I was hoping to get this upgraded tonight, but it doesn't look like it is going to happen.
     
  9. shall

    shall Regular Pleskian

    26
    57%
    Joined:
    Apr 2, 2007
    Messages:
    226
    Likes Received:
    0
    I received that error as well, but ignored it and the upgrade went smoothly anyway.
     
  10. MitchellK

    MitchellK New Pleskian

    19
    35%
    Joined:
    Aug 27, 2009
    Messages:
    6
    Likes Received:
    0
    Shall,
    Thanks for getting back to me. Strangely I went back and restarted the installation last night and the upgrade went fairly smoothly (although it did take close to forever to finish and it didn't remove the sitepreview.dll ISAPI filter and thus caused nothing to work initially...but I digress). Well, I'm just grateful that I got the upgrade to work. Thanks again for your help!
     
  11. shall

    shall Regular Pleskian

    26
    57%
    Joined:
    Apr 2, 2007
    Messages:
    226
    Likes Received:
    0
    I experienced the sitepreview isapi issue as well and had to manually remove it from every site. AAAaaaarrrrggggghhhh! Removing a single ISAPI reference from a few hundred websites is a total and absolute waste of time. Sigh.

    Oh, the other problem I've been having is that ALL of the spam filter settings were purged, resulting in *authenticated* email coming from user A on the server, sent to user B on the server, is always treated as spam. I've upgraded to ME Ent 6 but the problem remains. Well, mostly. I've disabled filtering completely - so now legitimate messages are NOT being tagged, but neither are the spam messages.
     
  12. MitchellK

    MitchellK New Pleskian

    19
    35%
    Joined:
    Aug 27, 2009
    Messages:
    6
    Likes Received:
    0
    Oof. Sounds like no fun at all! Fortunately, the only place I had to remove the siteremove.dll ISAPI filter was on the "Web Sites" general setting. If I were in your shoes, I probably would've tried editing the metabase file directly to remove the filters. (Of course, I probably would have monkeyed up my server too!) For the spam settings, I use MailEnable rather than the SpamAssassin tools with Plesk so at least I didn't have to worry with that. Hopefully Plesk 11 will be a better upgrade!
     
Loading...