No Edit Session Rules

[jnjkerbin]

Hi,
As the title suggests when I click the edit session rules button nothing appears. However, the computer seems to think it has because I can't do anything else afterwards apart from pressing ENTER to exit the "window".
This has recently come up but it was working fine before. This affects every session, not just one. By the way I use TS2010.

Any help will be much appreciated.

Joe

 

[shaneturner12]

A few questions:

1.Have you installed any new rules into the game from the DLS? If so, check they are not faulty.
2.What build is your version? It may need a patch.

As it was working fine before, question 1 is more likely.

Shane

 

[jnjkerbin]

Shane,
Thanks for the reply.
Had a look at my rules and couldn't find any faulty ones.
The build Number is 44088
By the way one session, the one on which I first discovered the problem has the following thread exception errors:
Driver command rule: Thread Exception: ER_exception, line 418, file drivercommandrule.gs(1)
and also
Driver command rule:World.add driver command> not a driver command asset : <kuid2:122285:3498:3> (file world.gs)(1)
Thanks again,
Joe

 

[shaneturner12]

Might be worth tracking down the asset mentioned in the second exception in Content Manager - this is likely to be the problem one.

Shane

 

[jnjkerbin]

Thanks for the reply.
Had a look and that is andi06's Call at command which I don't actually have downloaded.
Any ideas...?
Joe

 

[shaneturner12]

My guess is that a route/session you are using requires that command, so you may need to download it.

Shane

 

[jnjkerbin]

Alright, thanks.
I'll do that as soon as the server isn't full any more.
I may be sometime...

 

[jnjkerbin]

Having downloaded the Call At command it still will not show the edit session rules box. In all other sessions where there is also this problem there are no thread exception errors, at least, not of this type. Any other ideas?
Thanks
Joe

 

[shaneturner12]

I think a database repair or possibly even a reinstall may be needed here, although I would advise trying the following (especially if you are running in Native mode)

1.Load into Content Manager.
2.In the search box, enter the following and click Apply:
LOCATION:LOCAL
FAULTY:TRUE
CATEGORY:SCRIPT
3.If anything appears in the results, review the errors as they will need fixing.
4.Repeat with Category:Rule.

If that still does not improve things, try an extended database repair.

If that still does not fix the problem, a reinstall is probably needed.

Shane

 

[jnjkerbin]

Thanks Shane, Had ago at the first method and I did an extended database repair when the problem first appeared so it looks like a reinstall will be needed.
Joe

 

[shaneturner12]

Good luck with that.

Shane

 

[jnjkerbin]

I'll tell you if it works.

 

[jnjkerbin]

Yep, thanks. That seems to have done the job.
Joe

 

[shaneturner12]

If it has fixed the problem, it was probably a faulty installation the first time.

Shane