Having issues installing the WCF Extensions on Visual Studio 2005 when you have .NET 3.0 SP1 installed? Getting an error message the looks something like the following?
Setup has detected that a prerequisite is missing. To use Visual Studio 2005 extensions for .NET Framework 3.0 (WCF & WPF), November 2006 CTP you must have the .NET Framework 3.0 runtime installed. Please install the .NET Framework 3.0 runtime and restart setup.
Well, instead of just installing the application by double clicking on the MSI, run it the following way. This ends up bypassing the prereq checks and it installs successfully. Yay to broken installers!
msiexec /i vsextwfx.msi WRC_INSTALLED_OVERRIDE=1
See the second update for the correct way of setting this up :)
You may be like me, and have a test lab running VI3. You may also only be running Microsoft VMs for whatever reason. I happen to be because that’s all I deal with as I work for a MS Consulting company. Anyways, whenever I wanted to create a new machine I needed to have the ISO copied out to the ESX storage device. This was always a pain because I’d have to use WinSCP or Filezilla to copy it from a host virtual machine to the storage device. Plus there was the fact that I was now using 2x the space on the storage device because it’s accessible to ESX and it’s stored in a VM. Lame.
With VI3 you can use NFS shares as storage devices. Downside is, is that by default Windows only uses CIFS (or SMB) sharing. However, with Windows 2003 R2 (you may be able to do it in Win2k3 too) you can install the Unix NFS tools which allows for the creation of NFS shares.
From the Windows machine you want the NFS share(s) located on, you need to open Add/Remove Programs from the Control Panel and then Add the following Windows components. Under Other Network File and Print Services select to install all of the Microsoft Services for NFS. I don’t think if you need all of them, but it’s working with them all (feel free to leave feedback if you play).
After you install those, it will require a reboot. Once you’re back up, open up the Microsoft Services for NFS in the Administrator Tools. Right click on the root (Microsoft Services for NFS) and select the user name mapping you want. I set mine to AD lookup, but I’m using anonymous read only access on the share anyways.
If the CIFS share has already been created, you will need to create the NFS share from the command line. This can be done with the following command: nfsshare -o anon=yes
=drive:path. Obviously replace
with the name you like and drive:path with the location for the share.
If the CIFS share hasn’t already been created, then you will see a NFS Sharing tab when you attempt to create the share.
Once the share has been created, within your VirtualCenter client (or host based VI Client), select the host, go to configuration tab, and then Storage (SCSI, SAN, and NFS). Select Add Storage and select the Network File System option. Enter the info for the server you just set this up on and the folder (/
). Now you have a mounted storage device for your share. Yay!
As mentioned before, this NFS mount point can be a virtual machine on the host. I haven’t restarted the host yet, so I’m not sure how nicely it plays with that though.
Resources used for this:
http://levelsofdetail.kendeeter.com/2007/01/setting_up_an_nfs_server_on_wi.html
http://support.microsoft.com/kb/324089
**Update**
Ugh, so just doing the above doesn’t work. At least it didn’t list the contents of the iso directory. No good. Further research comes up with one possible solution, but it’s ugly.
Add anonymous login read access to the share and ntfs permissions on the share. This seems to work, but I’m not really a fan of it. For some reason, user mapping doesn’t seem to be working. You should be able to do user mapping by grabbing the /etc/passwd and /etc/group files from your VI3 host and then importing them into the Microsoft Services for NFS User Name Mapping section (right click and define the location for these two files).
I’ve mapped the local admin to the root account. I get no love though as soon as I disable anonymous access on the NFS share. Boo. What really makes me angry is that I want to host templates on this Windows NFS share. That would require me to enable read/write access to the anonymous user. Needless to say, something I’m really not comfortable with. Maybe I can fix this stupid user mapping issue, and then I won’t have to worry.
Oh yeah, be sure to enable the NFS client firewall rule on your host…
**Update #2** This is the way to get this setup
Alright, I’m retarded as to why I couldn’t get this figured out. The real steps to get this going:
Well, it was a day late, but I got my 7.5 mile run in! I ran it on Saturday and then yesterday put in a small 1.5 with Yow-Yow. Good times. Now I’m off to the gym…
Holy crap. Having the right shoes can definitely make a huge difference. I normally just use my trail running shoes for various excercise related activities. However, since I’m running in a relay, and by “a” relay I mean “the” relay, out in SFO (feel free to donate, it’s tax deductible!), I figured I should go a little bit more professional, especially since I normally have a hard time running long distances on pavement.
Well, I bought the shoes on Monday, a pair of Saucony ProGrid Triumph 5’s, and this morning was the first time I was able to try them out. Now, I’m not sure if it’s because I’ve been running a lot with hills on the treadmill and this was the first time this year outside or the new shoes, but I was able to go Next loop will be up to Addison to make it 7.5 miles. Hopefully I’ll do that tomorrow or Friday now that I’ve broken in the shoes. Plus, now that I know that 5 miles is not that big a deal, I’m going to start running to the gym and back. What’s really wierd is that I’m actually excited about this. I thought I wasn’t going to be in that great of shape for this relay, but now I’m not too concerned. I just want to be able to hit 10 miles or more prior to shipping out, since I’m not doing any hilly stuff.
Make sure your Database Access account is an admin on the central administration server, otherwise you’ll get access denied errors when trying to create new web applications. This is because the db access account won’t have the ability to edit the metabase. Oh, and this bubble up by MOSS saying that you, the logged in user doesn’t have access, which is completely inaccurate, especially since I was a Farm Administrator. In addition you’ll see the error message listed below in the Application event logs.
Log Name: Application
Source: ASP.NET 2.0.50727.0
Date: 3/18/2008 10:58:42 AM
Event ID: 1309
Task Category: Web Event
Level: Warning
Keywords: Classic
User: N/A
Computer:
Description:
Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 3/18/2008 10:58:42 AM
Event time (UTC): 3/18/2008 3:58:42 PM
Event ID: c59d97a1bbf8405cba1d837292259be4
Event sequence: 4767
Event occurrence: 8
Event detail code: 0
Application information:
Application domain: /LM/W3SVC/236168797/ROOT-1-128503227503346172
Trust level: WSS_Minimal
Application Virtual Path: /
Application Path: C:\inetpub\wwwroot\wss\VirtualDirectories\37466\
Machine name:
Process information:
Process ID: 3720
Process name: w3wp.exe
Account name:
\
Exception information:
Exception type: COMException
Exception message: Access is denied.
Request information:
Request URL: http://
:24055/_admin/extendvs.aspx
Request path: /_admin/extendvs.aspx
User host address: fe80::e48a:75aa:9034:9106WSS_Minimal
User:
\
Is authenticated: True
Authentication Type: NTLM
Thread account name:
\
Thread information:
Thread ID: 9
Thread account name:
\
Is impersonating: False
Stack trace: at Microsoft.SharePoint.Utilities.SPUtility.HandleAccessDenied(Exception ex)
at Microsoft.SharePoint.ApplicationRuntime.SPRequestModule.HandleAccessDenied(Exception ex)
at Microsoft.SharePoint.ApplicationRuntime.BaseApplication.Application_Error(HttpApplication app)
at Microsoft.SharePoint.ApplicationRuntime.SPRequestModule.ErrorAppHandler(Object oSender, EventArgs ea)
at System.Web.HttpApplication.RaiseOnError()
I hate having service accounts admins on boxes.
After trying to install MOSS 2007 on a new Windows 2008 box, I almost went completely bonkers. No place in the installation documentation does it tell you what Role Services need to be installed for MOSS to successfully install and run. Initially MOSS 2007 wouldn’t even install because I didn’t have the IIS6 metabase compatability installed. However, just because it’s installed, doesn’t mean it actually runs. I then started installing additional role services to see if I could get it to work. Needless to say, even after installing all of services, my MOSS installation didn’t work. Turns out you need to have the services installed prior to actually installing MOSS. Otherwise the page will never render, and you’ll get a 5MB binary download instead of the actual application.
However, after I knew what I was looking at (reinstalling MOSS again after all the services were installed), I decided to start whittle down the actual services I need. Instead of doing it by hand, I finally found a website that listed what’s needed. I’d like to give Bill Baer’s site a shoutout as to where I found this information.
Web Server
Common HTTP Features
Static Content
Default Document
Directory Browsing
HTTP Errors
Application Development
ASP.NET
.NET Extensibility
ISAPI Extensions
ISAPI Filters
Health and Diagnostics
HTTP Logging
Logging Tools
Request Monitor
Tracing
Security
Basic Authentication
Windows Authentication
Digest Authentication
Request Filtering
Performance
Static Content Compression
Dynamic Content Compression
Management Tools
IIS Management Console
IIS 6 Management Compatibility
IIS 6 Metabase Compatibility
I really want to upgrade to ESX 3.5. However, I’m not having that much luck with it. I’ve tried 2x now, and have had the exact same experience. So, I do the upgrade from 3.0.2 to 3.5.0. However, after the upgrade, not all of my VMs function. Some of them work just fine. However, others are sitting at the command prompt saying that no OS has been found. It’s weird because the drives are attached and recognized, but it doesn’t like to boot from them. It’s like it can’t find the MBR.
Things I’ve tried to fix this:
I really don’t know what to do at this point. I know that I can downgrade again to 3.0.2 and it will work fine. The machines will boot right up without issues. However, to downgrade, that means I have to recreate all of my Virtual Machines again. Not completely awful, but time consuming. I may try to do a full install instead of any upgrade too, see if that works. Any other ideas?
I’d really like to move to 3.5 as it has some nice features. Plus I’ll be sitting the VCP class soon, which will be on 3.5.