Sage 100

I know FRx is going away, but this banking client has a lot of reports and uses FRx to secure access to information by ""branch"". We are getting very inconsistent results with security, and of course our test user works just fine. See the attached document which shows the setup and the testing and error message.

Can you pdf

Hit return too fast

But of course.

I've not dealt with this level of security - it's not something keyed into an ""allow external data access"" type thing? I assume not and that these are all errors on the same company code.

Allow external access is on. ODBC security is off. And this is in the same company with the same role based security. If it were easy, even I could figure it out! maybe

Yikes........... What service update of FRx are you running?

6.7.10343

A couple of thoughts that a looooong shots. When you installed FRx then installed the service updates, did you install 6.7.0911 first then install the current version. The reason I ask is that I had a similar situation that I finally had to call tech support on. After installing the SU's in order (no skipping), my error 8900 was resolved. A second thought would be to install SU 6.7.11027. What happens if you give the user complete rights to MAS?

We are going to try the SU 6.7.11027 and will update

It is important that you install all three SU's in sequence...........

Well a straight install of SU 6.7.11027 did not work. Given that we are here. Can you reapply patches or do you start clean. I am not sure we have all the interim patch levels. Does anyone have them all?

I always start over. Didn't Jim/Robert upload them to SugarSync?

Just got back in the office. I haven't been on the group long enough to know about or how to get into SugarSync. Do I have access. If so let me know how!

@GaryFeldman - Awhile back on a similar post from you (maybe for same client), I mentioned doing a Process Monitor trace at the time the 8900 error occurs in FRx - http://technet.microsoft.com/en-us/sysinternals/bb896645 Then in Process Monitor, start the trace and create the scenario that causes the 8900 to appear (or whatever error or issue is occurring on screen). Then you save trace to CSV file, open in Excel, and sort by Result column, then Time of Day column. You may see an ACCESS DENIED error which will show you which registry key or file/folder the permissions issue occurred on.

Yes, I remember. We are going to try this tomorrow before reinstall. Just got the files from Sugar Sync. Thanks and I will update tomorrow.

Update - We tried the process monitor and got nothing from it. We are installing on a clean server and will apply all patches in order.

The installation disk we use is 6.7.8069. The files downloaded from the Sugar Synch were labled 6.7.4 amd 6.7.8. We also have 6.7.11027 which I beleive is the last patch. It seems to me we only have one patch to install. Can anyone confirm?

Start with the 6.7.8069 CD. Then install ALL SU's that have a higher number than 8069. I think there are at least two, possibly three. I only installed .11027 once and fought the install for over a week. Opened a case with Sage and they installed ALL the SU's. Worked like a champ after that. Seeing was believing. Not sure why it worked as I had done everything Sage did with the exception of install all the SU's

Under the sugarsync site I see 2 service packs SP 9 and SP 11. We will go with SP 9 first and then 11 and report back. (We won't mess with the folder ""Appears to be bad"")

FRx67011027.exe, FRx67010343L.exe, FRx6709111h.exe

Did not see FRx67010343L.exe , they are no longer on the Sage site and it was not on SugarSync.

I have done quite a few SP installs where I jumped from 6.7.8069 to ""10"" or ""11"" without issue. It seems like this is a ""when in doubt try this"" situation.

That is what I previously thought until I ran into the buzzsaw. That was the line that Sage used. It worked so I am a believer. Looks like you can upload a 53 MB file. See attached.

We will put this on sugarsync