SIMS: Fault Code 1079-5888-0800

[Gatt]

Any idea?

Got this cropping up a fair bit since we cam back..

No info on SupportNet either..

 

Running version 7.112 here, tried a re-install but to no avail..

[Mcshammer_dj]

can you cut and paste a screen dump for us

[Gatt]

I shall try and get one for you...

[PhilNeal]

This fault code isn't in our solutions so please log a call.

[Setra]

Hi, we're now getting this too.

Did you get a solution, please, Gatt?

Thanks,

B

[danrhodes]

Hi, we're now getting this too.

Did you get a solution, please, Gatt?

Thanks,

B

 

As Phil said, log a call with sims.

 

D

[apeo]

Yeah, pretty much the best thing to do is to log a call/case. I assume the fault code didnt give you any options? i.e. the link that goes to the Capita site.

[Setra]

As Phil said, log a call with sims.

 

D

 

Thanks.

Aye, have done with the LA, but was just hoping at there might be more information on this, a year on...

B

[Setra]

Yeah, pretty much the best thing to do is to log a call/case. I assume the fault code didnt give you any options? i.e. the link that goes to the Capita site.

 

It mentions the S:\ Drive and lack of Connect.ini but no-one else has the fault and there's no link in it.

We're checking he can still see the S:\ srive but other than that, we're a bit stumped.

 

Thanks

B

[Gatt]

From what I can gather, this simply means that the SIMS Client cannot locate the connect.ini file

Usually it means the S: Drive hasn't been mapped or isn't accessible anymore

[Setra]

Thanks all!

 

Turns out the user had been prompted to change his network logon. He'd not restarted after doing that, so the network password was wrong, preventing access to the S:/ Drive (and all other drives).

Better cancel the LA call then!

B

[danrhodes]

Yeah it does, just make sure that your drive is mapped and permissions are correct.

 

In your Connect.ini you should have:

 

[sIMSConnection]

ServerName=AdminServerName

DatabaseName=sims

commandtimeout=100000

 

D

[timzim]

Do you map your drives with a logon script? We've had the same code a few times - usually means the user has logged on using their cached profile and then connected the network cable afterwards. Consequently the logon script, which maps the network drives, doesn't run correctly.

 

-edit- damn this instant updating........my post is now irrelevant......

[danrhodes]

Yes, we map using a staff logon script that connects the mapped drive to the server share. Remeber if your network has different domains, eg Admin and Curruiclum then the drive letter may be different.

 

D

[PhilNeal]

Just to reitterate. Fault codes are generated at run time and help us to pin down the failure to specific lines of code.

 

If a fault code cannot be found in our solution search, it has never come up before (unless our process fails!) so we will have to investigate.

[timzim]

If a fault code cannot be found in our solution search, it has never come up before (unless our process fails!) so we will have to investigate.

 

Hmm, not quite true Phil - I think you mean "we've never seen it" rather than "it has never come up before". Not quite the same thing!

[danrhodes]

Hmm, not quite true Phil - I think you mean "we've never seen it" rather than "it has never come up before". Not quite the same thing!

 

That made me smile. Fair point though TimZim, I agree, I think that was the wrong wording to use.

 

D

[matt40k]

Hmm, not quite true Phil - I think you mean "we've never seen it" rather than "it has never come up before". Not quite the same thing!

 

Like being back in English class!! Surely ignorance is bliss? If you don't know about it, it didn't happen!!

 

"No, sorry, my server didn't catch fire because it didn't send me an email informating me that it caught fire"

[vikpaw]

i think they've got enough problems to fix, without worrying about things that they've never had occur to them, and nobody else has reported to them yet!

[vikpaw]

Thanks all!

 

Turns out the user had been prompted to change his network logon. He'd not restarted after doing that, so the network password was wrong, preventing access to the S:/ Drive (and all other drives).

Better cancel the LA call then!

B

 

Don't cancel the call, it would be useful if they can get it to appear on SupportNet even if it says that it's not been fully investigated, but has previously been solved thus:. .. . .

[danrhodes]

i think they've got enough problems to fix, without worrying about things that they've never had occur to them, and nobody else has reported to them yet!

 

VikPaw are you implying that sims is problematic? ;-)

 

D

[vikpaw]

VikPaw are you implying that sims is problematic? ;-)

 

D

Are you implying it isn't?

There are so many things in the pipeline at the moment, i'd rather they got them right first time, rather than spend time elsewhere unless it's absolutely necessary.

[timzim]

i think they've got enough problems to fix, without worrying about things that they've never had occur to them, and nobody else has reported to them yet!

 

How many times do we (or our users) click on a SIMS error message and get the reply "Unknown error"? How hard is it for Crapita to make this into automatic error reporting (if it isn't already)?

 

I give up on the number of times I've directly reported an error to them, only to be told "send us your database" (a pointless exercise since they either never get back to you with a reply once you send it and/or claim you never sent it in the first place). Yawn.

[creese]

How many times do we (or our users) click on a SIMS error message and get the reply "Unknown error"? How hard is it for Crapita to make this into automatic error reporting (if it isn't already)?

 

I give up on the number of times I've directly reported an error to them, only to be told "send us your database" (a pointless exercise since they either never get back to you with a reply once you send it and/or claim you never sent it in the first place). Yawn.

 

As long as it was turnoffable, I wouldn't want the majority of users anywhere near a potential fix. In case they tried it.

[vikpaw]

How many times do we (or our users) click on a SIMS error message and get the reply "Unknown error"? How hard is it for Crapita to make this into automatic error reporting (if it isn't already)?

 

I give up on the number of times I've directly reported an error to them, only to be told "send us your database" (a pointless exercise since they either never get back to you with a reply once you send it and/or claim you never sent it in the first place). Yawn.

 

Yeah, i see what you mean on the first point, except, quite often people get exceptions, thrown out with some random error, that's not known, but then they reboot and try again as per my advice, or i attend and it's all fine. So i wouldn't want all those false positives being recorded, as i imagine there's no benefit for every tiny user fault combination to be logged.

 

I completely sympathise with the second point, and since i moved overseas, the internet is so slow, i have to split my 1GB zip into 10 chunks and send them 1 at a time. That's a right royal PITA!

 

As long as it was turnoffable, I wouldn't want the majority of users anywhere near a potential fix. In case they tried it.

 

I do encourage my users to record / send me the fault codes, and at least try and click the 'Search for Solution' button. On occasion there is a simple solution, but i see what you mean, if it says reinstall sims or rerun simsapplicationsetup maybe you don't want users doing that.

 

I've added a link to the fault code search page to our intranet helpdesk to make troubleshooting a bit quicker, though yes, in practise it doesn't often offer a solution.