Windows 7 Installation Problems for A1Law

Over the weekend my staff and I installed several new PCs at my office. The A1 program wouldn't load correctly after running the "A1Setup.exe" program (we're using version 6.x of the application).

After paying my two techs for two full days to migrate my server (literally $2000 out of pocket -- a little extra to make this happen over the weekend, of course, not to mention another $2K for a new server rig from Dell), I was pretty frustrated at watching them bang their heads against the wall on this for two hours. I watched as they talked about "security descriptors" and "dependency checks", installed, cleared, restarted, toyed with virus protection settings, etc., for quite some time.

This is the support request we eventually sent to Mike Appell:

OS: Windows 7 Pro. Brand new installation on a new PC. Other software: MS Office 2007, Firefox, Microsoft Security Essentials, all windows update options.
Firm: (xxxxxxxxxx).

Issue:

After initial setup (again, fresh, no C:\lawlocal folder yet), we run the A1Setup.exe app -- it says it's v 6.00.
1. Register controls process hangs at "Registering C:\lawlocal\Controls\vfp9r.dll"
2. After about 20 seconds, Windows reports that "Microsoft Register Server has stopped working". The error out put is below.

Tried:

+ Enabling all User Account Control limitations (prompt on install, etc)
+ Disabling all virus protection (ms security essentials)

Please help. This is urgent as we have just upgraded several workstations over the weekend and we need them operational for Monday morning.

Thanks.
--------
This is the error text from Windows itself:

Files that help describe the problem:
C:\Users\File Room\AppData\Local\Temp\

WER8FD1.tmp.WERInternalMetadata.xml
C:\Users\File Room\AppData\Local\Temp\WERCEE4.tmp.appcompat.txt
C:\Users\File Room\AppData\Local\Temp\WERCF14.tmp.mdmp

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

This is the content in WERInternalMetadata.xml:
--

xml version="1.0" encoding="UTF-16" ?>

- <WERReportMetadata>

- <OSVersionInformation>

<WindowsNTVersion>6.1WindowsNTVersion>

<Build>7600Build>

<Product>(0x30): Windows 7 ProfessionalProduct>

<Edition>ProfessionalEdition>

<BuildString>7600.16539.x86fre.win7_gdr.100226-1909BuildString>

<Revision>1Revision>

<Flavor>Multiprocessor FreeFlavor>

<Architecture>X86Architecture>

<LCID>1033LCID>

OSVersionInformation>

- <ParentProcessInformation>

<ParentProcessId>912ParentProcessId>

<ParentProcessPath>C:\LawLocal\law.exeParentProcessPath>

<ParentProcessCmdLine>C:\LAWLOCAL\law.exe 1 VLSParentProcessCmdLine>

ParentProcessInformation>

- <ProblemSignatures>

<EventType>APPCRASHEventType>

<Parameter0>regsvr32.exeParameter0>

<Parameter1>6.1.7600.16385Parameter1>

<Parameter2>4a5bca28Parameter2>

<Parameter3>vfp9r.dllParameter3>

<Parameter4>9.0.0.7423Parameter4>

<Parameter5>49a31c32Parameter5>

<Parameter6>c0000005Parameter6>

<Parameter7>000149e5Parameter7>

ProblemSignatures>

- <DynamicSignatures>

<Parameter1>6.1.7600.2.0.0.256.48Parameter1>

<Parameter2>1033Parameter2>

<Parameter22>0a9eParameter22>

<Parameter23>0a9e372d3b4ad19135b953a78882e789Parameter23>

<Parameter24>0a9eParameter24>

<Parameter25>0a9e372d3b4ad19135b953a78882e789Parameter25>

DynamicSignatures>

- <SystemInformation>

<MID>2A1ED726-F383-4401-BB81-37745DB087EEMID>

<MarkerFile>1028_Dell_VOS_230</MarkerFile>

<SystemManufacturer>Dell Inc.SystemManufacturer>

<SystemProductName>Vostro 230SystemProductName>

<BIOSVersion>1.0.0BIOSVersion>

SystemInformation>

WERReportMetadata>

-----------------------------
This is the content in 'appcompat.txt':
--



16385" BIN_PRODUCT_VERSION="6.1.7600.16385" PRODUCT_VERSION="6.1.7600.16385" FILE_DESCRIPTION="Windows NT BASE API Client DLL" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft® Windows® Operating System" FILE_VERSION="6.1.7600.16385 (win7_rtm.090713-1255)" ORIGINAL_FILENAME="kernel32" INTERNAL_NAME="kernel32" LEGAL_COPYRIGHT="© Microsoft Corporation. All rights reserved." VERDATEHI="0x0" VERDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0xD5597" LINKER_VERSION="0x60001" UPTO_BIN_FILE_VERSION="6.1.7600.16385" UPTO_BIN_PRODUCT_VERSION="6.1.7600.16385" LINK_DATE="07/14/2009 01:09:01" UPTO_LINK_DATE="07/14/2009 01:09:01" EXPORT_NAME="KERNEL32.dll" VER_LANGUAGE="English (United States) [0x409]" EXE_WRAPPER="0x0" />
16385" BIN_PRODUCT_VERSION="6.1.7600.16385" PRODUCT_VERSION="6.1.7600.16385" FILE_DESCRIPTION="NT Layer DLL" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft® Windows® Operating System" FILE_VERSION="6.1.7600.16385 (win7_rtm.090713-1255)" ORIGINAL_FILENAME="ntdll.dll.mui" INTERNAL_NAME="ntdll.dll" LEGAL_COPYRIGHT="© Microsoft Corporation. All rights reserved." VERDATEHI="0x0" VERDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x14033F" LINKER_VERSION="0x60001" UPTO_BIN_FILE_VERSION="6.1.7600.16385" UPTO_BIN_PRODUCT_VERSION="6.1.7600.16385" LINK_DATE="07/14/2009 01:09:47" UPTO_LINK_DATE="07/14/2009 01:09:47" EXPORT_NAME="ntdll.dll" VER_LANGUAGE="English (United States) [0x409]" EXE_WRAPPER="0x0" />


THISFILEONLY">
7423" PRODUCT_VERSION="9.0.00.7423" FILE_DESCRIPTION="Microsoft Visual FoxPro 9.0 SP2 Runtime Library" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft Visual FoxPro" FILE_VERSION="9.0.00.7423" ORIGINAL_FILENAME="VFP9R" INTERNAL_NAME="VFP9R" LEGAL_COPYRIGHT="Copyright© Microsoft Corporation 1988-2005. All rights reserved." VERDATEHI="0x0" VERDATELO="0x0" VERFILEOS="0x4" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x4896BC" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="9.0.0.7423" UPTO_BIN_PRODUCT_VERSION="9.0.0.7423" LINK_DATE="02/23/2009 21:59:14" UPTO_LINK_DATE="02/23/2009 21:59:14" EXPORT_NAME="VFP9R.dll" VER_LANGUAGE="English (United States) [0x409]" EXE_WRAPPER="0x0" />

This is the reply we got back, which, to Mr. Appell's credit, did reach us later that same Sunday evening:

Click Start, Accessories and then RIGHT CLICK on command and click Run as administrator.

Next type cd\lawlocal\controls

Then type REGALL1

Click OK as it should say SUCCESS each time you click OK.

Once it is done click EXIT. Next open Computer or My Computer then RIGHT CLICK on LAWLOCAL and click SECURITY and be sure to click ALLOW where it displays FULL CONTROL. Do this for each group in the list.

Mike

There are some minor corrections my techs were able to make to these instructions -- the Windows 7 interface is different from what is described -- but this did indeed allow operations to resume Monday morning.

The "register controls" widget within A1 itself still doesn't work right, but we can get around this by running through these command line instructions every time we do an upgrade.

Hope this helps someone else out there.