Using Salesware with Microsoft's 64-Bit Operating Systems – Known
Using Salesware with Microsoft’s 64-bit operating systems – known issues
Overview
Salesware works on 64-bit operating systems.
Nearly every new computer you buy now is “64-bit” – Core 2 Duo processors, any Intel processor that has a “D” like Pentium D or Celeron D, all the AMD processors.
Differences in the registry
Because Salesware applications are 32-bit applications, they run under something called WOW64 (Windows-on-Windows 64-bit), which is an emulator allowing 32-bit applications to run on a 64-bit operating system. To the user, this is quite transparent, but for support you should be aware of the following: • 32-bit applications are installed in a folder called ‘Program Files (x86)’. You will therefore find the ‘Siriusware’ folder here on a 64-bit PC instead of in ‘Program Files’, which contains 64-bit applications. • 32-bit system files are installed in ‘Windows\SysWOW64’ instead of ‘Windows\System32’, which contains 64-bit files. • 32-bit registry entries are written to a registry key called ‘Wow6432Node’. You will therefore find the ‘Siriusware’ key in ‘HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node’. • 32-bit ODBC registry entries are found in ‘Wow6432Node’ too. This makes things particularly interesting because after an install, you will see no System DSNs at all when you view ODBC Data Sources. Why not? Because you are only looking at 64-bit data sources. Yet our application works, because the install creates a 32-bit System DSN. To see 32-bit data sources, you must run the 32-bit ODBC data source application (C:\WINDOWS\SysWOW64\odbcad32.exe). Using ‘Control Panel/Administrative Tools/Data Sources (ODBC)’ to add a System DSN called SiriusSQL adds a 64-bit data source with does not appear to work with our applications. This only confuses things because it appears as if you have a working ODBC connection. You must add/configure ODBC data sources using the 32- bit data source application.
To get RentEZ up and running on a Windows Server 2008 64-bit machine, you will encounter a problem. The problem was that the registry keys for a 32-bit application have a different registry path, as noted above. It has an extra “Wow6432Node” in the registry path as seen below:
1
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Siriusware]
.NET 1.1 on 64-bit computers
You need to perform an addition step to get Self Entry/ww.dll to work on 64-bit computers running Windows Server 2003. .NET 1.1 works only in 32 bit mode, so one has to enable that and then install asp.net 1.1.4322. The link to this info is http://support.microsoft.com/kb/894435
The following are the instructions from that link: ASP.NET 1.1, 32-bit version To run the 32-bit version of ASP.NET 1.1, follow these steps: 1. Click Start, click Run, type cmd, and then click OK. 2. Type the following command to enable the 32-bit mode: cscript %SYSTEMDRIVE%\inetpub\adminscripts\adsutil.vbs SET W3SVC/AppPools/Enable32bitAppOnWin64 1
3. Type the following command to install the version of ASP.NET 1.1 and to install the script maps at the IIS root and under:
%SYSTEMROOT%\Microsoft.NET\Framework\v1.1.4322\aspnet_regiis.exe -i
4. Make sure that the status of ASP.NET version 1.1.4322 is set to Allowed in the Web service extension list in Internet Information Services Manager.
Installing the SiriuswarePDF driver
During installation of Common Files, installation of the SiriuswarePDF driver fails. To fix this, after you install Common Files:
Note: Steps 1 – 3 are not required with the most recent version of the Common Files installer because the .dlls are installed. You will know you have the most recent version if those files are already in the directory specified in step #2.
1. Get the acfpdfuamd64.dll and acfpdfuiamd64.dll files from Siriusware Technical Support. 2. Drop the two .dlls in C:\Program Files (x86)\Siriusware\PDF
2
3. Run the Common Files installer again and select REPAIR (or do REPAIR from Add/Remove programs in Control Panel). This runs the Amyuni installer again, with the correct parameters for our license. This time, the Common Files installer should install SiriuswarePDF because those files are available to it on a 64 bit machine. 4. Finally, you must set the PORT for SiriuswarePDF to NUL on 64 bit systems: a. Make sure that you are logged in as a user with administrator rights. b. Select Control Panel, and click Devices and Printers. c. Right-click the SiriuswarePDF printer and select Printer Properties. d. Select the Ports tab, then click the Add Port... button. e. Select Local Port and click the New Port... button. f. Enter NUL for the new port name and click OK. Close the Printer Ports window. g. Ensure that the NUL port is selected in the Ports list. h. Select the Advanced tab. i. Select the Spool print documents radio button to make the options below it clickable. j. Clear (uncheck) the box labeled Enable advanced printing features. k. Select the Print directly to printer radio button again. l. Click the Apply button, and then click OK.
ODBC connections on 64 bit Operating Systems
Problem: When you create a new ODBC connector on Windows Server 2008 64-bit, ReportManager or SysManager fail to start.
When you create an ODBC connector, it makes a bunch of registry entries in HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI. But when a 32-bit application looks for those entries (like ReportManager or SysManager), the applications look in HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ODBC\ODBC.INI. So I exported the non- WOW entries, and edited the file, and re-imported them so they showed up under the Wow6432Node section, and ReportManager started.
I strongly suspect this will happen on Vista 64 bit as well.
I had some problems with the original install of Siriusware on my system related to this too. The funny thing was that there was an entry for the SiriusSQL ODBC connector in both places. Perhaps when a 32-bit app works on the registry directly, it does the right thing? Anyway – I had to change my ODBC connector after it was installed – but since my changes only happened in the non-Wow section, ReportManager wouldn’t work. I had to manually adjust the Wow section for it to start.
Solution: I am running Vista 64 on my laptop and ODBC worked OK from the default installs. Although you have to run odbcad32.exe from the syswow64 folder in order to actually see or modify the ODBC connection. If you run it from administrator tools you get the 64-bit version which
3
shows nothing. Run that version if you are on a 64 bit OS, run the normal one from the Administrative Tools menu otherwise.
For more information, see: http://portal.siriusware.com/docs/kb-pdf/error_and_other_messages/siriussql_2009_nov_18.pdf
64-bit Windows Server 2008
When installing Salesware on Windows Server 2008, you must turn on DEP and then exclude SysManager, ReportManager and Sales. See the Salesware Installation Guide for information about how to do this. After you do so, you may get the message: “The resource file is not valid. Overwrite it with a new empty one?”
Click Yes.
If you haven’t excluded Sales from DEP, you may get the message: “Unable to create instance of PrintEZ - Unable to load PrintEZ. Exception occurred.”
If you haven’t excluded SysManager from DEP, you may get a message with the words: “Fatal error: Exception code=C0000005, Common Files\Microsoft Shared\VFP\vfp8rerr.log, called from SysManager line 484” or something similar.
4
Sales generates SalesData_64bit.inf for use with Food Service FileSync
As of the 4.0.58 release, Sales generates the SalesData_64bit.inf file in the local Sales folder for use when using FileSync for shared data on a 64-bit computer.
Installation of ww.dll on 64-bit operating systems
Installation of ww.dll occurs exactly as described in the Salesware E-Commerce Installation Guide. However, you do not need to register it as a COM+ object because it can be pooled as a web garden using IIS 7, as described in http://portal.siriusware.com/docs/kb-pdf/Installation_and_updates/e- commerce_2010_mar_8.pdf. Note that if you are installing on a 64-bit computer then you need to modify the registry paths in ww.reg in order to get the registry entries installed in the correct locations. The following shows an example of the correct registry paths:
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Siriusware\E-Commerce]
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Siriusware\E-Commerce\CC] "Protobase"="65.118.84.235:4209" "TerminalID"="" "Operator"="Websales" "OCV"="" "AccountID"="" "Timeout"="120" "PreAuth"="TRUE"
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Siriusware\E- Commerce\Preferences] "ConnectionString"="Provider=SQLOLEDB.1;Password=siriusweb;Persist Security Info=True;User ID=siriusweb;Initial Catalog=SiriusSQL;Data Source=BENJAMIN2"
5
"DefaultInfo"="
Testing ww.dll with 64-bit operating systems
Siriusware provides the ww Test Script #1 and ww Test Script #1 scripts to test ww.dll on 64-bit operating systems. Download http://portal.siriusware.com/docs/kb-data/64-bit_wwdll_test_scripts.zip.
These test scripts are used in conjunction with the ww.dll test scripts described in http://portal.siriusware.com/docs/kb-pdf/Utilities/e-commerce_2009_Jan_25.pdf.
Execute from C:\Program Files\Siriusware or whatever directory is one folder “up” from where ww.dll is installed.
Using these scripts is the equivalent of running:
"C:\Windows\SysWOW64\cscript.exe" ww1.vbs "C:\Windows\SysWOW64\cscript.exe" ww2.vbs
Steps required to successfully re-install the SiriuswarePDF driver on a 64-bit Windows 2008 server (applies to Windows 7 also)
1. Delete SiriusPDF printer 2. Run RegEdit.exe and go to the following:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Print\Printers\SiriuswarePDF\PrinterDriverData
If this location exists, delete the “Code”, “License” and “TC” entries if they exist.
6
3. Repeat step 2 for these two registry locations:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Printers\SiriuswarePDF\P rinterDriverData
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Hardware Profiles\Current\Software\SiriuswarePDF
4. Reboot the PC. 5. Install the latest Common Files.
Error message: The module "C:\Program Files(x86)\Siriusware\Siriusware\E-Commerce\ww.dll" failed to load
Error message: The module "C:\Program Files(x86)\Siriusware\Siriusware\E-Commerce\ww.dll" failed to load
Solution: Install Siriusware Common Files. ww.dll is a c++ program that requires the c++ runtime libraries which are installed by the Common Files installer. So, on any computer that ww.dll runs on, Common Files needs to be installed.
7