locked
Known Issues for Power Pack 1 RC4 RRS feed

  • General discussion

  • Hi Everybody,

    As you know, today we have released Windows Home Server Power Pack 1 Release Candidate 4. While this build is mostly complete, there are a few known issues that we wish to make you aware of, and ask that you not file a bug, unless asked to by a member of the Home Server team or is explicitly stated below.

    Storage:

    ·         A Windows Home Server may blue screen with a specific “THIRD_PARTY_FILE_SYSTEM_FAILURE (108)” error code. This blue screen is generated to verify a specific code path in the Drive Extender filter driver, and doesn’t indicate a failure. In the case that a blue screen occurs please follow the steps outlined in the “What should I do if my home server crashes” section of the Release Documentation to submit the crash information.

    ·         If installing from the Power Pack 1 Server Installation DVD, you may receive an error that the Backup Service is not running. You can ignore this message, as the service will start shortly after login.

    ·         If you attempt to remove a hard drive and the removal fails, Drive Extender Migrator will not attempt any migration passes until the server is restarted.

    ·         If you are using a two drive Windows Home Server, and you remove one drive, and then add a new drive in its place, you may see notifications of file conflicts. You can safely ignore these notifications.

    ·         The “Storage Balanced on” date and time status on the Windows Home Server Console will not display the last time storage was balanced accurately. To update the Storage Balanced status, click on the shared folders tab each time the Home Server Console is opened.

     

    Backup:

    ·         In some scenarios, your Windows Home Server may run out of memory. You may see client-side notifications that the Backup service is not running. If you experience this issue, a workaround is presented below, and we ask that you please file a bug report with the requested information.

     

    Workaround:

    1.       RDP into your Server by using Remote Desktop Connection

    2.       Open System Properties by clicking Start then right-click on My Computer and then click    on Properties

    3.       Select the Advanced tab then click on  the Settings button under the Performance section

    4.       Select the Advanced tab and click the Change button under Virtual Memory

    5.       Increase minimum and maximum page file size to 3000MB if you have values smaller than that displayed for the pagefile size.

     

    What to do when filing a bug:

    ·               Upload Error Reporting (TALQ) logs by running Toolkit (insert link to bug report doc on Connect)

    ·               Include information about the size of the pagefile

    ·               Include output of running processes by launching Command Prompt on your Home Server, and typing “tasklist > tasklist.txt” and attach the tasklist.txt file which will most likely be stored at “C:\Documents and Settings\Administrator”

     

    Windows Home Server Connector:

     

    ·         Under certain conditions, the download of the necessary files to update the Home Server Connector may take up to an hour or more. If you experience this issue, a workaround is presented below, and we ask that you please file a bug report with the requested information.

     

    Workaround:

     

    o   Run Setup.exe from \\<servername>\Software\Home Server Connector Software

     

    What to do when filing a bug:

     

    ·         Include the answers to the following questions in your bug report:

    o   Is your router connected to the internet?

    o   Is your computer a member of a domain?

    o   Has this computer ever been a member of a corporate network?

    o   A snapshot of the IE proxy settings. Open IE, click on Tools/Internet Options/Connections/LAN Settings. Attach a screenshot of the proxy settings.

    o   Attempt to browse to http://<servername>:55000/ Was there any noticeable delay?

    ·         Upload Error Reporting (TALQ) logs by running Toolkit (insert link to bug report doc on Connect)

     

    ·         Under certain conditions when a health notification is displayed, your Tray Icon may appear hung and not recover from the hang. If you experience this issue, a workaround is presented below, and we ask that you please file a bug report with the requested information.

     

    Workaround:

     

    ·         Fix the problem that caused the Tray to issue a notification: Look at the Health dialog in the WHS Console for information on how to fix the actual problem.

    ·         Close the WHS Console.

    ·         From Task Manager, go to the Processes tab, and kill WHSTrayApp.exe

    What to do when filing a bug:

    ·         Include the answers to the following questions in your bug report:

    o   Did you see an error bubble popup from the Tray? What did it say?

    o   What was the storage capacity of your home server? How many drives?

    o   How much free space did you have on your primary hard drive?

    o   Was your primary/secondary drive failing?

    o   Any other storage related observations?

    ·         Upload Error Reporting (TALQ) logs by running Toolkit (insert link to bug report doc on Connect)

    Tuesday, June 10, 2008 12:39 AM
    Moderator