Accpac 5.6 Slow Printing 2

[hurricane4]

Good Day All,
Just completed an upgrade to 5.6 PU3 (using SQL) and everything appears to be working correctly except printing on the client machines. All reports take approximately 20 seconds to print regardless of OS, printer or even to print preview. Even the simplest reports including a custom Crystal report take this long. Other Accpac programs seem to be working fine with quick lookups and posting. On the server, reports are printing as expected without the delay.

I have tried just about all the suggestions I have seen regarding slow printing but have not had any success. Things tried include; checking DNS, checking ODBC settings, re-installing client, checking print drivers, checking the client registry, deleting p.ism and others.

Any ideas would be appreciated.
H4

 

[Jay Converse]

Administrative Services/Customization Directories/Old server in path

 

[hurricane4]

Thanks for your reply tuba,
Nothing in Customization directories though.

I also want to add that two of the client workstations are brand new and so do not have any remnants of the old Accpac on it.`

 

[Jay Converse]

Turn off antivirus and see what happens.

 

[hurricane4]

Uninstalled anti-virus from two workstations. One with XP which had old accpac is now taking even longer to print - about 45 seconds now! The other, Win 7 no previous Accpac had no effect. Anti virus was already disabled on server side.

 

[Jay Converse]

Something non-Accpac is interfering. What's your network infrastructure like? What other applications are installed (besides MSOffice)?

 

[hurricane4]

Not ignoring your last question tuba, but I have had somewhat of a breakthrough. I recreated the user DSN for the Administrator account on a client am now able to print without a delay. Strangely though this only seems to help for the Administrator account and does not help if I recreate the User DSN on other accounts that have been given administrative rights. I am also unable to reproduce this result on any other clients so far!

 

[Jay Converse]

You should be using a single System DSN, i.e., {servername}32, and in Accpac database setup, you reference the server name, not separate DSNs.

 

[hurricane4]

That did the trick - thank you very much for your help.

Just for information - at my other site I also recently completed a 5.6 upgrade in which my (previous) BP trained me to setup the dat and sys files in the client ODBC User DSN. That has been working without any issues, even though Accpac did create the servername32 DSN which has no password. I noted one difference in the database setup on that site is the Data Source/Server option is pointing to server as opposed to this new install which points to the Data Source.

Once again, thank you for your assistance. Now to sort out these 64bit Win7 machines!
H4

 

[Jay Converse]

Your BP is totally wrong, tell him Jay Converse said so. (Google my name with Accpac, you'll see why I said that)

 

[ettienne]

I agree with Jay, your BP is an ID10T. Only ID10Ts setup DSNs for the system and data files.