VMware Communities
rjzcap1
Contributor
Contributor
Jump to solution

can't suspend vmware play anymore

Attached is a log.

Was on and off before with it now wont do it at all.

I have the latest version.

Reply
0 Kudos
1 Solution

Accepted Solutions
bluefirestorm
Champion
Champion
Jump to solution

Just a suspicion, maybe the filename is hitting some limit in filename length.

2018-02-07T12:57:03.519-05:00| vcpu-0| I125: OBJLIB-FILEBE : Error creating file '.\cloudready-free-64bit-59.3.37 (2)-6b928e8d.vmss': 7 (Insufficient permission to access the file).

If that full name path is expanded to where the vmss should be stored

C:\Users\rzmuda.HOKIES\Documents\Virtual Machines\cloudready-free-64bit-59.3.37 (2)\cloudready-free-64bit-59.3.37 (2)-6b928e8d.vmss

which is 131 characters.

Windows filenames are limited to 260 characters but can be longer in Windows 10 Anniversary Update but is not enabled by default. So if it is some file name limit, it might be something internal to how VMware Workstation/Player software allocate a buffer for filenames.

You could try renaming the VM or the VM folder to reduce the number of characters. Taking away the "-59.3.37 (2)" will reduce 24 characters (12 on folder + 12 on vmss name).

View solution in original post

Reply
0 Kudos
6 Replies
wila
Immortal
Immortal
Jump to solution

Hi,

From the log:

2018-02-07T12:57:03.519-05:00| vcpu-0| I125: OBJLIB-FILEBE : Error creating file '.\cloudready-free-64bit-59.3.37 (2)-6b928e8d.vmss': 7 (Insufficient permission to access the file).

2018-02-07T12:57:03.519-05:00| vcpu-0| I125: OBJLIB-LIB: Could not create object '.\cloudready-free-64bit-59.3.37 (2)-6b928e8d.vmss': Insufficient permission to access the file (70002)

You don't have the required file access permissions to suspend.

Check user/owner of the file and folder where the VM lives.

Make sure you can create/edit files there

If you still encounter issues then check the hardware, although the error really suggests that it is a permissions error, so that would be my guess (not the hardware)

--

Wil

| Author of Vimalin. The virtual machine Backup app for VMware Fusion, VMware Workstation and Player |
| More info at vimalin.com | Twitter @wilva
Reply
0 Kudos
rjzcap1
Contributor
Contributor
Jump to solution

Checked permissions and they are ok. It's back to being speardic again./

What else could it be?

Could it be the HD going bad or something else?

Reply
0 Kudos
wila
Immortal
Immortal
Jump to solution

Hi,

Issues like this that happen sporadic, do indeed suggest that it is a hard disk that is starting to fail.

--

Wil

| Author of Vimalin. The virtual machine Backup app for VMware Fusion, VMware Workstation and Player |
| More info at vimalin.com | Twitter @wilva
Reply
0 Kudos
rjzcap1
Contributor
Contributor
Jump to solution

Ran a complete surface scan and other hardware checks. Everything is ok.

What else could it be. Ity might look like permissions but, its sporadic.

Reply
0 Kudos
bluefirestorm
Champion
Champion
Jump to solution

Just a suspicion, maybe the filename is hitting some limit in filename length.

2018-02-07T12:57:03.519-05:00| vcpu-0| I125: OBJLIB-FILEBE : Error creating file '.\cloudready-free-64bit-59.3.37 (2)-6b928e8d.vmss': 7 (Insufficient permission to access the file).

If that full name path is expanded to where the vmss should be stored

C:\Users\rzmuda.HOKIES\Documents\Virtual Machines\cloudready-free-64bit-59.3.37 (2)\cloudready-free-64bit-59.3.37 (2)-6b928e8d.vmss

which is 131 characters.

Windows filenames are limited to 260 characters but can be longer in Windows 10 Anniversary Update but is not enabled by default. So if it is some file name limit, it might be something internal to how VMware Workstation/Player software allocate a buffer for filenames.

You could try renaming the VM or the VM folder to reduce the number of characters. Taking away the "-59.3.37 (2)" will reduce 24 characters (12 on folder + 12 on vmss name).

Reply
0 Kudos
rjzcap1
Contributor
Contributor
Jump to solution

Moved it and so far it's been good for 1 week.

Reply
0 Kudos