on 10-21-2009 3:15 PM
Hi,
last month we used our AT BOXI system to help restore a folder's worth of reports that an unfortunate user had deleted in production. In the course of the restore the AT BOXI CMS and input and output frs were pointed at the restored databases.
I've now tried to repoint the CMS and frs's back to the original databases and though the CMS restarts ok the frs's refuse to restart.
The shared drive with the frs on it was 'unshared' for a while according to our server guy who helped with the restore but he says he's put it back now just as it was (though I believe the old name was atboxifrs and it's now ATboxifrs). He also says all the access rights to the share are the same.
What could be preventing the frs from restarting?
We have BOXIr2 SP4 on a Windows server.
thanks
Keith
thanks for your help guys, it's working again now after my colleague made some more changes at his end, it was the access to the drive causing the problem,
thanks
Keith
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Keith,
Did you try to enable tracing at frs process level ?
to do this, change the command-line of the processes and add "-trace" parameter.
Next, log files will be created in <BO dir>\Logging
And check errors in the log file. Beware that it could grow rapidly.
Samuel.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I added the -trace parameter and created a log file, the file shows the following problem:
[Thu Oct 29 10:17:59 2009] 4628 8280 Log: level=0 cat=28 msg=35600 p=Failed to setup the root directory
sdorsf004\ATboxifrs\boxi_frs\input\ for use. Please make sure permissions are correct and there is no sharing violation.
[Thu Oct 29 10:17:59 2009] 4628 8280 Log: level=0 cat=28 msg=35600 p=Failed to setup the root directory
sdorsf004\ATboxifrs\boxi_frs\input\ for use. Please make sure permissions are correct and there is no sharing violation.
[Thu Oct 29 10:17:59 2009] 4628 8280 Log: level=0 cat=14 msg=35101 p=The root server reported an error Internal Error. (Reason: Fail to initialize file system. Please see event log for details.).
[Thu Oct 29 10:17:59 2009] 4628 8280 trace message: SIServerController:run: Fail to initialize or uninitialize. Reason is The root server reported an error Internal Error. (Reason: Fail to initialize file system. Please see event log for details.).:
My server guy reckons that the account we are using has the correct permissions (though I've asked him to check that again). Is there anyway of checking for myself, or is there anything else this error message could be teeling me that I'm missing?
thanks
Keith
This errors indicate that the account under which FRS are running has no access, ot not enough rights on the
sdorsf004\ATboxifrs\boxi_frs\input\ directory.
To check, login into the server with this account, go to command prompt, cd
sdorsf004\ATboxifrs\boxi_frs\input\ and try to create a directory or a file there.
Denis is right. This is an access issue.
Do your server guy see something on Event viewer (security & log) ?
Also, maybe he could put access auditing on this particular folder to see with wich account the process try to access it.
see this forum post if it can help you out :
http://www.forumtopics.com/busobj/viewtopic.php?t=139193
Also, the folder should be shared I suppose...
Edited by: sjolly on Oct 29, 2009 1:18 PM
Please let me know this, Right click the Input Frs and in properties see what user id its using to logon, and please be sure to login using that user id and it should have admin access. If you still have error let me know
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
87 | |
10 | |
10 | |
9 | |
7 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.