Hi there Charles,

Was wondering if you found a fix to your problem of additional logins when not admin?

We're currently back at stage 1 from Feb. where we can't import anything into the server.

Users (even those with local & server admin rights..ie me! ) get error log =

ODBC-Call failed

Our server admin got this error at stage 2 ' Do Import' =

Exception path: EInOutError : File access denied

As it appears no-one else in the country has this problem, I think we can perhaps deduce it's our network. Not that we're any closer to solving it.

All & any help gratefully received.

I've managed to solve this problem, although the exact cause still eludes me. It seems remnants of R2002 and R2000 installs were affecting things. I removed all of the registry settings associated with R2K2 (the ones under the JNCC nodes in the registry) and that seemed to get things working on some of our computers. A couple of others were crashing on startup, but I found several more references to either R2K2 or R2K in the registry and also some directories left hanging about. I deleted all of these, re-ran the workstation install and I can now R6 runs as a restricted user.

One question though, on the computers that were crashing, a message came up saying that the Recorder 2000 settings were being updated. One of them required that I specify the DTD directory. Where was it getting the information that there had been a previous version of Recorder? I thought I'd stripped out all mention of previous versions, but clearly it was still finding something somewhere. Either way, everything is working now.

Just a thought, but are all of the registry settings/file locations/etc for previous versions of Recorder documented anywhere? It would be really handy to know what and where they are so that us users and admins can absolutely sure of what to clean up, should we need to.

Charles

Ah, that explains things then. Thanks John.

Hi there,

Well, we've finally had a successful morning with our network. Essentially, although the Recorder users group had read/write access to NBNData.mdb, they weren't actually listed as users for the SQL Server files within the C-drive in explorer. Our ICT guys are looking at whether the group still need to have local admin rights in order to use R6 this afternoon, whilst I check how to migrate the database from Standalone to server.

One of the things which perplexed me from Charles' earlier post was that in the machine we were testing this morning, no R2K version had ever been installed in it.

Referring to his latest post,

" have to log in as me (I'm an admin) change the user to an administrator, log out, log them in, start Recorder, log them out, log in as me, change the user back to restricted, log out, log back in as the user, then start Recorder"

we did get access violations until we noticed that we'd renamed one of the shared drives incorrectly during the install. However I'm guessing you're referring to normal operation, no?

So, once we've defined what & who has access to where, together with thoroughly testing it works, I'll post the configuration here then on Wiki, ok?

Cheers now, Rob.

Charles

I haven't used these for a while, but there are freeware tools around called RegMon and FileMon which should monitor your registry & file activity and let you know which accesses are failing when you start Recorder.  Worth a shot I think.

Did anyone resolve this problem? I have Recorder 6 installed on a network machine that's never had any previous versions installed on it, but still get the crash on opening of Recorder.