Level 5

Question

Fixed Asset Manager error: "File is not a Data File"

Forum|Forum|6 years ago
December 16, 2019
42 replies
252 views

stand alone FAM 18...have used with no problems for a number of clients all of 2019 and as recently as 12/11/19. Now, one of my client files (last used 12/11/19) won't open with error message File is not a Data File. After typical location in my C drive\FamWin18\Clients\{190701_

there appears the following: {190701_R.F80.

Other client files do not have this second client file number followed by _R.F80

wassup? how do I recover without having to go to my online backup company?

ProSeries Professional

This topic has been closed for replies.

J

Jana124

Level 2

Did you ever find a fix to this? I'm using Fixed Asset Manager 2019 and i keep getting the "not a data file" when i try to reopen the client

nytcpa2012Author

Level 5

I did not resolve this issue. It's been my experience here that when no one knows the answer, there's just no response whatever.

K

Karen6

Level 2

I have had this same issue with at least 6 client files. We have lost the data and had to recreate it because the problem usually occurs immediately after working in the client file so there is no time to backup the file. Please figure out a fix to this or we will have to quit using the program that we have used for the last 15 years with no problems. I have wasted at least 8 hours on this problem - PLEASE HELP!

N

njs

Level 2

We have had the same issue since the fall of 2019. We have used FAM for more than 10 years. Intuit is not acknowledging the problem. Support staff states "It has never happened to anyone else" , "it is specifiec to your setup", "Your IT must have something installed incorrecly" and I can go on each time a different twist but no help. We lost over 1 months hours recreating FAM files in the last year. We are considering changing tax programs for this reason.

H

HGH

Level 3

This happened to me, too. Was able to restore backup and reenter current year when it happened again. Now not even a menu in FAM.

nytcpa2012Author

Level 5

good to know that it seems to be happening when trying to convert to a pdf file and/or when printing a pdf file? That's the only clue I've heard (from fellow users of FAM in this forum, certainly not from ProSeries) since posing the question many moons ago

I will try to remember that and avoid doing that until I have saved the file under a different name or have a local backup for it.

Taxes-by-Rocky

Level 7

Similarly, we have used the package for over 10 years (on a network) but never had a problem until this past year, and the file always corrupted after someone had worked in it for a period of time. ProSeries tech support advised us to exclude the client file directory from the virus scanning software, which we did, but that did not resolve the problem. At the same time, we were experiencing a problem with Windows Explorer (via Windows 10) shutting down randomly multiple times a day (often when you had more than one window open). We determined that our group policy and drive maps were disconnecting multiple times a day and reconnecting instantaneously (similar to a IP lease reset on a network). In short, the person working in the FAM file never knew it was occurring while working in the program. A slight tweak to the group policy and drive maps by our IT guy fixed the problem. Moral of the story: I suspect the program is disconnecting from the underlying FAM client file while your working in it. But, as I said, you'll never know it. You might be able to isolate a root cause of same if you're on a network or place the client files on a 'remote' drive. Hope that helps. We have not had a problem with the FAM package since. [And yes, the thought of recreating a file is nothing short of a horror show.]

K

KSIT

Level 2

Any chance you know what the "slight tweak" your admin made to group policy? We are having the same issue here and I'd like to do some tweaking of my own.

Thank you.

Rob.

Taxes-by-Rocky

Level 7

Rob,

This is the response I got from our IT guy with respect to our system. We we're moving from SBS 2008 R2 to WS 2019:

....it had to do with the “Item-level targeting” section of the mapped drives group policy. There is an option that never worked properly in previous versions of Windows Server, but was finally “fixed” in the more recent versions. I can’t remember exactly, but I think it was the option for “Apply once and do not reapply” option that needed to be selected so that the policy would not try to re-map the drive while the use is in-session. This would need to be the same across all mapped drives in order to prevent the re-mapping."

Apparently worked for us.....but results may vary. If you search for "Apply once and do not reapply" you probably find it.

T

TAG

Level 2

Hi,

This issue happens a lot, the fastest way to restore your file is to open either your backup FAM or your actual FAM file.

1. Create a folder from a different location in your computer or your network, doesn't matter--but a different location helps. Keep the new folder name short.

2. Move the files inside the folder to another folder. Make sure that you copy and paste the files inside your backup file or FAM file --DO NOT move the folder itself--or it will not work.

3. Then go to the restore current year file and click that folder where you move it, it should restore everything. This is the only method that works for me.

Lastly, always backup your fixed asset file after making a major change.

Hope this helps.

Regards,

Rona

The Accountants Group

www.theaccountantsgroup.com

Sign up

Login with SSO

Let's get you signed in

Login with SSO