Link to home
Create AccountLog in
Avatar of IT Support
IT SupportFlag for United Kingdom of Great Britain and Northern Ireland

asked on

sage payroll legislation update on terminal server fails

User generated imageUser generated imageHi I hope you are well. thanks in advance for your help.

terminal server 2008 r2 (yes.... i know....they haven't got the funds to upgrade yet...)

I've got a big issue here. sage cloud payroll v26.1 requires an update using legislationupdate.exe. you cant log into payroll unless the update is installed, and the update wont install.

it sits there for a long time then i find the following errors on screen and the following in the application log(also see attached pictures). ive tried in both install mode and user mode(i tried installing in user mode in desperation)

Faulting application name: LegislationUpdate (1).exe, version:, time stamp: 0x57b887df
Faulting module name: ISSetup.dll, version:, time stamp: 0x57b88733
Exception code: 0xc0000005
Fault offset: 0x000525cd
Faulting process id: 0x2108
Faulting application start time: 0x01d60a55ed1ed9bc
Faulting application path: C:\Users\Administrator\Downloads\LegislationUpdate (1).exe
Faulting module path: C:\Users\ADMINI~1\AppData\Local\Temp\2\{65CC5BB5-26F5-490C-9FB2-64CF35583BAF}\Disk1\ISSetup.dll
Report Id: de57d00a-7649-11ea-a4bd-c86000e0ff58
Avatar of Hayes Jupe
Hayes Jupe
Flag of Australia image

two things

1) if you run the setup.exe from an elevated command prompt - do you get the same issue?
2) i have a feeling that it may require one of the VS runtimes.... and the required version might be missing - is there anything about that in the doco ?
Avatar of IT Support


thanks for the quick response.

i'm trying the elevated cmd prompt (putting it into install mode first) but it doesn't look promising...

will check the prerequisites after breakfast

i came accross this earlier

not sure if its relevant though...
elevated cmd fails in the same manner

there are no prerequisites at all given

just say that article too.... so... at least your not alone - but... that doesnt really help!

one other thing - are you running the setup.exe from somewhere in the appdata dir as per

i agree, its a longshot.... but.... its worth a crack.
i'm not running it from appdata, but it looks like it unpacks itself there after it is run...

there aren't any software restriction policies in place - that key is empty.

so i made a dump file  and these are the analysis  results...

Microsoft (R) Windows Debugger Version 6.3.9600.17298 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\Kev\Desktop\LegislationUpdate.DMP]
User Mini Dump File with Full Memory: Only application data is available

************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*c:\symbols*
Symbol search path is: SRV*c:\symbols*
Executable search path is:
Windows 7 Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: Server, suite: TerminalServer
Machine Name:
Debug session time: Sat Apr  4 12:35:03.000 2020 (UTC + 1:00)
System Uptime: 0 days 0:06:53.256
Process Uptime: 0 days 0:01:33.000
..................................WARNING: rsaenh overlaps cryptsp
.......WARNING: riched20 overlaps GdiPlus
00000000`74ed2e09 c3              ret
0:000> !analyze -v
*                                                                             *
*                        Exception Analysis                                   *
*                                                                             *

*** ERROR: Module load completed but symbols could not be loaded for LegislationUpdate.exe
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ISSetup.dll -
*** WARNING: symbols timestamp is wrong 0x4a5bdfe5 0x4a5bc3d5 for msiltcfg.dll
GetUrlPageData2 (WinHttp) failed: 12002.

00000000`00000000 ??              ???

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

CONTEXT:  0000000000000000 -- (.cxr 0x0;r)
rax=0000000000000001 rbx=0000000000000246 rcx=0000000000000208
rdx=0000000000000000 rsi=0000000000000208 rdi=000000000018e160
rip=0000000074ed2e09 rsp=000000000008ec08 rbp=000000000018e184
 r8=000000000000002b  r9=000000007789f9f2 r10=0000000000000000
r11=0000000000000206 r12=000000007efdb000 r13=000000000008fd20
r14=000000000008ec80 r15=0000000074ed2450
iopl=0         nv up ei pl zr na po nc
cs=0033  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00000246
00000000`74ed2e09 c3              ret

FAULTING_THREAD:  00000000000006c0


PROCESS_NAME:  LegislationUpdate.exe

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

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



APP:  legislationupdate.exe

ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre



LAST_CONTROL_TRANSFER:  from 0000000074ed2bf1 to 0000000074ed2e09

00000000`0008ec08 00000000`74ed2bf1 : 00000000`100f8ce3 00000000`74f40023 00000000`00000246 00000000`0018d9f8 : wow64cpu!CpupSyscallStub+0x9
00000000`0008ec10 00000000`74f4d286 : 00000000`00000000 00000000`74ed1920 00000000`776c3128 00000000`776fc4c1 : wow64cpu!Thunk0ArgReloadState+0x23
00000000`0008ecd0 00000000`74f4c69e : 00000000`00000000 00000000`00000000 00000000`74f44b10 00000000`7ffe0030 : wow64!RunCpuSimulation+0xa
00000000`0008ed20 00000000`776f4393 : 00000000`00244880 00000000`00000000 00000000`777f2e70 00000000`776c7550 : wow64!Wow64LdrpInitialize+0x42a
00000000`0008f270 00000000`777596e0 : 00000000`00000000 00000000`77766bdd 00000000`0008f820 00000000`00000000 : ntdll!LdrpInitializeProcess+0x17e3
00000000`0008f760 00000000`7770373e : 00000000`0008f820 00000000`00000000 00000000`7efdf000 00000000`00000000 : ntdll! ?? ::FNODOBFM::`string'+0x22770
00000000`0008f7d0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!LdrInitializeThunk+0xe

STACK_COMMAND:  ~0s; .ecxr ; kb

00000000`74ed2e09 c3              ret


SYMBOL_NAME:  wow64cpu!CpupSyscallStub+9

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: wow64cpu

IMAGE_NAME:  wow64cpu.dll


FAILURE_BUCKET_ID:  STATUS_BREAKPOINT_80000003_wow64cpu.dll!CpupSyscallStub



FAILURE_ID_HASH_STRING:  um:status_breakpoint_80000003_wow64cpu.dll!cpupsyscallstub

FAILURE_ID_HASH:  {b49b9ba3-a146-c725-bd13-e3ea7af98ea6}

Followup: MachineOwner
just an update...having spent all day since 9.30 am trying to get hold of anyone at sage, they finally answered the phone at 5pm.

conclusion - looks like they have changed the way they package their installers, leading me to believe that we were correct about it being something like the below

their phone lines are in melt down, leading me to believe that they have had a huge number of issues with it...

so i dont think theres anything to be done until they release a new version of the installer.  

im now having to go back to a client / server architecture from terminal services which is painful. but it will work.

i will keep you posted, thanks for your help so far.
Avatar of IT Support
IT Support
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
No comment has been added to this question in more than 21 days, so it is now classified as abandoned.

I have recommended this question be closed as follows:

Accept: '247computerdoctor' (https:#a43084184)

If you feel this question should be closed differently, post an objection and the moderators will review all objections and close it as they feel fit. If no one objects, this question will be closed automatically the way described above.

Experts-Exchange Cleanup Volunteer