Addsum web site and general info

Postings here will focus mainly on Advanced Accounting software updates, tips, and related topics. They will also include general comments relating to troubleshooting PC/Windows/network problems and may also include reference to our other software products and projects including any of our various utilities, or to the TAS Premier programming language. We considered setting up separate blogs for different topics so that users/others could subscribe to topics mostly aligned with their interests, but decided that it would be better to keep things simple since some topics cross over into others. We would nonetheless welcome your feedback/input in this regard. Our web site URL is www.addsuminc.com. Call us at 800-648-6258 or 801-277-9240. We also maintain www.advancedaccounting.us so that older Business Tools users in particular have a greater chance to find us.

Follow

We highly recommend that accounting software users "follow" this blog via e-mail (enter your address and click on Submit below) or subscribe to a feed (see also below) as a way to keep current on the latest updates and accounting software news and information. You may also want to whitelist this e-mail address: noreply@blogger.com.

Follow by e-mail

Thursday, October 26, 2017

This file is currently not available for use on this computer

An accounting software end user today experienced the message "This file is currently not available for use on this computer" when trying to click on existing icons on two client PC's trying to launch tp7runtime.exe via a previously established network share and both using UNC paths.  The software in the installed ("gateway") PC in this workgroup still worked as expected.

The user had not made any changes other than to install an Adobe Flash Player update on one of the two client PC's.   No doubt however these PC's received recent Microsoft (and last week was a bad week for those that led to numerous problems, more than usual) and anti-virus updates (which can suddenly change settings, block ports, etc.).

All three of the PC's were Windows 7 Professional.   The network had already been established as a "public network" and naturally everything had been working without any problem until this morning.  The user had already tried re-booting the PC's on the network to see if that would resolve the problem.  It did not.

Remotely viewing one of the client PC's that could not load the software as well as the gateway PC, we noticed that the icon that launches the software that in this situation had been previously set to "Run as administrator" now had that check box grayed out.   And in trying for troubleshooting purposes to setup a new icon, Windows returned the same "file is currently not available for use" message.   In navigating the available computers to set that icon, it showed the gateway PC's computer name twice which was very odd.   We did make sure that the UAC was not getting in the way.

A net view of the gateway PC that had also been mapped as a drive letter for some reason indicated something interesting in the comments:  [Offline share].   In trying to delete the drive map, Windows responded that files were in use but viewing the gateway PC where that drive was mapped, in fact there were no open files in the shared folder.  

While we could also navigate to and view all of the files in the shared folder (and could also see the files at CMD prompt via a DIR of the UNC path), when we tried to inspect a text (INI) file by opening it in Notepad, we received the same response:



We made some minor changes to some of the network settings on both PC's, and tried to stop and start various network services on the gateway PC; the issue remained.   While the sharing and file privileges all appeared to be correct on the gateway PC, we decided to stop sharing the folder and then re-share it after first disconnecting from the offline share (after also turning off the option to share files offline which seemed to have no effect).   That was completed and we re-added "Everyone" with read/write privileges.  In doing this, Norton Internet Security installed on the gateway PC came up with a prompt indicating that because it was a public network, certain Windows services were blocked. We decided to go ahead and allow Network Discovery, File and Printer Sharing and Remote Procedure Call and Remote Procedure Call (and so they were added to the NIS exception list) which seemed logical in that it had already been established as a public network.    

Re-testing, the client PC's were then able to once again launch the tp7runtime.exe application.

There have been other reports of this issue that have involved very different solutions.












No comments:

Post a Comment