Or at least vaguely connected to the actual problem.
I mean why have it come up with Reason 2.......great, yeah I know the reasons off by heart!
And the best one being
"This software requires an additional xxxx bytes free on the X: drive to install"
Yet the drive in question is mapped and has 126GB free. So the error message isn't stating the problem at all.
Well I know it is'nt much help but Reason 2 is aways to do with network connection propblems, either the cable is out, the server is down or the share hasn't mapped. Something networky. Why oh why they couldn't have labelled it that way I have no idea.
Reason # alwasy seem like debugging labels that have never been re-mapped. Shoddy unfinished coding? Noo can't be Capita.
Oh yeah we worked out Reason 2 in the end. Guys from the council said the actual Reason 2 error is that the SQL server isn't started. So basically if you have a network cable unplugged, it can't contact the server and thinks SQL isn't up.
This is like Lord of The Rings error codes. One bloody error to rule them all.
Like you said, anything with loss of network will mean it can't see SQL so reason 2. But why not just have:
"Reason 2 - Cannot see the SQL server, please make sure the service is running and the PC is connected to the network"
Anything like that at least narrows down messages!
As for the free space error, i give up. even simsinst.exe moans that the mapped drive doesn't exist, even though im running simsinst.exe from that drive!
The ran out of disk space problem I have found is down to the setup program pointing to a drive that isn't mapped on your system. E.g. S:\SIMS.
When you run the setup program, click the settings button (bottom left) and under 'Workstation' change the drive letter for 'Install SIMS application in the shared directory' to the drive letter of your SIMS drive mapping.
This worked for me when I got that error message.
Originally Posted by MK-2
For an error message to be useful, the programmer actually has to know what's gone wrong when an error message is issued.
'nuff said
yep, but like i said, the drive is mapped and working fine.
plus we have a new layout simsinst thing. there isn't a 'settings' button to click anymore. it asks for the setup dir, then the next page asks for local and remote paths. but when it asks for setup dir, it defauls to c:\sims\setups\ and if i try changing that to i:\sims\setups\ (where the simsinst.exe is running from) it says that the path doesn't exist.
elsiegee: good point well made!
We had on a couple of occasions when running SIMS.net the following error message:
Catastrophic Error
That was it apart from an OK button which when clicked allowed you to carry on working as normal... if someone would like to explain that to me I would be grateful!
Thanks for pointing this out - a fair cop I think.
I have had a word with the Development Director!
Have to agree, and glad to see Phil has had a word
With the bytes free error, is it down to permissions? Just a stab in the dark...........
I would love to see this! It would bring some humor to the day!
My favouriteSIMS error message must be the one in the old DOS module. It went something along the lines of:
Error 234232.
Something has happened to cause SIMS to stop working. It probably isn't your fault but is caused by an error in our programmers' logic.
Try restarting or calling your SIMS support team.
Well... you can't beat honesty.
I think it was "Thinking hard - please wait"!
Just skimmed over this forum and it made me chuckle, I really liked some of those older errors.
Whats annoying about the reason 2 error is that it actually used to say, SQL Server does not exist or access denied which was more obvious to resolve.
On the other hand however I've been moving a few SIMS and FMS installations from PC's to Servers recently using converted FMS databases and I've found that the error messages have been quite helpful telling me exactly whats missing or what app to run to resolve my issue.
A shame this can't be so good all the time.
To be fair to Capita (not defending them), but Sims requires SQL server and .NET Framework which are both Microsoft products. A lot of error messages I come across in Windows do not make sense, or display a random error code. How usefulI would blame MS too.
Error messages are one of the more difficult aspects of programming to set up and maintain. Ensuring they are meaningful to an end user is a very difficult thing to do.
Imagine 10 million lines of code, much of which can cause an error. Now imagine documenting it, and introducing error messages. It makes even the most battle hardened programmer sweat.
There are currently 1 users browsing this thread. (0 members and 1 guests)
Posting Permissions
LinkBack URL
About LinkBacks