Update instructions

Important: The updating process has changed to streamline the update process for their accesso SiriuswareSM product suite. Before beginning the updating process, please review the following steps:

One-time setup

Clients may now use the DACPAC for database updates with our batch file moving forward. The Microsoft files are required for you to use this new process. You will only need to do this the first time that you use the DACPAC or when Microsoft releases new DACPAC files. accesso Siriusware will post recent version details when updates are published. The current Data-Tier Application Framework is 16.4, version 13.0.3450.1.

Important: Clients using a 64-bit server must install x86 and x64 versions.

64 bit servers

1. Visit https://www.microsoft.com/en-us/download/details.aspx?id=53876 2. Click on System Requirements

3. Download both the SQLSysCLRTypes.msi x64 and the SQLSysCLRTypes.msi x86 files by clicking on each link.

Note: Both files download with the same name by default, so it is recommended to use Save As or to rename the downloaded files to add the version to the file name

4. Click the Download button

5. Select the check boxes for both EN\x64\DacFramework.msi and EN\x86\DacFramework.msi.

6. After all files are downloaded to the SQL server, double click each SQLSysCLrTypes.msi file and install individually.

7. To run the DacFramework.msi files, double click on each one.

32 bit servers

1. Visit https://www.microsoft.com/en-us/download/details.aspx?id=53876 2. Click on System Requirements

3. Download the SQLSysCLRTypes.msi x86 file by clicking on the link.

4. Click the Download button

5. Select the check box for EN\x86\DacFramework.msi.

6. After both files are downloaded to the SQL server, double click on the SQLSysClrTypes.msi file to run it.

7. Double click on the DacFramework.msi to run it.

Steps to Update

1. Create a temporary folder on the desktop of the SQL server and name it 4603 Update. 2. Create two folders inside of the 4603 Update folder called: DACPAC and Updates.

Note: This folder temporarily holds the files that need to be updated until both the script and DACPAC run successfully.

3. Download all required update files, which are located on Downloads > Updates > 4.6 Updates page of the accesso Siriusware portal.

4. Check for update files in: 4.6.03 Salesware, 4.6.03 Optional Modules, 4.6.03 Reports, and 4.6.03 Utilities. 5. A new update file is required for each file in the Siriusware\Updates folder.

Important: The accesso Siriusware product suite must be on version 4.5.04 before running DACPAC. Clients using version 4.5.04 or older must update the database with required script(s) before proceeding to the next step.

6. Download the DACPAC file from the portal, located on Downloads > Updates > 4.6 Updates > 4.6.03 Salesware page. Locate SiriusSQL_DACPAC_4.6.03_01007.zip and SiriusSQL_Update_SetupFiles.zip files and save them in the 4603\DACPAC folder previously created on the desktop.

7. Extract the contents of both zip files into the DACPAC folder and delete the .ZIP files.

8. Create a backup of the SiriusSQL database. 9. All applications on the accesso Siriusware product suite must be closed and services must be stopped.

These applications include: • Accounting Export • BookEZ • ExportService • MessengerService • RentEZ • ReportManager • Sales • SalesEZ • SysManager • TallyEZ • Web Sales Host

Note: All IIS on ww.dll and eCommerce page servers must also be stopped.

64 bit servers

1. Users must run the update directly on the SQL server and be logged-in as an Administrator with SQL access.

2. Double click on the SirisuSQL_Update.bat file to run it.

Important: Do not right click and run as an administrator – it will cause the process to fail.

3. The C:\Windows\system32\cmd.exe dialog now appears.

4. After the DACPAC finishes running, the following dialog will appear:

Note: If the DACPAC fails a message will appear, indicating that an error occurred and the log file must be checked to identify the issue. Failure may be caused by:

• Not running a backup • Applications and/or services running

If these scenarios caused the failure, the DACPAC can be run again. If any other errors are present:

1. Restore your backup 2. Open a case 3. Attach the SiriusSQL_Update.log file to the case

32 bit servers

Clients using a 32-bit operating system need to edit the SiriusSQL_update.bat file by performing the following:

1. Right click on SiriusSQL_Update.bat and choose edit to open the file in the Notepad application. • Locate the file path by scrolling to the bottom of the file list. The file path is located after the Running

the database update <this may take a while>… line. Edit the file path by removing the x86 after the Program Files section. The path should read as follows: C:\Program Files\Microsoft SQL Server\...

• Click the Save button and close the file.

2. Users must run the update directly on the SQL server and be logged-in as an Administrator with SQL access.

3. Double click on the SirisuSQL_Update.bat file to run it.

Important: Do not right click and run as an administrator – it will cause the process to fail.

4. The C:\Windows\system32\cmd.exe dialog now appears.

5. After the DACPAC finishes running, the following dialog will appear:

Note: If the DACPAC fails a message will appear, indicating that an error occurred and the log file must be checked to identify the issue. Failure may be caused by:

• Not running a backup • Applications and/or services running

If these scenarios caused the failure, the DACPAC can be run again. If any other errors are present:

• Restore your backup • Open a case • Attach the SiriusSQL_Update.log file to the case

6. Move the new 4.6.03 application update files to the SiriusFS\Updates or Siriusware\Updates

folder, which are located on the SQL Server by default. 7. Open SysManager and log-in. 8. The Security Update dialog box appears while the system performs a precautionary scan of the database

to verify that all credit card data is secure. Click the Start button.

9. After the mandatory update has run completely, click the Close button.

10. The final setting is located on SysManager > Utilities > Data Maintenance > MaxKeys on Server button.

Updating services

The following services do not update automatically:

1. The Middleware server has a folder on the desktop named Update Pools that contains short cuts that need to be double clicked to pull the updates down.

2. The following services: ww.dll, Export Services, Accounting Export and Messenger Service have a shortcut on each server desktop which are named: • Update ww.dll • Update ExportService • Update Accounting Export • Update MessengerService

Updating the ww.dll

1. If not already completed, download the update file located on Downloads > Updates > 4.6 Updates > 4.6 Updates > 4.6.03 Optional Modules.

2. Perform an IISRESET/stop in the Command Prompt. 3. Double click on the Update ww.dll shortcut located on the ww.dll machine. 4. Perform an IISRESET/start in the Command Prompt.

Note: If the shortcut file is not present or the ww.dll machine is not local, copy the c_ww_4603_01019.exe file to your c:\Program Files (x86)\Siriusware\E-Commerce folder.

1. Open a Command Prompt. 2. Perform an IISRESET /stop in the Command Prompt. 3. Double click the c_ww_4603_01019.exe file to extract it. 4. Do an IISRESET /start in the Command Prompt.

eCommerce

Steps to update eCommerce pages

Please read the below instructions carefully!

Note: Follow these steps if accesso Siriusware has updated the client eCommerce pages:

1. Make a copy of the live eCommerce folder located on c:\inetpub\wwwroot\ 2. Open the folder sent by accesso Siriusware and copy the updated files into the appropriate folders 3. Check Permissions on these folders and ensure the IIS_USRS user has modify permissions:

• Images • XMLFiles • SiteConfig.config

4. Perform an IISRESET

Step 1: Preparing for the Update

Note: Follow these steps if the client is updating eCommerce pages independently:

Important: The following applications must be updated to 4.6.03 prior to updating eCommerce: SiriusSQL, SalesEZ, Sales Host, and ww.dll.

1. Stop the website by opening a command prompt and typing: IISRESET /STOP 2. Download the ECommerce_Pages_4603_01025.exe update file located on Downloads > Updates >

4.6 Updates > 4.6.03 Optional Modules.

Note: Do not download the Ecommerce_Pages _Config_4603_01025.exe file.

3. Create a desktop folder named E-commerce 4603. 4. Extract the Ecommerce_Pages_4603_01025.exe file into the E-Commerce 4603 folder created

in step 3. These files contain the latest pages and updates. As next steps, files will be copied from this location to the main eCommerce directory.

5. Copy the live eCommerce folder located on c:\inetpub\wwwroot\. This serves as a backup in the event of update failure.

6. Apply all the Step 2 through Step 5 changes as per the instructions listed below.

Step 2: BIN update

1. Delete all the files in the c:\inetpub\ecommerce\BIN folder 2. Copy all the files from the folder to the E-commerce 4603/BIN directory 3. Paste the files into the c:\inetpub\wwroot\ecommerce\BIN folder.

Note: The eCommerce folder may have an alternate name. In this scenario, identify the correct set of pages.

Step 3: New files to be added \admin\help\add-on-module.htm \admin\help\calendar-alt-url.htm \admin\help\calendar-avail-threshold.htm \admin\help\calendar-items-incell.htm \admin\help\calendar-mode.htm \admin\help\calendar-remaining-template.htm \admin\help\calendar-savings-break.htm \admin\help\calendar-savings-format.htm \admin\help\calendar-show-capacity-alert.htm \admin\help\calendar-show-price.htm \admin\help\calendar-show-savings.htm \admin\help\calendar-show-tooltip.htm \admin\help\calendar-use-itemurl.htm \admin\help\developer-settings-panel.htm \admin\help\multi-add-view.htm \admin\images\green-circle-plus.png \admin\images\red-circle-remove.png \app\admin\ - (and all children) \app\calview\calendarItemDirective.js \app\general\ - (and all children) \app\templates\addressVerificationTemplate.html \app\templates\checkboxesTemplate.html

\app\templates\creditcardTemplate.html \app\templates\customTemplate.html \app\templates\dropdownTemplate.html \app\templates\emailTemplate.html \app\templates\guestTemplate.html \app\templates\heightTemplate.html \app\templates\maskedInputTemplate.html \app\templates\ModalTemplateIframe.html \app\templates\passwordTemplate.html \app\templates\phoneInputTemplate.html \app\templates\textMemoTemplate.html \app\templates\textRegexTemplate.html \app\templates\weightTemplate.html \app\templates\zipCodeTemplate.html

\App_Themes\themeName\bootstrap\ - (and all children) \App_Themes\sirius_admin\bootstrap\ - (and all children) \App_Themes\sirius_admin\fonts\glyphicons-halflings-regular.eot \App_Themes\sirius_admin\fonts\glyphicons-halflings-regular.svg \App_Themes\sirius_admin\fonts\glyphicons-halflings-regular.ttf \App_Themes\sirius_admin\fonts\glyphicons-halflings-regular.woff \images\Screenshot Calendar.PNG \scripts\xml2jsonAdmin.min.js \template\FinalizedTemplate-Moneris.html \template\SavedTemplate-Moneris.html License.aspx

Step 4: Remove

Remove the Calendar folder and all contents.

Step 5: Replace Files

If changes were made to any of these files, pages will need to be manually updated. It is recommended that users pay close attention to commonly customized files. Users should leverage a utility, such as the BeyondCompare utility, to make the changes to customized pages. Customized pages are noted below with a * symbol:

\admin\AdminControls\ConfigEditor.ascx \admin\AdminControls\ItemEditor2.ascx \admin\AdminControls\ItemTreeEditor2.ascx \admin\AdminControls\AdminMaster.master

\admin\ItemListConfig.aspx \admin\Utilities.aspx \app\calview\calendarDayDirective.js \app\calview\calendarViewDayPopover.html \app\calview\calendarViewDayTemplate.html \app\calview\calendarViewDirective.js \app\calview\calendarViewTemplate.html \app\calview\calviewController.js \app\calview\calviewService.js \app\itemTree\itemTreeService.js \app\app.js \App_Themes\themeName\calendarView.css \App_Themes\sirius_admin\style.css \App_Themes\sirius_admin\style_admin.css \scripts\frameBuster.js \scripts\memberbenefits-itemshow.js \UserControls\AngularLinks.ascx *\UserControls\Cart.ascx

\UserControls\Email.ascx \UserControls\ItemListMulti.ascx \UserControls\RSControl.ascx CalendarView.aspx * Checkout.aspx * Checkout2.aspx * Checkout3.aspx * Conf2.aspx * GuestEdit.aspx * GuestSelected.aspx

Step 6: Changes to Files

XMLFiles\dynamicControls.xml

Add: <guestEdit> <Name>UCmid_name</Name> <RowID>mid_name</RowID> <dbField>g.mid_name</dbField> <Columns>20</Columns> <MaxLength>15</MaxLength> <Required>0</Required> <Required_purch>0</Required_purch> <RequiredText>Required!</RequiredText> </guestEdit>

After this: <Name>UClast_name</Name> section

MasterPageThemeName.master (if this file is not already present)

Remove: scripts/resize_fancybox.js

After the scripts/jquery-1.12.3.min.js

Add: <script src="scripts/jquery-migrate-1.3.0.min.js"></script>

MasterPageThemeNameMobile.master (if this file is not already present)

Add: <script src="scripts/jquery-migrate-1.3.0.min.js"></script>

SiteConfig.config

Add these new keys below the last </SiteConfig> and above the </ArrayOfSiteConfig> tag

<SiteConfig> <Key>GivexInsufficentFundsMsg</Key> <Value>Sorry, you do not have sufficient funds on your Givex Gift Card for this sale. Please try another form of payment.</Value> <Category>Checkout Settings</Category> <Description>Set GivexInsufficentFundsMsg to the text that should be displayed when a user attempts to use a Gixex Gift Card, but has insufficient funds.</Description> </SiteConfig> <SiteConfig> <Key>GivexLabel</Key> <Value>Pay with Givex Gift Card</Value> <Category>Checkout Settings</Category> <Description>Set GivexLabel to the desired label to appear on Checkout.aspx to enable this payment type.</Description> </SiteConfig>

<SiteConfig> <Key>GivexPayment</Key> <Value>1</Value> <Category>Checkout Settings</Category> <Description>Set GivexPayment to 1 to enable a checkbox on Checkout.aspx that allows paying with a Givex Gift Cards. Note, this is available through Elavon's Simplify solution.</Description> </SiteConfig> <SiteConfig> <Key>GivexGiftTermID</Key> <Value></Value> <Category>Checkout Settings</Category> <Description></Description> </SiteConfig> <SiteConfig> <Key>UniqueEmailError</Key> <Value>Sorry, this email is already in use. Please click &lt;a href="GuestLookup.aspx"&gt;here&lt;/a&gt; to login or use a different email address</Value> <Category>Guest Related Settings</Category> </SiteConfig> Check to see if the client already has these keys <SiteConfig> <Key>MicroDonate</Key> <Value>0</Value> <Category>Donation Settings</Category> <Description>Set MicroDonate to 1 to enable 'round-up' donation prompts to the ecommerce customer at checkout</Description> </SiteConfig> <SiteConfig>

<Key>MicroDonateText</Key> <Value>Would you like to make a $1.00 donation to our energy-offset program?</Value> <Category>Donation Settings</Category> <Description>MicroDonateText will be the text displayed to the ecommerce customer when using the microdonate feature.</Description> </SiteConfig> <SiteConfig> <Key>MicroDonationItemDCI</Key> <Value>DDDDDDDDDDCCCCCCCCCCIIIIIIIIII</Value> <Category>Donation Settings</Category> <Description>MicroDonationItemDCI is the padded nickname of the round-up donation DCI</Description> </SiteConfig>

Tix2.aspx

Change this: <script src="scripts/jquery.min.js" type="text/javascript"></script>

To this: <script src="scripts/jquery-1.12.3.min.js" type="text/javascript"></script>

Web.config

Change this: <httpRuntime requestValidationMode="2.0" />

To this: <httpRuntime requestValidationType="CustomRequestValidator" requestValidationMode="2.0" />

Step 8: Restart the Site

1. Check Permissions on these folders and ensure the IIS_USRS user has modify permissions: • Images • XMLFiles • Siteconfig.config

2. Open the command prompt and type IISRESET 3. Test the site to ensure it is functioning properly