[sims] SIMS FMS General SQL Error LRM07

[lquinnuk]

Hi all,

 

The school manager is looking at creating the entry for new fianancial year in FMS, how ever when it comes to clicking 'save' at the end of the process I get a lovely error message reading...

 

'General SQL error [Microsoft SQL Native Client] SQL Server LRM07'

 

Again I'll have to admit I'm a little wet behind the ears when it comes to SIMS, the server and workstation have been rebooted, all the other features in SIMS/FMS work perfectly happily for everyone in the school, it's just when trying to create a record for the new financial year.

 

Does anyone have any suggestions as to where to start with this?

 

Thanks in advance for the always sterling help.

[vikpaw]

LRM33 was a printer issue, so worth a try.

[Rawns]

It could be a printer error like @vikpaw suggested, but I think it's an error relating to lack of write permissions to the PDOXUSRS.NET file, or the folder it's stored in. In the BDE settings, we set the Paradox NET DIR location to C:\IDAPI and ensure every user has full write permissions to that folder.

[lquinnuk]

It could be a printer error like @vikpaw suggested, but I think it's an error relating to lack of write permissions to the PDOXUSRS.NET file, or the folder it's stored in. In the BDE settings, we set the Paradox NET DIR location to C:\IDAPI and ensure every user has full write permissions to that folder.

 

I think my lack of SIMS knowledge is my down fall here, what are the 'BDE settings, and paradox net etc, I understand about write permissions but not a lot else, unfortunately I've walked into a situation were everything has been setup long before I arrived and now there is literally no one in the school with any knowledge of the system and its configuration.

 

When I search for the pdoxusers.net file it's sat on C:\ on the server in no folder

 

Cheers

.

[lquinnuk]

I'll log on to the system as domain admin and see if that changes the outcome as it should rule out write permissions...

[vikpaw]

Then it's most likely permissions if you're using a win7 client.

There are threads here with details on moving the file as granting permissions.

[vikpaw]

Try run as admin on FMS to rule it out.

[vikpaw]

But then your Sims drive connection may not work!

[Rawns]

I think my lack of SIMS knowledge is my down fall here, what are the 'BDE settings, and paradox net etc, I understand about write permissions but not a lot else, unfortunately I've walked into a situation were everything has been setup long before I arrived and now there is literally no one in the school with any knowledge of the system and its configuration.

 

When I search for the pdoxusers.net file it's sat on C:\ on the server in no folder

 

Cheers

.

 

It's not specifically on the server (although it will be on the server as FMS is installed on it). It's a file on every machine that has the FMS client installed. I "believe" it controls table access to the FMS database to ensure users don't try and amend the same data at the same time.

 

Open the control panel on the workstation, and you'll find a BDE Administrator option. Open it, select the configuration tab then expand Drivers | Native | Paradox and the first setting in the list is the NET DIR (where the PDOXUSRS.NET file is created). Try setting it to a folder off the root of C: (like C:\IDAPI) and click the blue arrow to save the changes. Create an IDAPI folder on the C: drive and ensure that users have full write access to this folder, then get the user to try again.

Edited March 12, 2013 by Rawns

[lquinnuk]

It's not specifically on the server (although it will be on the server as FMS is installed on it). It's a file on every machine that has the FMS client installed. I "believe" it controls table access to the FMS database to ensure users don't try and amend the same data at the same time.

 

Open the control panel on the workstation, and you'll find a BDE Administrator option. Open it, select the configuration tab then expand Drivers | Native | Paradox and the first setting in the list is the NET DIR (where the PDOXUSRS.NET file is created). Try setting it to a folder off the root of C: (like C:\IDAPI) and click the blue arrow to save the changes. Create an IDAPI folder on the C: drive and ensure that users have full write access to this folder, then get the user to try again.

 

OK I'll give that a try, I've just tried logging onto the work station as domain admin and got the same error as before.

 

I've spoken to the user and she's managed to create a new financial year, year in year out since 2001 so I'm puzzled as to why this year decided to have a problem.

 

She's out on duty at the moment so I'll have to wait for her to get back before I can try it (coded door lock) I'll try it and let everyone know asap

[lquinnuk]

I've also tried running FMS directly from the server it's installed on loggin on as the user and performing the same actions, and I got the same error.

 

I'm not sure if this changes anything in terms of diagnosing the problem

 

cheers.

[lquinnuk]

It's not specifically on the server (although it will be on the server as FMS is installed on it). It's a file on every machine that has the FMS client installed. I "believe" it controls table access to the FMS database to ensure users don't try and amend the same data at the same time.

 

Open the control panel on the workstation, and you'll find a BDE Administrator option. Open it, select the configuration tab then expand Drivers | Native | Paradox and the first setting in the list is the NET DIR (where the PDOXUSRS.NET file is created). Try setting it to a folder off the root of C: (like C:\IDAPI) and click the blue arrow to save the changes. Create an IDAPI folder on the C: drive and ensure that users have full write access to this folder, then get the user to try again.

 

Have carried out the instructions as you suggested but to no avail, exactly the same issue.

 

I've got a called logged with our external support company who set up SIMS originally and am waiting to hear back from them.

 

In the mean time any other suggestions will be greatly appreciated.

[vikpaw]

Reinstall SQL native client.

Reinstall FMS.

ideally on a new machine rather than mess with the existing working one.

[lquinnuk]

Reinstall SQL native client.

Reinstall FMS.

ideally on a new machine rather than mess with the existing working one.

 

I was hoping to avoid such extreme actions, new machines are like gold dust in our school, as are old ones, I'll definitely wait for a reply from the support company before I go down that route.

 

On the subject, how is FMS installed? I've installed SIMS by running the siminst.exe (that might be spelt slightly wrong) on the server, but as of yet I haven't needed to install FMS, is it more or less the same method?

[lquinnuk]

Is it possible that windows updates could have caused any problems.

 

The SIMS server is still running 2003, could the work station (win 7) have installed any 2008/2012 SQL updates that are causing a conflict or is that unlikely?

[Rawns]

Is it possible that windows updates could have caused any problems.

 

The SIMS server is still running 2003, could the work station (win 7) have installed any 2008/2012 SQL updates that are causing a conflict or is that unlikely?

 

Workstations won't receive any SQL updates as they don't have SQL installed.

 

Have you tried the classic (and sometimes successful) step of doing a complete reinstall of FMS? It's installed in the same way as SIMS, but in your Setups\FMS folder is an FMSInst.exe file. Basically, rename the current FMS installation folder on the affected workstation to something like C:\Program Files\SIMS\FMSSQL.OLD and then run the FMSInst.exe from the S:\SIMS\Setups\FMS folder. It will install any pre-requisits that are missing and then install the FMS client.

 

Does this happen on any other FMS workstations?

Edited March 12, 2013 by Rawns

[Rawns]

I was hoping to avoid such extreme actions, new machines are like gold dust in our school, as are old ones, I'll definitely wait for a reply from the support company before I go down that route.

 

Reinstalling FMS is really not an "extreme" action. You'd be surprised how often good, old fashioned reinstall of SIMS .net or FMS fixes odd issues!

Edited March 12, 2013 by Rawns

[lquinnuk]

 

Does this happen on any other FMS workstations?

 

There are only 2 FMS workstations in the school and the problem occurs on both of them, which leads to me think that a re-install of FMS on the clients will do very little, unless they have both developed the same issue at th esame time, which I'd think would be a strange co-incidence.

[lquinnuk]

Reinstalling FMS is really not an "extreme" action. You'd be surprised how often good, old fashioned reinstall of SIMS .net or FMS fixes odd issues!

 

 

You won't find a bigger advocate of the complete reinstall than me, I just have a feeling it's not were the problem lies, plus it would mean too much down time for the manager whilst I'm carrying out the action.

It is something I'll try if needed but that fact the error is the same on all the workstations running FMS makes me think a reinstall will do very little.

[techie08]

Got this same error yesterday. Have you checked the users FMS permissions? Has the user supervisor access?

[vikpaw]

i was thinking more along the lines of install it your machine for testing then remove it, not a new one, and not on theirs.

[lquinnuk]

Got this same error yesterday. Have you checked the users FMS permissions? Has the user supervisor access?

 

I assume to check the users FMS permissions I would need to log in as an FMS admin, unfortunately the admin accounts are known only by a now retired ex employee who only comes in on Mondays, I have absolutely no access to FMS, only to SIMS, and even then I don't have full access rights to everything.....I'm aware how stupid that is.

 

How did you ressolve the issue?

[techie08]

I assume to check the users FMS permissions I would need to log in as an FMS admin, unfortunately the admin accounts are known only by a now retired ex employee who only comes in on Mondays, I have absolutely no access to FMS, only to SIMS, and even then I don't have full access rights to everything.....I'm aware how stupid that is.

 

How did you ressolve the issue?

 

I Logged on as the sysman user and gave the user supervisor access in FMS. The user could then create the new Financial year.

Edited March 12, 2013 by techie08

[lquinnuk]

I Logged on as the sysman user and gave the user supervisor access in FMS. The user could then create the new Financial year.

 

Thats a Bingo, luckily the support company had a record of the admin unser name and password which meant I was able to give the user supervisor access, and hey presto.

 

At least now I can stress the importance of me having top level logins for SIMS with school management, so I can ressolve issues like this as and when they arrise in future.

 

Thanks for everyones help today, and hopefully people who have this problem in future have a nice clear answer to that specific error message.

 

Cheers.

[vikpaw]

Make sure the support company feeds back to Capita, so the solution ends up on SupportNet the official Capita support site.

In terms of your access you can tell them that top level sysman access doesn't necessarily give you rights in to all areas of sims, only to grant those rights to others. So it should be safe and auditable. It's a little different for FMS, but in theory the same principle should apply.