Hey listers,
I did a search but didn't find anything on this potential bug (that or my
search fu is weak). I have a user who is ready to go to his director and
buy a vertical application rather than deal with this problem in Remedy
any longer...so any help would be appreciated.
The environment: desktop w/ core2 chipset, 1GB RAM, Windows XP Pro sp2,
ARS User tool version 7.01 patch 002.
The server is a HP DL360 running Windows Svr 2003 standard, ARServer
7.01.002 w/ Tomcat and Crystal Reports/Business Objects 11.
After upgrading to the 7.01 user tool (patch 002 - although patch 001 bugs
also), when a crystal report is called, the viewer will display the report
properly. If you click on the print icon, it will print correctly (even
if you change some of the printer preferences) one time.
The bug happens when you go to print a second time (regardless of which
record you try to print). As soon as you alter any of the preferences on
the printer (for example a different paper tray) or if you decide to print
more than one copy, the user tool will crash and terminate abnormally.
However, if on the second time you print, you change none of the
preferences or number of copies, it will function and not crash the user
tool.
The microsoft error dialog box complains about the USP10.dll. There were
three different versions on the desktop (including the one in the
activexviewer.cab for the crystal viewer). But overwriting and registering
them
all to the same updated version doesn't change anything, it still bombs.
The error capture returns the following:
NAME="usp10.dll" FILTER="GRABMI_FILTER_THISFILEONLY">
<MATCHING_FILE NAME="USP10.DLL" SIZE="325120" CHECKSUM="0x9291565F"
BIN_FILE_VERSION="1.405.2416.1" BIN_PRODUCT_VERSION="1.405.2416.1"
PRODUCT_VERSION="1.0405.2416.1" FILE_DESCRIPTION="Uniscribe Unicode script
processor" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft(R)
Uniscribe Unicode script processor" FILE_VERSION="1.0405.2416.1
(lab06_N.010104-1344)" ORIGINAL_FILENAME="Uniscribe"
INTERNAL_NAME="Uniscribe" LEGAL_COPYRIGHT="Copyright (C) Microsoft
Corporation. 1981-2000" VERFILEDATEHI="0x0" VERFILEDATELO="0x0"
VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32"
PE_CHECKSUM="0x56CF5" LINKER_VERSION="0x50001"
UPTO_BIN_FILE_VERSION="1.405.2416.1"
UPTO_BIN_PRODUCT_VERSION="1.405.2416.1" LINK_DATE="01/06/2001 05:14:26"
UPTO_LINK_DATE="01/06/2001 05:14:26" VER_LANGUAGE="English (United States)
[0x409]" />
<EXE NAME="kernel32.dll" FILTER="GRABMI_FILTER_THISFILEONLY">
<MATCHING_FILE NAME="kernel32.dll" SIZE="984064" CHECKSUM="0xF12E1D4A"
BIN_FILE_VERSION="5.1.2600.2945" BIN_PRODUCT_VERSION="5.1.2600.2945"
PRODUCT_VERSION="5.1.2600.2945" FILE_DESCRIPTION="Windows NT BASE API
Client DLL" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft
Windows Operating System" FILE_VERSION="5.1.2600.2945 (xpsp_sp2_gdr.060704-
2349)" ORIGINAL_FILENAME="kernel32" INTERNAL_NAME="kernel32"
LEGAL_COPYRIGHT=" Microsoft Corporation. All rights reserved."
VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x40004"
VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0xF724D"
LINKER_VERSION="0x50001" UPTO_BIN_FILE_VERSION="5.1.2600.2945"
UPTO_BIN_PRODUCT_VERSION="5.1.2600.2945" LINK_DATE="07/05/2006 10:55:00"
UPTO_LINK_DATE="07/05/2006 10:55:00" VER_LANGUAGE="English (United States)
[0x409]" />
It sounds crazy but is there something in the way XP handles print
spooling that it would work once but not twice? I'm actually in the middle
of regression testing starting with a virgin copy of XP SP2 and the User Tool.
I am installing each of our standard applications and then testing the print
functionality.
Have any of you seen this after upgrading to 7.01?
TIA,
Carina Burns
Richardson ISD
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the
Answers Are"
