FMS Issue (Fix works but only temporarily).

[Heebeejeebee]

Hi,

 

We have a workstation that was fine yesterday but today shows "Runtime Error at 217 at 000256AA" when runnig FMS when logged in as a nornal user. It works fine as administrator.

 

The solution KB73422 covers this and I've deleted the user profile (several times) and deleted all temp files. No joy on Fix1. Fix 2 works but only until the next time they try to use it. This user has PDF creator and a networked printer and switching the default printer to PDF allows FMS to be run. If they then switch to the usual default printer they can't print from FMS until they've gone into the print setup and selected the network printer. Also switching back makes the program fail next time.

 

As you can imagine this is a bit of a faff for the user concerned and I'm wondering if the solution fails because it's a networked printer. What I don't understand is why it worked yesterday and not today.

 

Any pointers?

 

KB73422 Fix:

 

FIX 1

 

This is a Windows error referring to the user profile becoming corrupt. You can check this by logging on the Server as a different user with administrative privileges

 

To solve the error

1. delete the corrupt user profile and recreate it.

2. delete the contents in C:\ Windows\temp folder

 

If this is the administrator profile on the server, another profile can be created with admin rights.

 

FIX 2

 

Please change the default printer, and then log into FMS.

Once you can login successfully, you may then change the default printer back to what it was.

 

Cheers

 

HBJB

[matt40k]

Basically, assuming I thinking of the same KB, the problem with FMS is that it's written in Delphi which has poor print support. Basically, the simplest way is to use a Adobe PDF writer as your DEFAULT printer. Otherwise you'll be trying different print drivers, I tend to find PS drivers the best. I would guess your default printer has changed between now and then, or Windows Update has "helpfully" updated your print drivers.

[Heebeejeebee]

Ta,

 

No WSUS update to this machine since yesterday and the printer drivers have not been updated. Default printer is set at logon script and has not changed.

 

It's FMS.net. BTW.

 

HBJB

[matt40k]

There's SIMS .net, no such thing as FMS .net. Not for a while anyway.

[Steve_T]

Not herd of this with a printer, only when no default had been selected? What drivers are you using PCLX?

[Heebeejeebee]

There's SIMS .net, no such thing as FMS .net. Not for a while anyway.

 

D'oh - you know what I mean, FMS-SQL - the new one (v6.116) !! OK now?

 

Printer uses PCL6 drivers and there is always a default one set.

 

HBJB

[matt40k]

D'oh - you know what I mean, FMS-SQL - the new one (v6.116) !! OK now?

 

Printer uses PCL6 drivers and there is always a default one set.

 

HBJB

 

Hehehe, yer we've all done it.

 

Just to confirm it is a printer problem. Remove all the network printers, add a local USB printer, give it a whirl.

[splattthecat]

Catita recommend PCL5 drivers for FMS printing.

[Steve_T]

^^ beat me too it try changing to PCL5 unless on Vista.

[Heebeejeebee]

Catita recommend PCL5 drivers for FMS printing.

 

Will try that. Cheers.

 

It still doesn't explain why it stopped working though. I could if necessary make the printer local because it's in the same room as the PC it's only networked because the office is shared and the other person needs to print to it too (and we need to log all the print jobs).

 

Cheers

 

HBJB

[Potato-Peeler]

I just experienced this myself, and it turns out with sims fms, if you change the default printer it will stop working, until you change it back to what it was. Does that help you at all?

[Heebeejeebee]

I just experienced this myself, and it turns out with sims fms, if you change the default printer it will stop working, until you change it back to what it was. Does that help you at all?

 

I was about to update this thread but you beat me to it.

 

That didn't work for me when the problem existed. My problem happened on a Friday and I tried all sorts of things to fix it to no avail, when I got in on the Monday to change the drivers to PCL5 ones it was reported to be functioning normally again and hasn't failed since . I changed the drivers anyway but it seems to have been a glitch that fixed itself somehow.

 

HBJB

[Sam_Brown]

2015 and this issue still happens!!!