Deployment Guides (SIPP/SSAS~Pro)

See attached

Overview When the FileMaker Server service is started, a number of events are recorded in the Application event log. These can be viewed in two ways: FileMaker Sever Console Windows Event Viewer Note: Option 1 is our default choice as it provides a pre-filtered list of FileMaker events. FileMaker Server Console The following steps are to be completed on the FileMaker server that is hosting your SIPP~Pro and/or SSAS~Pro data. Click on ‘Start > All Programs > FileMaker Server Console’. Note: Can also be launch by running 'drive:\FMServer\FMSCONSL.msc' Ensure the '32-bit' radio button is selected and click 'OK'. Once the console has opened, expand the 'Classic Event Viewer' menu. Select 'FileMaker Server'. Review the events to see if any errors or warnings have been encountered, since the 'FileMaker Server' service started.

Target Audience Customers experiencing specific errors (see Related Articles) or have been directed to this article by Delta Product Support. Overview SIPP~Pro and SSAS~Pro contain embedded (hard-coded) processes that read/write files to disk. If the appropriate folder structure does not exist, some processes may not function correctly. Symbolic Links should be used to resolve these issues. Symbolic Links Symbolic links are file-system objects that point toward another file or folder. The object being pointed to is called the target. Symbolic links are transparent to users; the links appear as normal files or directories, and can be acted upon by the user or application in exactly the same manner. Syntax mklink /d Reference: mklink Deployment Prerequisites Administrator access to computer Command Prompt (elevated mode) Create Symbolic Link MKLINK /D "C:\Program Files\FMPRO55" "C:\Program Files (x86)\FMPRO55" Remove Symbolic Link RMDIR "C:\Program Files\FMPRO55" Command Prompt (Elevated) Locate the 'Command Prompt' shortcut in the Start menu. Right-click, and select 'Run as Administrator': Background Information From the mid-80's to shortly after the turn of the millennium, mainstream personal computers (PC's) used a '32-bit' architecture. In lay terms, this meant they could process 32 'lanes' of data simultaneously. Around 2003, 64-bit machines began to emerge, however operating systems and programs required development to take advantage of this extra processing power. Microsoft Windows By default, programs deployed on Microsoft Windows operating systems install in the 'Program Files' folder, providing their coding matches the native architecture. To accommodate a mix of 32/64-bit programs on one machine, Microsoft created a new application folder 'Program Files (x86)' in which 32-bit applications are installed. The following table demonstrates the variations: Example No. Hardware Software Default Installation Folder 1 32-bit 32-bit Program Files 2 64-bit 64-bit Program Files 3 64-bit 32-bit Program Files (x86) Note: Windows Server 2008 R2 was the first 64-bit only operating system. SIPP/SSAS~Pro Due to the evolution of computing architecture, our applications have needed to adapt. The core development of SIPP~Pro and SSAS~Pro predates 64-bit machines, therefore some coding references 'Program Files'. When customers began replacing their 32-bit PC's and servers with 64-bit machines, a hybrid environment was born in which our applications needed to work across all variants. Related Articles Error Message: ADC_ADC.Mer file not found

Overview The Delta Module Manager application is populated using an exported data set from SIPP~Pro and SSAS~Pro.To achieve this, a set of CSV files are exported from FileMaker Server each evening, ready to be imported in to the Report~Pro databases (SQL Server). Audience/Purpose If you are the IT support provider responsible for the maintenance and upkeep of the servers which Delta's applications run from, you need to know how the CSV export process works in order to effectively troubleshoot and resolve issues reported by the end-users. Delta Financial Systems will only provide technical assistance once all suggestions here have been exhausted. Data Export Process Flow The following diagram provides a high-level flow of the CSV file export process: Notes: This process runs on the machine with FileMaker Server installed. The default location of the SIPP~Pro CSV export folder is ‘drive:\Program Files (x86)\FMPro55\SIPPReportProCSV’. The CSV’s are generally exported locally, but can be configured to write directly, or copied to, a network share. Troubleshooting Guide Logically, it makes sense to start at the beginning of the process with the scheduled task. Locating this will enable you to locate the batch script it runs, which in turn will tell you where the CSV files are exported to. Note: With more experience, it's possible to start the troubleshooting process at a later stage. Step 1 - Task Scheduler Open Windows Task Scheduler (taskschd.msc). Locate the export task - This is called 'ExportRP' by default. Is it's status Running or Ready? Note: If 'Running', FileMaker Pro is probably stuck in memory (see step 3). Step 2 - CSV Files Examine the batch script to identify the CSV export folder . Are there any CSV files in the folder path?  If there there are CSV files, what's their time/date stamp? Warning: Do not run/execute the batch script, you must right click and select Edit in order to view. Step 3 - FileMaker Pro Is FileMaker Pro running in memory? Open 'Task Manager'. Under the 'Processes' tab, can you see 'FileMaker Pro.exe'? If yes, click the process, then select 'End task'  (The 'ExportRP' scheduled task will now return to Ready). Warning: Do not stop FileMaker Server. Step 4 - FileMaker Server Event Logs TBC

See attached

See attached

See attached.

Open FileMaker Server Console by one of the following methods: Locate on Start menu; Locate and run 'installdrive\FMServer\FMSCONSL.msc' Once open, select 'Database Hosting': Click the 'Next' button 6 times until you see this screen: Select the tick box and click 'Finish'.