Running SECC 4.2 client on an XP PC; suddenly, one of the Symposium user accounts no longer will access its reports, reporting that "Operation failed, no current record." Problem persists whether logged in locally or on our network (and the local account has full admin rights). The nicrpt.mdb is intact and has reports owned by the user. If I use the sysadmin account on that same PC, we can pull up the canned reports, but of course cannot see the reports that were setup by the other user. Other than changing the owner name to a different account name (or sysadmin), is there a way to get around this error? I have no clue yet what happened to cause this, but I do have some suspicion about a remote control utility we use that seems to wrangle with the user's registry. Any related suggestions or testimonials appreciated!
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
SECC 4.2 User can no longer access Reports 1
- Thread starter RParent
- Start date
-
1
- Thread starter
- #3
Resolved, with a bit of help from tier 2 support as well as some pure luck:
- After the initial problem, we tried to delete the user and recreate, but then saw two errors on the server, indicating there was a problem deleting the user. Turns out you need to go into the scheduler and delete ALL the scheduled reports tied to that user, in order to be able to delete it.
- once the reports were deleted from the scheduler, I still could not see the original user in the normal user admin screen, so I went into the advanced functions and saw the account there.
- Nortel training warns against any user admin at this screen, but since the account was already broken and I couldn't see the account on the normal user admin, I decided to try to delete it, now that the scheduler was clean. Now the account deleted!
- went back into the normal user admin screen (use the Wizard Manager option under Windows) and created the user, with the same PC id that we had before
- on client workstation, opened nicrpt.mdb, opened the reports table, and took out the check in the active field, where the owner name was the same as my account; I don't know if this step was necessary, but I still don't understand the layers of PC/server authentication for this application, so I thought it best to clear this field rather than potentially cause any grief with this scheduler function.
- launched the client and logged in successfully. Things seem to be working, including activating the scheduled reports...
A few other things I noted:
- we run a Novell client; logging in to the workstation locally did not have any impact on the situation;
- we also normally roam our Novell profiles and stacking local profiles do not seem to cause problems with the application, providing the registry is getting the HKCU merge it needs to run the application for any user
- rebooting the server had no impact on the acccount delete error - the key there seems to be to delete associated jobs out of the scheduler prior to manipulating an account
- After the initial problem, we tried to delete the user and recreate, but then saw two errors on the server, indicating there was a problem deleting the user. Turns out you need to go into the scheduler and delete ALL the scheduled reports tied to that user, in order to be able to delete it.
- once the reports were deleted from the scheduler, I still could not see the original user in the normal user admin screen, so I went into the advanced functions and saw the account there.
- Nortel training warns against any user admin at this screen, but since the account was already broken and I couldn't see the account on the normal user admin, I decided to try to delete it, now that the scheduler was clean. Now the account deleted!
- went back into the normal user admin screen (use the Wizard Manager option under Windows) and created the user, with the same PC id that we had before
- on client workstation, opened nicrpt.mdb, opened the reports table, and took out the check in the active field, where the owner name was the same as my account; I don't know if this step was necessary, but I still don't understand the layers of PC/server authentication for this application, so I thought it best to clear this field rather than potentially cause any grief with this scheduler function.
- launched the client and logged in successfully. Things seem to be working, including activating the scheduled reports...
A few other things I noted:
- we run a Novell client; logging in to the workstation locally did not have any impact on the situation;
- we also normally roam our Novell profiles and stacking local profiles do not seem to cause problems with the application, providing the registry is getting the HKCU merge it needs to run the application for any user
- rebooting the server had no impact on the acccount delete error - the key there seems to be to delete associated jobs out of the scheduler prior to manipulating an account
- Status
Similar threads
- Locked
- Question
- Locked
- Question
- Locked
- Question
