Hi,
Please run system file checker (sfc /scannow) first to check the result. For the detailed information, please refer to the following Microsoft KB article:
How to use the System File Checker tool to troubleshoot missing or corrupted system files on Windows Vista or on Windows 7
http://support.microsoft.com/kb/929833
If the issue persists, please also try to perform an In-Place upgrade to repair the installation.
Regards,
Not sure what triggered this error for Tomi, but I know EXACTLY how to bring this message on in my case. It is as simple as renaming the machine - either using the Server Manager -> Local Server option OR through a series of NETDOM commands. Either one will make server manager post the error after the reboot from renaming. I am guessing this is already known, but it causes the Storage role to now show up in the server manager window.
The only issue found and repaired by the SFC for me was:
Repairing corrupted file [ml:520{260},l:28{14}]"\??\C:\sources"\[l:30{15}]"RdsUpgCheck.dll" from store
And the problem persisted after that, even after reboot. Performed an in-place upgrade and same results the error is displayed. Event log is not registering anything either for this.
Any additional suggestions?
I'm having the same problems using the new 8400 build. Also after the server rename and also not seeing the storage role.
Can't find any logs just yet regarding this.
Oddly enough this "resolved" the issue for me as well. Guess they will just have to document that renaming servers needs to be done twice in order for it to stick :) Thanks for the post!
EDIT: After playing with this more, I do not think it is the second rename that made it work. Oddly I think it is the presence of the number that makes it work. I built a new machine from scratch and instead of naming it "server" as I had been for testing named it "win-00". This did not have the error pop up after reboot as ALL previous installs had. Not going to play any further as there are LOTS of other areas I want to explore and this one is working with that caveat.
- Edited by Excel.Net - Excellent Computers Friday, June 01, 2012 12:55 PM More details found...
Hmm .. I just renamed it back to SERVER and I'm getting the same errors as before.
It would seem the hostname "server" pisses something off.
Hi,
The issue for "File and Storage services" node not available when machine named as SERVER is already being tracked for Windows Server 2012. For now, rename machine as "Server1" or "Server2" (as mentioned above in the post).
Thx
Manish
- Proposed as answer by freggel Sunday, June 03, 2012 3:48 AM
- Marked as answer by Arthur_LiMicrosoft contingent staff, Moderator Monday, June 04, 2012 3:01 AM
Hi,
as soon as i join the Server to a Domain the error occur
when i put it back to a Workgroup the error disapears
a solution would be nice :)
I know this topic is very outdated but curious if there has been any updates?
I have a server that isn't named "server" which has been joined to the domain and I also get this error.