Error Id 1604 Scvmm
Contents |
2012 (TFS2012) Lab Management with System Center Virtual Machine Manager 2012 (SCVMM2012). I ran into this bizarre problem where I could log in to SCVMM from the SCVMM console on the local machine but if
Scvmm 2012 Error Id 1604
I tried to access it from a different machine, I’d get an error. Specifically, virtual machine manager 1604 Error ID 1604 – “You cannot access the VMM management server servername.” That message would ordinarily *SCREAM* permission problems if it weren’t for the fact that I could access SCVMM when I’m logged on to my SCVMM server. Along the way, I found a blog post that hinted that there is some weird behavior when you log on to SCVMM using a username in the “domain\username” format vs. just “username”. Here’s the link to that blog post: http://www.itguy.gr/2011/12/anoying-you-cannot-access-vmm.html Conveniently enough, SCVMM’s administrator console has a nice feature that lets you choose how SCVMM gets your credentials. As you can see in the screenshot below, you can either pick “Use current Microsoft session identity” or “Specify credentials”. If you choose “Use current Microsoft session identity”, you don’t have to type a username/password and your current login is just passed up to the server. Think “single sign on” (aka. SSO). The second option lets you type in your username and password directly. Sure enough, if I chose “Specify credentials” and then typed in “benday\administrator” I couldn’t log in but if I typed in just “administrator” then I was fine. CRAZY! I spent a number of hours beating my head against the wall on this one and along the way, I kept reading about people having random problems with Kerberos, Service Principal Names (SPNs), and running SCVMM under a domain account vs. Local System account. When I installed SCVMM, I used a domain account (see screenshot below) so I decided to try uninstalling and re-installing. This time when I installed, I used Local System account for the Virtual Machine Manager Service Account. This fixed my problem!!! And now when I get to the TFS Admin Console and go to the Lab Management Settings page, setting up SCVMM Server Name (FQDN) value actually passes validation! So, the moral of the story is to run SCVMM 2012 using the Local System account if you want a smooth install. -Ben -- Looking to mov
1604 ★★★★★★★★★★★★★★★ Michael Michael [Apprenda]July 21, 20081 0 0 0 After installation, if you try to open the VMM administrator console and you get the error below, you can follow these stepsto troubleshoot and fix the issue: You cannot access Virtual Machine Manager server
a member of a valid user role and then try the operation again." 1:55 PM | Posted by Andreas Panagopoulos | | Seen this before?? I just introduced SCVMM 2012 RC to my Hyper-V cluster lab environment. Set it up on a http://www.itguy.gr/2011/12/anoying-you-cannot-access-vmm.html VM, it immediately saw my hosts, and I was able to manage VMs, fabrics, libraries, http://serverfault.com/questions/413379/vmm-error-1604-cannot-access-virtual-machine-manager everything worked perfecly! I then installed the VMM console on my PC, typed the VMM server FQDN and port, and used "current Microsoft Windows session identity" credentials. Clicked connect and boom, got the above error window. The account I was currently logged on not only already was a member of the Administrator User Role, it's a bleedin' Domain Admin user. So error id I went to "Specify Credentials" and typed it myself again as per the instructions: contoso\domainuser. Same error. I poured all over the Internet checked potential domain credential issues, kerveros key status, potential SCP issues, ran queries on the VirtualManagerDB database, ran vmmtrace, you name it. Nothing worked. Now I could very well fudge it and just work on the SCVMM virtual machine, but I just cannot let such things go, it would just kill me!! Then error id 1604 I gave the Self-Service Portal a go (same account) and it popped up a message about the user not being a member of a self-service user profile type: "Unable to log on to the Self-Service Portal because the specified account is not a member of a self-service user role. Please try again using a self-service user account." Fair enough, I created the user role and tried again... same error message! Then I remembered a silly bug with SCVMM 2008 and R2: if you typed the account as domain\username you got an error message, but if you just typed the account, no domain name it worked. You'd think after 3 editions of the product it would have been fixed... Tried it on the self service portal, and bingo!! Tried it on the VMM console, bingo again!! So there you have it: instead of typing domain\username and password, just type username and password. Labels:Virtualization Email This BlogThis! Share to Twitter Share to Facebook 24 comments: Stephan van der PlasApril 26, 2012 at 2:39 PMAnd still in the RTM version this bug exists. Problem is that users in a different domain than where the server lives cannot connect remotely!ReplyDeleteAndreas PanagopoulosApril 26, 2012 at 3:59 PMJesus Christ, you'd think that after 4 years and 3 versions they'd get round to fixing it...ReplyDeleteLars MortensenMay 22, 2012 at 9:20 AMThanks..... Really annoying bug....ReplyDeleteAnonym
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top VMM Error: 1604 Cannot Access Virtual Machine Manager up vote 2 down vote favorite I keep getting the error: You cannot access Virtual Machine Manager server localhost. Cantact the Virtual Machine Manager administrator to verify that your account is a member of a valid user role and then try the operation again ID: 1604 My setup: Win Server 2008 R2 (Domain Controller) Hyper-V installed System Center Virtual Machine Manager 2008 R2 installed I am logged in under Domain\Administrator, yet it still says I have no access to VMM. Administrator is a member of: Administrators/Domain Admins/Domain Users/Enterprise Admins/Group Policy Creator Owners/Schema Admins/Virtual Machine Manager Servers. Any ideas? Thanks. ps. this is a test machine that I have set up to get familiar/learn about VMM and Hyper-V authentication scvmm share|improve this question asked Aug 1 '12 at 18:31 user130622 112 Did you by any chance change the admin password because of all the root cause mine is caused due to this as there is no other way to explain it –Anurag Shetti Mar 16 '13 at 5:12 add a comment| active oldest votes Know someone who can answer? Share a link to this question via email, Google+, Twitter, or Facebook. Your Answer draft saved draft discarded Sign up or log in Sign up