Access Denied

Solar2D Win32 Desktop
#1

While I did get an app built and running, I also ran into a problem.

The Problem

When building any app for Windows, I get an ‘access denied’ error when trying to save the final project (Project Path) anywhere except to C:.*.

i.e. Saving to drives other than C:\ doesn’t seem to work.

The Setup

  • Corona build -  2015.2656 (typoed in initial post)
  • OS - Windows 7 x64 Ultimate
  • Virus Scanner (Avast Pro) - Disabled for test
  • Drives:
    • C:* - Can save pretty much anywhere here.
    • G:* - Game drive - Access denied.
    • X:* - Primary data drive - Access denied.
    • S:* - Data shadow - Access denied.

The point of listing the other drives above, was to demonstrate that I did try multiple no C:\ drives to be sure it wasn’t just a fluke with ‘X:’

Here is an excerpt of the log output:

Extracting Resources\widget\_theme\_onOff\_mask\_android\_holo.png Extracting Resources\widget\_theme\_pickerWheel\_mask.png Extracting vccorlib120.dll Everything is Ok Files: 25 Size: 5779564 Compressed: 2933293 Failed to copy built application to destination directory: g:\dg.Win32 Reason: Access is denied.
#2

Hi roaminggamer,

There is a known issue where if you have the build directory window open in Explorer when trying to build it can, in some instances, give you an error.

Can you try it again with that in mind and let us know of the results?

Regards,

Michael

#3

@Michael,

I tried building again, after ensuring that Windows explorer was not open to the folder (or even drive) I was building to.

Same results.

Please note: My working environment is complex and I keep it up-and-running for long periods (I’m in one now).

I’ll try this experiment again in other scenarios when I next reboot and give additional feedback then.  Things I’ll try:

  • Safe Mode - Will take all my tools and environment mods out of the equation.
  • Clean Boot - Just in case something else is going on.
  • Normal Boot minus some tools that touch disks and external connections on (I share parts of my data drive with my other dev machines.)

Meanwhile, thanks for the response!

#4

This issue will be fixed in daily build #2657.

We’ve modified the Win32 build system to build to another drive/volume much more reliably.

It will also detect if you have any files locked in the destination directory and display a nice helpful message on how to resolve it as well.  This handles the case Michael mentioned up above where Windows Explorer can be a bit overly aggressive about keeping a file/directory lock on the directory that you’re trying to overwrite.

Thanks for bringing this issue up Ed!

#5

Thanks guys.  

I just downloaded and tested 2657.  I can confirm, that it works like a charm now.

#6

Hi roaminggamer,

There is a known issue where if you have the build directory window open in Explorer when trying to build it can, in some instances, give you an error.

Can you try it again with that in mind and let us know of the results?

Regards,

Michael

#7

@Michael,

I tried building again, after ensuring that Windows explorer was not open to the folder (or even drive) I was building to.

Same results.

Please note: My working environment is complex and I keep it up-and-running for long periods (I’m in one now).

I’ll try this experiment again in other scenarios when I next reboot and give additional feedback then.  Things I’ll try:

  • Safe Mode - Will take all my tools and environment mods out of the equation.
  • Clean Boot - Just in case something else is going on.
  • Normal Boot minus some tools that touch disks and external connections on (I share parts of my data drive with my other dev machines.)

Meanwhile, thanks for the response!

#8

This issue will be fixed in daily build #2657.

We’ve modified the Win32 build system to build to another drive/volume much more reliably.

It will also detect if you have any files locked in the destination directory and display a nice helpful message on how to resolve it as well.  This handles the case Michael mentioned up above where Windows Explorer can be a bit overly aggressive about keeping a file/directory lock on the directory that you’re trying to overwrite.

Thanks for bringing this issue up Ed!

#9

Thanks guys.  

I just downloaded and tested 2657.  I can confirm, that it works like a charm now.