VMware Cloud Community
Panzer
Enthusiast
Enthusiast
Jump to solution

Cannot access image after upgrading VC

After upgrading VC from 2.0 to 2.5 i can no longer access my images from a file share. Error message "please specify a valid image file"

Reply
0 Kudos
1 Solution

Accepted Solutions
SomeClown
Enthusiast
Enthusiast
Jump to solution

Nevermind... figured it out. For some reason the new version of VirtualCenter doesn't like long .iso names (like the ones Microsoft uses if you have an EA or Technet account). I just renamed my .iso images to shorter names and everything is great. Though I still think this is a @#$@# thing to just "toss in" on an upgrade like this... especially since I now won't know what I've downloaded as matched against the official .iso names from Microsoft.

View solution in original post

Reply
0 Kudos
16 Replies
SomeClown
Enthusiast
Enthusiast
Jump to solution

Bump

Same thing is happening to me. I keep my .ISO install images out on a network share, and while I can still see them, I get this error any time I try to connect the CD/DVD device. Worked repeatedly and often in 2.0.

Reply
0 Kudos
SomeClown
Enthusiast
Enthusiast
Jump to solution

Nevermind... figured it out. For some reason the new version of VirtualCenter doesn't like long .iso names (like the ones Microsoft uses if you have an EA or Technet account). I just renamed my .iso images to shorter names and everything is great. Though I still think this is a @#$@# thing to just "toss in" on an upgrade like this... especially since I now won't know what I've downloaded as matched against the official .iso names from Microsoft.

Reply
0 Kudos
williamarrata
Expert
Expert
Jump to solution

Just for kicks, how long were your names???

Hope that helped. Smiley Happy

Hope that helped. :slightly_smiling_face:
Reply
0 Kudos
SomeClown
Enthusiast
Enthusiast
Jump to solution

Just the standard Microsoft .iso names that you get when you download licensed software from their licensing portal... something like so:

SW_DVD5_Office_SharePoint_Server_2007_W32_English_-2_1_PA_BP_ISO_Onl_X13-38800.ISO

It's not even so much that their may now be a limitation, it's just that I didn't find anything in the documentation referring to this, and since all of the Microsoft .iso files come down this way, now I have to come up with my own renaming scheme... just another bit of work I have to do to make VirtualCenter happy all of a sudden.

Reply
0 Kudos
RParker
Immortal
Immortal
Jump to solution

you konw an ISO image is just a file. Rename it to something shorter, yet descriptive like:

OfficeSPPS_2007.ISO

Reply
0 Kudos
SomeClown
Enthusiast
Enthusiast
Jump to solution

Yes, yes I know... as evidenced by my comments to that effect earlier in the thread. My irritation at this point is with the lack of documentation on the change, and with the fact that I have to do the renaming in the first place because of some (apparently) arbitrarily imposed file-name-size limit in the new version of VirtualCenter.

Reply
0 Kudos
RParker
Immortal
Immortal
Jump to solution

Yeah, I see it now.. Apparently I didn't see "renaming scheme", it was clear you would rename it.. haha..Sorry.

I see what you mean now, the image isn't mountable in a VM or it doesn't find the file at all?

Reply
0 Kudos
Panzer
Enthusiast
Enthusiast
Jump to solution

Thanks for your help guys!

To RParker: It isn't mountable, you get "pleace specify a valid image file".

Reply
0 Kudos
carne
Contributor
Contributor
Jump to solution

Use lowercase on the file extension, then it work.

Reply
0 Kudos
Syik
Contributor
Contributor
Jump to solution

Yes, I got the same problem with the extension of CAPITAL LETTERS, that is "myimage.ISO"

Simply rename it to "myimage.iso" and it works.

Ain't that a bug????

Reply
0 Kudos
cmbuechler
Contributor
Contributor
Jump to solution

Yeah it doesn't have anything to do with file name length, it's the extension in all caps, like you get from the MS Licensing site downloads. Renaming to .iso rather than .ISO fixes the problem, even leaving the 64 character filename MS uses.

Reply
0 Kudos
arabisoft
Contributor
Contributor
Jump to solution

Definitely a bug. Had the same issue and it only worked by connecting directly to an iso, and ofcourse I had to rename the .ISO to .iso for it to work with it. I guess some lame developer is doing a case sensitive comparison on the extension. The strange this though, is that if I mount that iso with MagicISO and have VC connect to it, it won't recognize it during the boot at all. Thank you guys for this.

Reply
0 Kudos
kid23lopez
Contributor
Contributor
Jump to solution

ESX Server is Linux based and extensions are case sensitive. .ISO is not the same as .iso

The VI Client is not mounting the ISO but the ESX actually is. In this case it's looking for .iso instead of both ISO or iso

Reply
0 Kudos
arabisoft
Contributor
Contributor
Jump to solution

Still think it is a bug. Linux may differentiate between .iso and .ISO but if I'm writing a software on linux I would keep that in mind. It's not like .ISO is a different type of file. In any case, if people are running into this issue then it needs fixing. They should either make the esx piece accept any form of .iso or make the windows client pass the file as .iso so it will match their ESX expectations.

Reply
0 Kudos
cmbuechler
Contributor
Contributor
Jump to solution

Uh, yes, the service console is indeed Linux based. But for one this is in the Windows client which has nothing whatsoever to do with any files or file names on any *nix-ish OS, and two even if the file extensions were caps sensitive, it shouldn't differentiate between iso, ISO, IsO, isO, whatever. The VI client doesn't even let you get to the point where it's mounting the device on ESX. Definitely a bug.

Reply
0 Kudos
kid23lopez
Contributor
Contributor
Jump to solution

The bug is in the programming not how ESX is handling it. Doesn't matter what OS it's on. When we develop utitlies for cross platforms we make sure we code for various platforms. Never said it wasn't a bug on the client side. Wether you like it or not, in ESX, ISO is completely different of iso. You or anyone else cant' change that fact, they simply need to fix this bug on the client.

Reply
0 Kudos