Sage 50cloud accounts / Line 50 closes after password screen. After upgrade from v26 to v28

Another Sage problem.

The same old crap – program disappears after the splash screen, or after entering your password. In this case it was after entering password.

Only this time, the cause, or at least the fix, was different. After an hour of pissing about re-installing, rebooting, deleting everything I could find related to Sage, re-installing again, etc., I remembered the dot-net trick, gave it a go, and whaddaya know, it worked.

The fix, is to go into Windows’ Programs and Features, then Turn Windows features on or off, and turn off .NET Framework 3.5, and also 4.8. Let that take effect, reboot, then turn them back on.

Jobs a goodun.

Do yourself a favour and move to Xero.

Sage 50 Data Access will not install. Fails & rolls back at ODBC stage.

The machine is a terminal server. Windows Server 2012 a.k.a. Windows 8.

These are the MSI log lines of interest. Specifically the ‘wrong context’.

MSI (s) (88:A4) [11:25:47:730]: Created Custom Action Server with PID 5344 (0x14E0).
MSI (s) (88:A8) [11:25:47:754]: Running as a service.
MSI (s) (88:A8) [11:25:47:757]: Custom Action Server rejected - Wrong Context
MSI (s) (88:A4) [11:25:47:760]: CA Server Process has terminated.
MSI (s) (88:BC) [11:25:47:760]: Failed to get IMsiCustomAction*
11/05/2021 11:25:47.761 [7048]: Assembly Install: Failing with hr=80070005 at RemoveDirectoryAndChildren, line 393

Custom MSI actions & terminal server wrong context is a known thing apparently, introduced as an issue around Windows 7 / Server 2008 times with some updates to Windows Installer.
The issue seems particularly common with ODBC related packages, and I suspect this is because there are separate User and System contexts for ODBC configurations. Something is getting confused somewhere.

People say to revert various Windows Updates to downgrade the Windows Installer version.
Unfortunately none of that could be applied here for this Server 2012 machine – all the discussion I found was around Server 2008 / Windows Vista/7.

The other suggested workaround of using psexec did work though, and after a day of fighting this, it will do.

psexec -s -i msiexec /i "c:\users\administrator\Downloads\Sage Accounts 27_2\packages\Sage50Accounts_DataAccess.msi"

Don’t forget you need the full path, because the task runs in a new session / environment as the system account, and will not have the current working directory as its working directory.

If you are installing the whole thing rather than just the DataAccess components, leave off the msiexec /i and just call the installer executable:

psexec -s -i  "c:\users\administrator\Downloads\Sage Accounts 27_2\install.exe"

LINX 12×64 tablet PC cameras not working, BIOS settings kaput, etc.

No it’s not the Windows drivers! The BIOS (UEFI) configuration utility on these things is not built to match the hardware at all. In fact it is wide-open with all the options that the original BIOS-software-supplier has available – most options that are not valid choices for the actual machine at all. A hackers dream perhaps, but a nightmare on this occasion.

Whatever you do, do not do a ‘load defaults’, because you’ll lose the LCD display as well!

If you do lose the LCD display, you’ll need to buy a micro-HDMI to HDMI adapter cable, so that you can plug a big HDMI screen or TV into the tablet, and get back into the BIOS setup, from where you can set the LCD-out to EDP, instead of MIPI or whatever it’s been accidentally set to.

Now, forgetting the above, and even knowing that the problem with the cameras is actually down to the configuration options in the BIOS setup utility, I still could not get the cameras going! There are too many options. It’s not just the list of cameras (front: 6 different camera types, rear: 8 different camera types, or vice-versa), there is more to it than that. I suspect some kind of multiplexer or GPIO module which allows the switching between front/rear camera.. yet more options to which we don’t know the correct setup.

As luck would have it, somebody from LINX / Exertis responded to my email request for help – which was a surprise because their auto-responder said that they would only help with in-warranty requests for hardware support. I had given up hope, but a week or so after my initial email, I received a helpful response from Mr Moores at Exertis, with links to an updated BIOS for the machine, and the promise that loading this would apply all the correct settings for the machine, for camera, and other things that probably weren’t working correctly but had yet to come to light. It also purportedly improves WiFi with Windows 10.

I tried it, and it worked!

You can find the file here.

Windows failed to start because a required driver is missing or corrupt: vmbus.sys

Upgrading Server 2003 to 2008, with Hyper-V Integration Services installed, results in this boot failure after a few hours :-/

In hindsight, you should remove integration services first.

Without the benefit of hindsight:

  • Shut down the virtual machine.
  • Using Computer Management -> Disk Management on the Hyper-V host, attach the .VHD file, so that you are mounting the virtual HD of the affected guest.
  • Ensure your Windows Explorer is set to show hidden & system files.
  • Open up regedit, then go to HKLM.
  • File -> Load Hive
  • Browse to the virtual HD -> Windows -> System32 -> Config
  • Choose the ‘SYSTEM’ hive, and when prompted for a name, type ‘broken’, or the name of the machine or something, and press enter.
  • The affected VM machine’s registry is now showing under HKLM->’broken’.
  • Browse to ControlSet001 (do the same for 002, etc.), \Services\vmbus
  • Delete the whole vmbus key (folder).
  • When done, highlight ‘broken’ (where the registry is attached to), and go to File -> Unload Hive.
  • Then go back to disk management and detach the VHD.
  • Try to start the VM so that the final stage of the in-place upgrade can continue.

After the upgrade finishes, you will probably have no networking, no mouse, and other issues.

You should try (sans-mouse) to switch the HAL from ACPI to APIC (as per here)*. Upon reboot, the vmbus issue may return (did it re-install itself?), and so have to repeat the above procedure.
Once the system has booted up with an APIC HAL, you can try to re-install Integration Services properly.

Fingers crossed :-*

(*incidently, I am all done now – the system is working just fine. I had to re-install the integration services, but device manager still shows an ACPI HAL for me. This is x86 Server 2008 (upgraded from 2003). A very temporary measure).

Hint: if the special function keys (start menu, ctrl-esc, alt-tab, etc), are not passing through to the guest: Ctrl-Alt-End will get you to task manager, from there Alt-F -> Run, cmd to open up a command prompt, from the command prompt: taskkill /im taskmgr.exe so that you can get rid of the always-on-top taskmgr that’s in the way, then do your stuff. sysdm.cpl for system properties/device manager, etc.

Citrix ShareFile Migration Tool, Drive Mapper and other rubbish.

(UKFast FastDrive is Citrix ShareFile rebranded and using a StorageZone at the UKFast datacentre.)

Frustrating is the word. It’s not a good start when even the basics are totally wrong and broken 🙁

Some other general ShareFile and SFMT problems:

  • SFMT misses files and folders.
  • It crashes every time you close it.
  • Setting up a migration and setting a schedule doesn’t seem to work properly and certainly isn’t intuitive, if working at all. I gave up.
  • Pausing / cancelling a transfer that you just set up but told to run on a schedule seems to kill the schedule or something. It basically just doesn’t work.
  • The metrics – ETA, number of items to do / done makes no sense (see above picture)
  • It says it supports Server 2008, but, along with the other tools, required Dot Net 4.6.2 which isn’t possible on Server 2008. So anybody moving from Server 2008 or SBS 2008 to ShareFile will have to use a workstation to migrate all the data.

So, you try plan b – some sort of File sync utility to the ShareFile mapped drive. This appears to complete, but nope, there’s 10 gigs of stuff still missing in ShareFile!


Further to this, the ShareFile Drive Mapper allows you to specify (via Group Policy) an AccountSubdirectory. You can set this to your main root SF Shared folder, e.g. ‘Data’. You would then think that the mapped drive would show the contents of this folder, but nope – even though the Drive itself shows with the label ‘Data’, when you click into it, you are shown a folder called ‘Data’. So it is showing the shared folder within the shared folder. It’s basically completely stupid and useless.

The only way around this I have found is to make the MountLocation something like %userprofile%\ShareFile , and run subst X: %userprofile%\ShareFile\Data in everybody’s login script.
In fact – it’s not even as simple as that (subst in the login script is a no-go). Instead, the login script must copy a script (e.g. sharefile.cmd) to “%appdata%\microsoft\windows\start menu\programs\startup”. This will then cause Windows Explorer to run the subst command in the correct user context.

sharefile.cmd looks like this:

@echo off
REM this causes the script to re-open itself, but minimised.
if not defined IS_MINIMISED set IS_MINIMISED=1 && start "" /min "%~dpnx0" %* && exit

net use t: /del /y
if not exist "%userprofile%\ShareFile" mkdir "%userprofile%\ShareFile"

echo Waiting for ShareFile to mount at %userprofile%\ShareFile
ping localhost -n 2 >NUL 
if not exist "%userprofile%\ShareFile\Data" goto startloop

echo Doing Subst for drive T: to ShareFile folder
subst t: "%userprofile%\ShareFile\Data"



None of this should be necessary – it’s pretty poor all round really. We’ll see how the go-live goes on Monday.

Update: The rollout was eventful and a followup to this post is forthcoming!

notes to self in case I forget: DriveMapper confirmed as a total fail by about midday of day-two. New files not appearing even 45 mins after creation by colleagues, even though saved ~20 plus times by the creator (as per version history in ShareFile web GUI – so we know the saves are making it up to the cloud, but the change notification to other clients is either broken or (could it even be? would they dare???) simply does not exist). Confirmed not caused by subst workaround. Users can’t create new folders because explorer’s default/initial temporary new folder name of ‘New Folder’ already existed, but wasn’t showing so explorer tried to create same folder as already-existing, instead of its usual trick of making a ‘New Folder (2)’. This resulted in an Access Denied error that made no sense. Citrix Files Beta (which isn’t even available to this customer but I happened to find it via a random popup at another customer) seems to: resolve the issue around mapping to a shared folder (no subst needed any more), and also in my testing seems to show up new creates/saves/deletes from one PC to another in near real-time (couple of seconds).. Should I be having to install beta software to make this thing work though? DriveMapper uninstall on win10 leaves behind explorer namespace, had to create a [-HKCU blah] reg file to delete it en masse, as well as undo all my previous logon script / subst work. Must also rant about the need to use Group Policy to customise anything worthwhile. The whole point of this is to become serverless/decentralised, yet I need to import the policy definitions, make policies (which I can’t do on server 2008 because the templates aren’t compatible with the group policy editor, so I have to install remote server admin tools onto a workstation), and *then* (sheesh) I can export the policy from the registry, to import onto non-domain-joined PCs, just so that Citrix Files Beta will mount ‘Shared Folders\Data’ to the letter T:
F.U.C.K.  .M.E.

Taking control of gadgets!

In my search for a nice display with housing for my datalogger project, I came across the Autool X50 and X60 OBD2 gauge / code reader gadget (pod and gauge style respectively).

I bought them, in the hope that there might be something usable inside – a recognisable display panel or controller or something. I’m not interested in the OBD or automotive aspects of these devices, because I have already built a separate, more rugged ECU datalogger. I just wanted a display, but what I really wanted, was a display inside a gauge. I’ve only been able to get my hands on the X50 so far. The X60 gauge style version is on its way from China.

What I found inside was a GigaDevices GD32F103RBT6, 2MB flash eeprom, an LM393 for K/L line, an NXP CAN bus transceiver, and with the help of the guys on the forums, the TFT panel and its controller were identified.

After some experimentation, the key components are all working with stm32duino.

There was some trouble getting the TFT LCD going. It turned out that the pin used for the TFT RST was claimed by JTAG by default, and the pin used for TFT D/C (data/command select) was claimed by USB in the maple / stm32duino base code, so workarounds were needed for these things.

Also the display controller (ST7789V), whilst working great with the ILI9341_STM library, does require MADCTL_BGR changing to MADCTL_RGB in Adafruit_ILI9341_STM::setRotation(uint8_t m)

The discussion thread is here.

and here’s a happy picture. The MCU is clocked at 128MHz here, which increases the SPI clock from the default 18MHz to the 32MHz that you can see here.

Sage Accounts v22 (2016) will not open. Splash screen flashes by.

Another month, another half day wasted on Sage problems. I’ve had this problem at a few sites, mostly accountancy practices, some of which use ADM / Client Account Manager and multiple versions of Sage Accounts.

The fix was to find SDBDesktopUpdateInstaller.msi in %temp%\SageAccounts\Q3Update. Right-click -> Uninstall, and then Right-click -> Install.
You may need to install the v22 ‘May Improvements’ before this works. YMMV. I’ve had enough of Sage. I now advise my customers to move away as soon as possible. Report designer problems, updates not updating, emails not emailing, data service screwing up both file servers and end user machines by backing-up gigabytes of user profile data instead of just Sage data at 5pm every night, and now to top it off, Sage 50 Data Service isn’t even compatible with / supported on Small Business or Essentials servers. What market are they targeting exactly? Don’t forget Sage isn’t compatible with / supported on Office 365 either (a.k.a. you will be fobbed off and on your own when report designer emails break again). I look forward to the day Sage are a dead and buried legacy.

FYI last month a huge amount of time was spent on a Report Designer issue with Accounts v23. It appeared that the Data Source was locked to ‘SageLine50v13’, as the reports failed to run, citing that data source as being missing, and it was not possible to change the data source from SageLine50v13 in any reports either (the dialog box’s Save Changes button was not clickable). I told the customer that it looked like they might have restored reports from a v13 client which needed updating, or maybe to set the reports path to local rather than data files location. That didn’t work, so I advised they make use of their Sage Cover support contract, since I only charge this client £100 per month for mostly-everything IT service and support. Sage advised the client that the computer was corrupt and needed a full re-format and reinstall. Given that it was a new computer a few weeks earlier and had Sage installed from a new v24 ADM disk, I disputed this, but was nonetheless left to try to work it out. After 6 – 8 hours of pissing about, I happened upon this Sage article. I had searched for the term SageLine50v13 a week earlier and found nothing, so who knows when this article was published?

My advice to Sage users is that it’s a nightmare to support and very prone to failure. There are thankfully many alternatives available now. Xero works for me.

The two biggest mistakes Sage ever made in my opinion, apart from getting involved in ACT!, were to introduce the Sage Business Desktop / SBD central-launcher/common-platform/whatever-the-hell-it-is thing, and the SData service and its follow-ups. Neither of these things have been beneficial to the end user. Both of them have had a gigantic net-negative impact.