what diagnostic to obtain for Advanced Reporting - ARFAX

[GeraldC1]

Prognosis Advanced Reporting has components on both a Prognosis server and an SQL server. What diagnostics should I obtain if I need help with an Advanced Reporting issue?

[GeraldC1 · Accepted solution]

In addition to getting an IRFAX from the Prognosis server side, the ARFAX is a diagnostic of the SQL side of Prognosis Advanced Reporting - BigDataInsight / BusinessInsight versions 11.0, 11.3, 11.4 and 11.5. An ARFAX can be generated by downloading and running the attached 'arfax11.5.sql.txt' SQL script and directing the output into a text file. The Microsoft 'sqlcmd.exe' command line utility can be used as described below.

Requirements:

• permission to read the sys.tables in SQL / system tables

option 1 - as 'SA' SQL user:

In a command prompt, in the directory where 'arfax11.5.sql.txt' is downloaded to:

"SQLCMD.EXE" -S <hostname>\<instance> -U SA -P <password> -d <BigDataInsight-DB-name> -W -s, -i arfax11.5.sql.txt -o arfax.csv

option 2 - as 'domain\user' NT authentication:

runas /user:domain\user  cmd.exe

Then in the new launched command prompt in the directory where 'arfax11.5.sql' is downloaded to: 

"SQLCMD.EXE" -S <hostname>\<instance> -d <BigDataInsight-DB-name> -W -s, -i arfax11.5.sql.txt -o arfax.csv

Note:

• The full path of 'sqlcmd.exe' may need to be specified. For example:
  "C:\Program Files\Microsoft SQL Server\110\Tools\Binn\SQLCMD.EXE"
  or
  "C:\Program Files\Microsoft SQL Server\Client SDK\ODBC\110\Tools\Binn\SQLCMD.EXE"
• If successful then the output 'arfax.csv' file size should be larger than 100KB.
• Arfax does not replace the irfax diagnostic which is still needed for the Prognosis server side of the Prognosis Advanced Reporting.

[GeraldC1 · Accepted solution]

Here is a short video example of option 2 and on the Prognosis server.

Steps in the Video:

1. Copy the commands into a text editor; then determine the variables from Prognosis Client and fill in the variables.

2. NT user - Properties of a BigDataInsight databases; File > Create Document > Database Collection , select Format tab, note the passwordkey, then get the NT user from that passwordkey in PASSWORDS configuration.

3. SQL server hostname and instance name - in the database properties, use the server name (or IP address) and instance name (or if it is a blank instance)
 

4. SQL database name - Open "ODBC Data Sources 32-bit" console (or 64-bit) > "System DSN" > the ODBC object name > flick through Configuration options find for example BigDataInsightUCSource, then DB name is , example BigDataInsightUC.

5. run the commands;

6. Inspect the resulting file to confirm that it contains diagnostics.