Dear Team,

Using windows 11 Pro computer to upgrade ADAGIO modules.

In April used same machine to upgrade, slice through like Cheese... no issues.

My Apps were installed on K Drive and we shortcut and presently work on K Drive.

Today, download and begin upgrade first module is ledger after input codes doing Standard Install I get this error (Destination Selection Error )

Message= The following chosen folder is not write-enabled
(K:\Softrak\Ledger)
Please choose again

I spoke to network admin he made sure all is OK on SERVER - ( Still No go)

I then took a look at K:\Softrak folder using File Explorer O/s (Windows 11 Pro)

I see the following attributes (see attached file) Its an international firm, with off shore administrator, so I can not go fudging around with local computer...


Anyone else encountered a similar issue.

Thanks in advance..

Edward

The user profile no longer has full rights to the folder. Their IT will have to change it back for that user if you want to install updates.

Sending your post to Network Admin - right now.. will keep you posted..

The Windows 11 (Growth Pains Continues)

One Love
Edward

Just to update this post ...

Edward contacted me directly and I advised him that I've seen that message when using the newer Adagio installs and/or installing on newer OSes when using mapped or substituted drives. I advised him to use the UNC equivalent for the install path and all was well.

The mapped drives still run the apps fine but have issues with the Adagio Installs on some machines and giving misleading messages like the one above. Why I have no idea but as soon as I have an issue with the mapped/substituted drive during an install, I just use the UNC path and so far so good. That is, of course, assuming that the network/folder rights are actually OK ... but especially in the case of upgrading where the site has been happily using (which also requires write access) Adagio then in most cases the rights would not have suddenly changed when you go to upgrade - not sure why the screen shot seemed to suggest that files in the folder were read-only.

Regards, Pete

The install will automatically "elevate" the security to Administrator and that error message usually indicates that the administrator doesn't have that folder mapped. That's why the UNC path works in that case. Because it doesn't require a drive mapping.

We usually map the drive on a batch file or the command line Run as Administrator (using NET USE). Even though UNC paths work too, the system is slower than running on mapped drives.

If this didn't happen before might be because the mapped drive was already mapped for the Administrator or the IT has changed the drive mapping to Group Policy.