Donnerstag, 3. September 2009 17:51Not sure if this is specific to PP3 beta or if it's an independant issue. Has anyone seen this? Know how to resolve?
From the HomeServerConsole log:
090831.210252.9721: Error: OperatingSystemName key does not exist. This is expected during PP1 to PP2 upgrade. System.IO.IOException: The specified registry key does not exist.
at Microsoft.Win32.RegistryKey.Win32Error(Int32 errorCode, String str)
at Microsoft.Win32.RegistryKey.GetValueKind(String name)
at Microsoft.HomeServer.Transport.PartnerInfo.GetValue(String key, RegistryValueKind kind, String path)
at Microsoft.HomeServer.Transport.PartnerInfo.GetPartnerValue(String key, RegistryValueKind kind)
at Microsoft.HomeServer.Transport.PartnerInfo.StringValue(String key)
EDIT: If this doesn't seem specific to PP3 could someone move it over to the general forum?
Freitag, 4. September 2009 21:02Mmm - can you confirm that Powerpack 2 was installed before the beta? Did you have any issues during the PP2 install process?
Dienstag, 8. September 2009 20:28Sorry for the lag in reply. These errors did not show up in the console logs after PP2 was installed. PP2 was installed 3/26/2009 and I saved off an archive of my WHS logs through 3/29/2009. The error does not occur in any of the archived console logs. The oldest console log in the WHS logs directory is 8/22/2009 (I'm assuming they're getting pruned.)
I went back through the logs currently in the WHS logs directory and all of the HomeServerConsole.<date/timestamp>.log files currently there contain this error. Unfortunately these errors aren't logged in the WHS or Application event logs. Sorry, not a lot to go on.
PP3 Beta 1 was installed on 8/8/2009 if that matters.
Dienstag, 8. September 2009 21:53ModeratorTom, could you submit a bug on Connect?
I'm not on the WHS team, I just post a lot. :)
- Als Antwort vorgeschlagen kariya21MVP, Moderator Mittwoch, 9. September 2009 01:59
Mittwoch, 9. September 2009 00:23Sure. Bug submitted .
I would have done that last week when I posted but I wasn't able to because of an unrelated issue. In case anyone's interested, Talq fails to roll the logs up if the total log size is too big. Too big includes having enough space for 2x the WHS logs (because talq makes a copy of all of the logs along with some other info at C:\Documents and Settings\Administrator\Local Settings\Temp\TalqLogs and then cabs them up to send to Microsoft. In my case the qsm logs were over 10 GB for the eight days worth of logs kept due to an issue with MS logging levels being overly verbose and not being configurable for certain data queries. I initially tried compressing the logs directory and the Temp directory so the drive didn't run out of space (20 GB fills up fast when you try to make two copies of 10GB of logs) :P When that didn't work I archived off most of the qsm logs and got the total down to just over 1 GB.
[/ ok, I'm done]