VMware Communities
HumptyDumpty
Contributor
Contributor
Jump to solution

This vitual machines policies are too old ..

Hello,

my problem is precisely discribed by this KB issue:

kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=2034362&sliceId=1&docTypeID=DT_KB_1_1&dialogID=453338166&stateId=1%200%20453344210

When I want to start a Win 2000 Pro machine I get this message:

This virtual machine's policies are too old to be run by this version of VMware. Contact your system administrator

I did what the KB told: I found 3 lines policy.vm. ... and removed them.

There was also a file host.vmpl which I rename host.vmpl.old.

The message still remains when I want to start this vm.

I think that my vm is an ACE machine and was created with Workstation 7.x -

there is an empty folder 'ACE Ressources' and 2 small files ace.dat and aceMaster.dat.

Today before I upgraded to Workstation 9 I had no problems to work with this machine.

So what can I do?

Thanks

Klaus (H.D.)

0 Kudos
1 Solution

Accepted Solutions
continuum
Immortal
Immortal
Jump to solution

Looks like you did not rename the vmpl file - try that first


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

View solution in original post

0 Kudos
4 Replies
continuum
Immortal
Immortal
Jump to solution

If you need to run ACE VMs the answer is very simple : do not use Workstation 9.

Anyway - please post a directory listing of the VM and attach the vmx-file if it is not encrypted


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

HumptyDumpty
Contributor
Contributor
Jump to solution

Hello Ulli,

very good idea not to use Workstation 9.

Well, here's the file listing

11.10.2012  09:31    <DIR>          .
11.10.2012  09:31    <DIR>          ..
10.10.2012  16:56    <DIR>          ACE Resources
19.06.2009  11:42               431 ace.dat
19.06.2009  11:42               769 aceMaster.dat
27.03.2012  17:19    <DIR>          caches
19.06.2009  11:42             1.416 host.vmpl.old
12.08.2012  11:43           152.155 vmware-0.log
19.07.2012  17:14           162.233 vmware-1.log
18.07.2012  14:35           216.515 vmware-2.log
10.10.2012  14:17           180.070 vmware.log
10.10.2012  14:17             8.684 Win 2000 Pro.nvram
19.06.2009  11:42             9.153 Win 2000 Pro.vmpl
03.02.2009  12:57                 0 Win 2000 Pro.vmsd
10.10.2012  16:44             3.529 Win 2000 Pro.vmx
20.06.2012  07:54             2.939 Win 2000 Pro.vmxf
10.10.2012  14:17           524.288 Windows 2000 Professional-1-cl2-s001.vmdk
10.10.2012  14:17     2.146.369.536 Windows 2000 Professional-1-cl2-s002.vmdk
10.10.2012  14:17     2.146.762.752 Windows 2000 Professional-1-cl2-s003.vmdk
10.10.2012  14:17     2.119.565.312 Windows 2000 Professional-1-cl2-s004.vmdk
10.10.2012  14:17     2.145.320.960 Windows 2000 Professional-1-cl2-s005.vmdk
10.10.2012  14:17     1.453.522.944 Windows 2000 Professional-1-cl2-s006.vmdk
10.10.2012  14:17         2.621.440 Windows 2000 Professional-1-cl2-s007.vmdk
10.10.2012  14:17       232.849.408 Windows 2000 Professional-1-cl2-s008.vmdk
10.10.2012  14:17           131.072 Windows 2000 Professional-1-cl2-s009.vmdk
10.10.2012  14:10             1.042 Windows 2000 Professional-1-cl2.vmdk
10.10.2012  14:17     9.578.938.368 Windows 2000 Professional-cl2.vmdk

The folder 'ACE Resources' is empty.

I have no idea what an ACE vm does different from a non ACE vm.

I'm sure this machine was created with Workstaion 6.x

Klaus

0 Kudos
continuum
Immortal
Immortal
Jump to solution

Looks like you did not rename the vmpl file - try that first


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

0 Kudos
HumptyDumpty
Contributor
Contributor
Jump to solution

Thanks Ulli,

obviously I only saw  the host.vmpl file.

Now the machine runs nicely.

Klaus

0 Kudos