Invalid Print Command [solved]

Discussion forum about all things Report Builder (all versions).
ursamajor

Invalid Print Command [solved]

Post by ursamajor » 23 Dec 2010, 13:14

A customer upgraded his office with new 64 bit windows 7 pc's.
Since then they randomly get an error: "Invalid Print Command" when printing from our application (multi.exe).
Before when they had windows XP 32 bit (same application) they had no problem at all.
I have a memorydump from the moment when this error is on screen, if it helps...

What is the problem here?
invalidPrintCommand.png
You do not have the required permissions to view the files attached to this post.

ursamajor
Netherlands
Posts: 44
Joined: 23 Aug 2019, 11:10
Location: Sliedrecht, The Netherlands

Invalid Print Command [solved]

Post by ursamajor » 23 Dec 2010, 16:41

Here is the analysis.

Code: Select all

0:000> !analyze -v
*******************************************************************************
*                                                                             *
*                        Exception Analysis                                   *
*                                                                             *
*******************************************************************************

*** ERROR: Module load completed but symbols could not be loaded for MULTI.EXE
*** WARNING: symbols timestamp is wrong 0x4a5bdfdd 0x4a5bc3d5 for msiltcfg.dll
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for Codejock.CommandBars.v12.0.2.ocx - 
*** WARNING: symbols timestamp is wrong 0x4a5be0bf 0x4a5bdb4b for winspool.drv
GetPageUrlData failed, server returned HTTP status 404
URL requested: http://watson.microsoft.com/StageOne/MULTI_EXE/0_0_0_0/45a545ac/unknown/0_0_0_0/bbbbbbb4/80000003/00000000.htm?Retriage=1

FAULTING_IP: 
+595f2faf0403de88
00000000`00000000 ??              ???

EXCEPTION_RECORD:  ffffffffffffffff -- (.exr 0xffffffffffffffff)
ExceptionAddress: 0000000000000000
   ExceptionCode: 80000003 (Break instruction exception)
  ExceptionFlags: 00000000
NumberParameters: 0

FAULTING_THREAD:  000000000000167c

DEFAULT_BUCKET_ID:  STATUS_BREAKPOINT

PROCESS_NAME:  MULTI.EXE

OVERLAPPED_MODULE: Address regions for 'msvcp60' and 'OLECLI32' overlap

ERROR_CODE: (NTSTATUS) 0x80000003 - {EXCEPTION}  Breakpoint  A breakpoint has been reached.

EXCEPTION_CODE: (HRESULT) 0x80000003 (2147483651) - One or more arguments are invalid

MOD_LIST: <ANALYSIS/>

NTGLOBALFLAG:  0

APPLICATION_VERIFIER_FLAGS:  0

PRIMARY_PROBLEM_CLASS:  STATUS_BREAKPOINT

BUGCHECK_STR:  APPLICATION_FAULT_STATUS_BREAKPOINT

LAST_CONTROL_TRANSFER:  from 00000000746b2d92 to 00000000746b2dd9

STACK_TEXT:  
00000000`0008ebf8 00000000`746b2d92 : 00000000`74fe0e8f 00000000`74720023 00000000`00000206 00000000`0018b3dc : wow64cpu!CpupSyscallStub+0x9
00000000`0008ec00 00000000`7472d07e : 00000000`00000000 00000000`746b1920 00000000`0008ee90 00000000`76f93831 : wow64cpu!Thunk0Arg+0x5
00000000`0008ecc0 00000000`7472c549 : 00000000`00000000 00000000`00000000 00000000`74724ac8 00000000`7ffe0030 : wow64!RunCpuSimulation+0xa
00000000`0008ed10 00000000`76fa82c8 : 00000000`002f3290 00000000`00000000 00000000`77093670 00000000`770654a0 : wow64!Wow64LdrpInitialize+0x429
00000000`0008f260 00000000`76fa7423 : 00000000`00000000 00000000`76fa8f81 00000000`76f60000 00000000`00000000 : ntdll!LdrpInitializeProcess+0x17e2
00000000`0008f760 00000000`76f92e2e : 00000000`0008f820 00000000`00000000 00000000`7efdf000 00000000`00000000 : ntdll! ?? ::FNODOBFM::`string'+0x2bd60
00000000`0008f7d0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!LdrInitializeThunk+0xe


STACK_COMMAND:  ~0s; .ecxr ; kb

FOLLOWUP_IP: 
wow64cpu!CpupSyscallStub+9
00000000`746b2dd9 c3              ret

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  wow64cpu!CpupSyscallStub+9

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: wow64cpu

IMAGE_NAME:  wow64cpu.dll

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5be125

FAILURE_BUCKET_ID:  STATUS_BREAKPOINT_80000003_wow64cpu.dll!CpupSyscallStub

BUCKET_ID:  X64_APPLICATION_FAULT_STATUS_BREAKPOINT_wow64cpu!CpupSyscallStub+9

WATSON_STAGEONE_URL:  http://watson.microsoft.com/StageOne/MULTI_EXE/0_0_0_0/45a545ac/unknown/0_0_0_0/bbbbbbb4/80000003/00000000.htm?Retriage=1

Followup: MachineOwner
---------

And some environment info:

Code: Select all

0:000> !peb
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: wow64!TEB32                                   ***
***                                                                   ***
*************************************************************************
PEB at 000000007efdf000
    InheritedAddressSpace:    No
    ReadImageFileExecOptions: No
    BeingDebugged:            No
    ImageBaseAddress:         0000000000400000
    Ldr                       0000000077093640
    Ldr.Initialized:          Yes
    Ldr.InInitializationOrderModuleList: 00000000002f2d00 . 00000000002f32b0
    Ldr.InLoadOrderModuleList:           00000000002f2bf0 . 00000000002f3650
    Ldr.InMemoryOrderModuleList:         00000000002f2c00 . 00000000002f3660
            Base TimeStamp                     Module
          400000 45a545ac Jan 10 20:59:40 2007 C:\Program Files (x86)\UNIT4\UNIT4 Multivers\Bin\N\multi.exe
        76f60000 4ba9b802 Mar 24 07:58:10 2010 C:\Windows\SYSTEM32\ntdll.dll
        74720000 4b3083e3 Dec 22 09:31:31 2009 C:\Windows\SYSTEM32\wow64.dll
        746c0000 4a5be127 Jul 14 03:36:39 2009 C:\Windows\SYSTEM32\wow64win.dll
        746b0000 4a5be125 Jul 14 03:36:37 2009 C:\Windows\SYSTEM32\wow64cpu.dll
    SubSystemData:     0000000000000000
    ProcessHeap:       00000000002f0000
    ProcessParameters: 00000000002f1fd0
    CurrentDirectory:  'C:\Windows\'
    WindowTitle:  'C:\Users\person\AppData\Roaming\Microsoft\Internet Explorer\Quick Launch\User Pinned\TaskBar\UNIT4 Multivers Nederlands (2).lnk'
    ImageFile:    'C:\Program Files (x86)\UNIT4\UNIT4 Multivers\Bin\N\multi.exe'
    CommandLine:  'multi.exe '
    DllPath:      'C:\Program Files (x86)\UNIT4\UNIT4 Multivers\Bin\N;C:\Windows\system32;C:\Windows\system;C:\Windows;.;C:\Program Files\Common Files\Microsoft Shared\Windows Live;C:\Program Files (x86)\Common Files\Microsoft Shared\Windows Live;C:\Program Files (x86)\UNIT4\UNIT4 Multivers\Bin\;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\UNIT4\UBC;C:\Program Files (x86)\Windows Live\Shared'
    Environment:  00000000002f1320
        =::=::\
        ALLUSERSPROFILE=C:\ProgramData
        APPDATA=C:\Users\person\AppData\Roaming
        CommonProgramFiles=C:\Program Files\Common Files
        CommonProgramFiles(x86)=C:\Program Files (x86)\Common Files
        CommonProgramW6432=C:\Program Files\Common Files
        COMPUTERNAME=PC02
        ComSpec=C:\Windows\system32\cmd.exe
        FPPUILang=en-US
        FP_NO_HOST_CHECK=NO
        HOMEDRIVE=C:
        HOMEPATH=\Users\person
        LOCALAPPDATA=C:\Users\person\AppData\Local
        LOGONSERVER=\\W2K-SERVER02
        NUMBER_OF_PROCESSORS=4
        OnlineServices=Online Services
        OOBEUILang=nl-NL
        OS=Windows_NT
        Path=C:\Program Files\Common Files\Microsoft Shared\Windows Live;C:\Program Files (x86)\Common Files\Microsoft Shared\Windows Live;C:\Program Files (x86)\UNIT4\UNIT4 Multivers\Bin\;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\UNIT4\UBC;C:\Program Files (x86)\Windows Live\Shared
        PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC
        Platform=BPC
        PROCESSOR_ARCHITECTURE=AMD64
        PROCESSOR_IDENTIFIER=Intel64 Family 6 Model 37 Stepping 5, GenuineIntel
        PROCESSOR_LEVEL=6
        PROCESSOR_REVISION=2505
        ProgramData=C:\ProgramData
        ProgramFiles=C:\Program Files
        ProgramFiles(x86)=C:\Program Files (x86)
        ProgramW6432=C:\Program Files
        PSModulePath=C:\Windows\system32\WindowsPowerShell\v1.0\Modules\
        PUBLIC=C:\Users\Public
        SESSIONNAME=Console
        SystemDrive=C:
        SystemRoot=C:\Windows
        TEMP=C:\Users\WC0BA~1.HOE\AppData\Local\Temp
        TMP=C:\Users\WC0BA~1.HOE\AppData\Local\Temp
        USERDNSDOMAIN=COMPANY.LOCAL
        USERDOMAIN=COMPANY
        USERNAME=person
        USERPROFILE=C:\Users\person
        windir=C:\Windows

(I renamed the username here...)

Jeff Luther

Invalid Print Command [solved]

Post by Jeff Luther » 27 Dec 2010, 18:31

Well, TD/RB v4.1 was not certified to be compatibile with Win7 64-bit. Based on the 'help' provided you are passing a set of cmd. line parameters for printing?

My suggestion is that you try to duplicate the problem on your own PC with Win7 64-bit and if you can, to then try to come up with a coding workaround/change solution that does not generate this error. I haven't heard of this problem before, maybe someone else here has?

What is odd is that:
they randomly get an error: "Invalid Print Command" when printing from our application
so that might need to be looked at. It would seem to me that either Print works or does not (if it is incompatible with Win7 64-bit). But "randomly" seems to indicate there is something else going on beyond basic incompatibility. In this case, I would want to have the customer try to narrow down when "randomly" occurs. Number of users?, printer being printed to?

ursamajor

Invalid Print Command [solved]

Post by ursamajor » 21 Jan 2011, 14:28

It seems that the printspooler is involved.
Our customer noted that when the printspooler hangs and is restarted (or when it's crashed), this error appears when printing.
So, I think this one is solved!

Return to “General Discussion”

Who is online

Users browsing this forum: [Ccbot] and 0 guests