SilkCentral - HTTP Status 500 - Java.Lang.NullPointer.Exception

October 22, 2015, 12:49 am

≫ Next: HTTP Access Logs in Silk Central

Current Revision posted to Silk Central Knowledge Base by MRS on 10/22/2015 2:49:00 AM

Issue Description: After applying the HF1 on SilkCentral V 16.0 following exception has been encountered:

Resolution:
This issue happens due to requirements synchronization log folder is full. To get past this problem clean up the synchronization logs with the following workaround:
• Stop AppServer and FrontendServer
• Go to your Silk Central log directory, e.g. C:\ProgramData\SilkCentral\log
• Move all files starting with "SynchLog" to another directory (e.g. c:\save)
• Start AppServer and FrontendServers again
• Try to reproduce by selecting root and starting synchronization

This issue will be taken care of in SilkCentral V 16.0 Hotfix 2.

Support Incident #2827301.

↧

HTTP Access Logs in Silk Central

October 29, 2015, 12:03 pm

≫ Next: Unexpected import processing error for Excel file java.lang.NullPointerException

≪ Previous: SilkCentral - HTTP Status 500 - Java.Lang.NullPointer.Exception

Current Revision posted to Silk Central Knowledge Base by Matthew McGibbon on 10/29/2015 2:03:44 PM

In Silk Central you can enable Access Logs for greater visibility in to users transactions with the system, and the specific URL's they are navigating to.

To enable this setting first go to,

%INSTALLDIR%\conf\frontendserver\conf

Install Directory will be the default location where Silk Central is install on the server.

Open the server.xml file and add the following line below the Host information:

<Valve className="org.apache.catalina.valves.AccessLogValve" directory="C:/ProgramData/SilkCentral/log/tomcat" prefix="access_log" fileDateFormat="yyyy-MM-dd.HH" suffix=".log" pattern="%t %a %m %U %q %s %D %F" encoding="UTF-8"/>
</Engine>

This will require a restart of your Front-End server to pick up the new file, and then will begin creating a log entry file in the directoy:

C:\ProgramData\SilkCentral\log\tomcat

Please find attached an example of the log file this will produce and a sample server.xml file to show how this is configured.

You can also modify this to suit your needs on the information returned which can be found on the tomcat site:

https://tomcat.apache.org/tomcat-7.0-doc/config/valve.html#Access_Control

Sample Documents:

access_log2015-09-21.21.log

server.xml

Tags: Silk Central, Tomcat, Access Logs, Server.xml

↧

Unexpected import processing error for Excel file java.lang.NullPointerException

October 29, 2015, 12:06 pm

≫ Next: Running a Powershell scripts with via Process Executor test in Silk Central Test Manager does not complete

≪ Previous: HTTP Access Logs in Silk Central

Current Revision posted to Silk Central Knowledge Base by Matthew McGibbon on 10/29/2015 2:06:37 PM

Using Google Sheets and importing the Tests in to Silk Central is possible but the Google sheet must first be converted using Excel.

Trying to import a downloaded Google Sheet will generate the following error:

Make a Google Sheet which relates to the Mapping File, an example is shown below:
Export the file to excel via File | Download As | Microsoft Excel:
Open the generated .xlsx file in Excel
Click FILE | "Save As"in Excel
The file can now be imported into Silk Central

Tags: Google Sheets, Silk Central, Error, EXCEL, import

↧

Running a Powershell scripts with via Process Executor test in Silk Central Test Manager does not complete

November 17, 2015, 7:12 am

≫ Next: Silk Central Report Templates - BIRT v4.4

≪ Previous: Unexpected import processing error for Excel file java.lang.NullPointerException

Current Revision posted to Silk Central Knowledge Base by Matthew McGibbon on 11/17/2015 9:12:51 AM

When executing Powershell scripts through a Process Executor script the Powershell process may hang because it has not been terminated when executed within SilkCentral.

It is therefore recommended that within your Powershell script you use a command to terminate the actual Powershell process. For example you can use the following code to terminate the Powershell process:

[Environment]::Exit(“0”)

Note:

If you are using Powershell version 4 or 5, you do not need to add the explicit Exit command.

Incident #2575652

Old KB# 36349

Tags: Powershell, SilkCentral, Process Executor

↧

Silk Central Report Templates - BIRT v4.4

November 18, 2015, 12:10 pm

≫ Next: Automating Result File Cleanup - Silk Central 16.5

≪ Previous: Running a Powershell scripts with via Process Executor test in Silk Central Test Manager does not complete

Revision 1 posted to Silk Central Knowledge Base by Matthew McGibbon on 11/18/2015 2:10:12 PM

Silk Central 16.0 introduced a new version of BIRT v4.4, and what this means is that some of the previous templates developed on older versions of Silk Central will need to be upgraded.

Below you will find the instructions in making sure that you can successfully upgrade your BIRT v2.5.

1. Some of the shipped templates used an if clause in chart series data to hide series with 0-values in (stacked) bar charts:

if (row["passed"] > 0) {
row["passed"];
} else {
Number.NaN;
}

This doesn't work any longer, an error that NaN can't be used as chart data is displayed. Just use e.g. row["passed"] as the series data, and paste the following into the "onRender" script on the Script tab of the chart:

function beforeDrawDataPointLabel(dph, label, icsc) {
if (label.getCaption().getValue() == "0") {
label.setVisible(false);
}
}

2. BIRT 4.4 is more critical on invalid data bindings on tables/grids. It seems that all the bindings are evaluated although they might be unused.

3. When creating custom reports, please use the BIRT RCP Designer package that can be downloaded on the Help/Tools page in Silk Central. This BIRT designer package includes Silk Central .jar files that are necessary to connect to Silk Central web services.

4. The BIRT 4.4 Report designer no longer has a "Preview" tab using a built-in browser control.
To preview reports, choose "Run/View Report/As HTML" from the menu.

The browser to be used can be specified as follows:

- In "Window/Preferences/Web Browser" select "Use external web browser" and choose a browser.
- In "Window/Preferences/Report Design/Preview" you can check "Always use external browsers"

Tags: template, Report, Reporting, Reports, SilkCentral, BIRT, Silk Central Test Manager

↧

Automating Result File Cleanup - Silk Central 16.5

November 19, 2015, 7:17 am

≫ Next: Silk Test Workbench returned error 3: DSN, username, or password incorrect

≪ Previous: Silk Central Report Templates - BIRT v4.4

Revision 1 posted to Silk Central Knowledge Base by Matthew McGibbon on 11/19/2015 9:17:08 AM

In Silk Central 16.5, the functionality to automatically create rules for cleaning up Execution Result Files or Runs, has been introduced,

This can be done at a Project Level, Folder Level or Execution Plan level.

The rules themselves can be rolled up to include multiple conditions that can be executed at different times.

DELETE all runs over a year old
DELETE all wmv files over 1 months old
DELETE all png files over 3 months old

The rules will now run on these periods to remove the designated files automatically and help users maintain, manage and control their database growth.

Tags: Silk Central, Database Growth, files, results, Runs

↧

Silk Test Workbench returned error 3: DSN, username, or password incorrect

November 20, 2015, 6:36 am

≫ Next: Could not delete user: java.sql.SQLException: The DELETE statement conflicted with the REFERENCE constraint

≪ Previous: Automating Result File Cleanup - Silk Central 16.5

Revision 1 posted to Silk Central Knowledge Base by Matthew McGibbon on 11/20/2015 8:36:13 AM

When executing Workbench scripts from Silk Central 16.5, you might see the following error:

Silk Test Workbench returned error 3: DSN, username, or password incorrect

This error indicates that the source control profile, that is used for execution, does not match the configuration of the SQL Server were your source control profile is pointed.

There is a few reasons for this, and the most common being incorrect credentials.

The other issue is that the port that is specified on your Source Control profile is incorrect. To check this, please do the following:

1. Open SQL Server Configuration Manager

Here we want to to take down the 'Process ID' for the SQL Server instance, in this case 17304.

2. On the machine, open a command prompt window and type the following command, netstat -ano | findstr 17304

This will return a list of the ports that the SQL Server instance is listening on. As seen by the top two connections.

This means that we must use one of these ports in our Source Control profile for establishing a successful connection to our SQL Server.

3. Source Control Profile

Once configured we will be able to establish a successful connection to the Silk Test Workbench database, and execute the Workbench Scripts.

Tags: workbench, Silk Central, Error, Silk Test, DSN

↧

Could not delete user: java.sql.SQLException: The DELETE statement conflicted with the REFERENCE constraint

November 24, 2015, 7:33 pm

≫ Next: Silk Central with TestNG

≪ Previous: Silk Test Workbench returned error 3: DSN, username, or password incorrect

Revision 1 posted to Silk Central Knowledge Base by Matthew McGibbon on 11/24/2015 9:33:36 PM

In the User Management section of Silk Central 16.5, when you are deleting a user, you might get the following error message:

This error indicates that the user you are trying to delete is tied to the template user on your LDAP Server.

To check this go to Administration -> System Settings, and on click the LDAP Server name and check the 'User Account Creation' settings.

Click the image below to show how to access this area:

If the user you are trying to delete is defined here as your 'template user', you will need to change this user first. Once the user is changed to a different user, you will be able to successfully delete the user.

Tags: User Account Create, Silk Central, Users, User, ldap, User Management

↧

Silk Central with TestNG

January 4, 2016, 12:00 pm

≫ Next: java.sql.SQLException: Login failed.

≪ Previous: Could not delete user: java.sql.SQLException: The DELETE statement conflicted with the REFERENCE constraint

Revision 1 posted to Silk Central Knowledge Base by Matthew McGibbon on 1/4/2016 2:00:31 PM

TestNG framework is currently inspired by JUnit testing, but includes extra functionality to make your testing more powerful.

Silk Central now has a runner, that allows you to utilize this testing framework, and run your TestNG scripts in Silk Central.

If you would like a copy of the the TestNG runner please log a case through SupportLine.

We will provide you with the instructions you need to install and run this in Silk Central.

Tags: Silk Central, TestNG, Silk

↧

java.sql.SQLException: Login failed.

January 6, 2016, 1:11 pm

≫ Next: How do I change which Application Server my Frontend server points to?

≪ Previous: Silk Central with TestNG

Revision 1 posted to Silk Central Knowledge Base by conorc on 1/6/2016 3:11:12 PM

You may see the following error message when running a report:

+ An exception occurred during processing. Please see the following message for details:
Cannot open the connection for the driver: org.eclipse.birt.report.data.oda.jdbc.
org.eclipse.birt.report.data.oda.jdbc.JDBCException: Failed to get connection.
SQL error #1:Login failed. The login is from an untrusted domain and cannot be used with Windows authentication.
;
java.sql.SQLException: Login failed. The login is from an untrusted domain and cannot be used with Windows authentication.

This is normally caused by the database connection details used between Silk Central and SQL.

The user for the integration does not have the necessary permissions to access some tables in the database.

To resolve this, use the steps below:

Log in to Silk Central as the user "sysadmin".
Go to the Database tab.
Disconnect your current database connection.
Check if you have a "Read Only Username/Password" entered.
If you do, then please remove the Read Only details, and keep only the normal username/password for the connection.
The username and password used here, should be a user within the SQL database that has full admin permissions.
Save your changes and database settings.
Try logging in and running the report once more.

SI: 2845380

Tags: birt.report.data, Silk Central, Windows, Untrusted, authentication, driver, Connection, login failed, Report, Error, sql, Exception, BIRT, JDBC, SQLException, SCTM, Java, Occurred, domain

↧

How do I change which Application Server my Frontend server points to?

January 20, 2016, 5:21 pm

≫ Next: VersionOne Integration - Test Task could not be created in SCTM

≪ Previous: java.sql.SQLException: Login failed.

Current Revision posted to Silk Central Knowledge Base by ryanmc on 1/20/2016 7:21:48 PM

If you wish to change the Application Server being used by your SilkCentral Frontend Server you should firstly stop the Frontend Server service and navigate to the following location:

"C:\Program Data\SilkCentral"
or
"C:\Documents and Settings\All Users\Application Data\SilkCentral"

Then open the file called "appserver.ini", this file should contain 2 lines:

1. Should contain the machine name or IP address of the application server.
2. Should contain the PORT number required to access the application server.

Simply edit the hostname and port for the new Application Server, save the file and then start the Frontend Server service.

Now when you access the Frontend Server URL it will be pointing to the new Application Server.

Tags: Application Server, app server

↧

VersionOne Integration - Test Task could not be created in SCTM

June 1, 2016, 9:04 am

≫ Next: Execution server is already used by application server on host error

≪ Previous: How do I change which Application Server my Frontend server points to?

Revision 2 posted to Silk Central Knowledge Base by MichealL on 6/1/2016 11:04:01 AM

When attempting to synchronise VersionOne test tasks to Silk Central, you may receive an error message in your Silk Central log files stating that your 'Test Task could not be created in SCTM'.

In order to resolve this issue, please ensure that you have a release/sprint value set in VersionOne. Once this is done, the synchronisation to Silk Central should be successful.

SI: 2864589

Tags: VersionOne, synchronise, Silk Central, integration, test task, SCTM, synchronisation

↧

Execution server is already used by application server on host error

June 1, 2016, 9:09 am

≫ Next: Exporting filtered test cases does not work in Tests > Details View

≪ Previous: VersionOne Integration - Test Task could not be created in SCTM

Current Revision posted to Silk Central Knowledge Base by MichealL on 6/1/2016 11:09:59 AM

This error can occur when you are changing an execution server from one environment to another on Silk Central.

Please see the below steps to delete execution server associations on the original machine without using Silk Central. This is useful if Silk Central has been uninstalled on the original machine.

On the original machine:

1. Delete the AgentBase folder at C:\ProgramData\SilkCentral.

2. Go to SQL Management Studio. Please see the below three delete queries that need to be run.

You will need to check the referenced tables first for the execution server names and values. Check the tables for the info and modify the delete queries to match it.

Sample queries:

DELETE FROM [demodb].[dbo].[SCC_Orders_ExecServers] WHERE ExecServerID_pk_fk = 18

DELETE FROM [demodb].[dbo].[SCC_ExecServers] WHERE Name = 'localhost'

DELETE FROM [demodb].[dbo].[SCC_Locations] WHERE Name = 'Local'

3. Restart the execution server.

On the new machine:

1. Log out of Silk Central and log back in again.

2. You should now be able to add the original machine as an execution server in your Execution Environment in Silk Central.

SI: 2832879

Tags: Silk Central, execution server, agentbase, SCC_ExecServers, sql, ProgramData, Application Server, SCTM, app server, Execution Environment

↧

Exporting filtered test cases does not work in Tests > Details View

June 1, 2016, 9:11 am

≫ Next: Enable SSL Setup in SC17

≪ Previous: Execution server is already used by application server on host error

Current Revision posted to Silk Central Knowledge Base by MichealL on 6/1/2016 11:11:07 AM

It is not possible to export filtered test cases in the Details View. The Download as XLSX option from the Test Grid View is the way to export filtered test cases.

There are no plans to change this in the Details View as of Silk Central 16.0. This enhancement is not possible currently as a subsequent Update would remove all the tests that are not part of the Export.
Therefore the Export and Update would have to be changed in a way that the data used for the Export and Update can co-exist with other data.

However, it is possible to return information on filtered test steps and attributes by extracting the information from the database using SQL queries.

SI: 2829713

Tags: Details View, grid view, Silk Central, Queries, 16.0, sql, update, Export, Export to Excel, EXCEL, SCTM, xlsx

↧

Enable SSL Setup in SC17

June 10, 2016, 10:15 am

≫ Next: Load Balancing Servers in SC17

≪ Previous: Exporting filtered test cases does not work in Tests > Details View

Revision 1 posted to Silk Central Knowledge Base by conorc on 6/10/2016 12:15:22 PM

To enable SSL on Silk Central 17:

1. Copy the certificate and key to the frontend server machine

2. Edit the file nginx.conf.template in C:\Program Files (x86)\Silk\Silk Central 17.0\instanceadministration\nginxFiles\conf

3. Uncomment the following lines by removing the #

#listen 443 ssl;

#ssl_protocols TLSv1.2 TLSv1.1 TLSv1;

#ssl_certificate "C:/.../ssl/host.cert";

#ssl_certificate_key "C:/.../ssl/host.key";

4. Set the correct path for ssl_certificate and ssl_certificate_key in the nginx.conf.template.

- Specify the path using slashes instead of backslashes

(Optional: Comment the listen 19120; if you want to allow SSL only)

5. Restart the Instance Administration

Tags: instance, Manager, 17, Central, HTTPS, nginx, Silk, Secure, certificate, SSL, SCTM

↧

Load Balancing Servers in SC17

June 17, 2016, 9:23 am

≫ Next: Silk Central 17.0 | Managing Silk Central Services

≪ Previous: Enable SSL Setup in SC17

Revision 1 posted to Silk Central Knowledge Base by conorc on 6/17/2016 11:23:47 AM

On Machine 1 – Main Application/Frontend Server

On Machine 2 – Frontend Server only

---------------------------

On Machine 2, do the following:

Open Silk Central Instance Manager
Stop the Services you do not need. (eg Application,Chart servers)
Click the Settings button > Go to Servers Tab > select Frontend server
Get the port being used and copy this

Go to Machine 1

Open Instance Manager
Click Settings > Activate maintenance mode to make changes to the config files
Open the NGINX custom properties file for editing by going to
1. C:\Program Files (x86)\Silk\Silk Central 17.0\nginx\conf
Right Click on the nginxCustom.properties file and Edit
Add the URL of the front-end server on Machine 2 by using the following format:
1. frontendservers.<Instance_Name>=<URL1:PORT>,<URL2:PORT>
eg: frontendservers.silk=localhost:19110,silkserver2:19110

7. Save the changes to this file

Go back to Machine 1 Instance Manager

Click Settings > Deactivate maintenance mode
Connect to the URL of Machine 2 > Enter your Application Server details
Now you can connect to the frontend server by using the URLS of Machines 1 or 2

** Because of NGINX restrictions it is not possible to use port 19120 of a front-end server.

Always get the port from the settings dialog as described above

For Setting Up Multiple Chart Servers

Log in to Frontend server as sysadmin user
Go to Infrastructure > Chart Server
Set up URL to active chart server on Machine 2

Tags: instance, Balance, Manager, Balancing, 17, Central, server, load, nginx, frontend, Silk, chart, SCTM, property

↧

Silk Central 17.0 | Managing Silk Central Services

June 23, 2016, 10:49 am

≫ Next: Installing Silk Central 17.0 using IIS

≪ Previous: Load Balancing Servers in SC17

Revision 1 posted to Silk Central Knowledge Base by Matthew McGibbon on 6/23/2016 12:49:15 PM

With the relase of Silk Central 17.0, Silk Central Service Manager is no longer used, only controls the Execution Server.

This is all controlled now by the Instance Administration section.

You can access this whilst logged in remotely yo your Silk Central server, using the URL:

http://localhost:19100/?lang=en

The actions tab is the area where you will control the services which are running. If you wish you can stop a single service or the whole instance.

If you view the settings for your instance, you will see the options available through the new Instance Administration tool.

From this window you can now put your instance in maintenance mode, this is also a new feature available in Silk Central 17.0.

This will display a message to users when the browse to the Silk Central server, so that they are aware there is maintenance happening on the server.

If you have any questions about this feature or any other new features for Silk Central 17.0, you can contact us through https://supportline.microfocus.com/

Tags: instance, maintenance, Silk, services, Silk Central 17.0

↧

Installing Silk Central 17.0 using IIS

August 11, 2016, 12:34 pm

≫ Next: Silk Central Test Manager -ArrayIndexOutOfBoundsException

≪ Previous: Silk Central 17.0 | Managing Silk Central Services

Revision 1 posted to Silk Central Knowledge Base by Matthew McGibbon on 8/11/2016 2:34:48 PM

With the release of Silk Central 17.0, the installation of IIS no longer uses the same process, as it will now use Application Request Routing and URL Rewrite for configuring the installation.

This will mean you need to install additonal extensions in IIS.

Application Request Routing: http://www.iis.net/downloads/microsoft/application-request-routing

URL Rewrite: http://www.iis.net/downloads/microsoft/url-rewrite

Once you have installed both of the extensions you will now see these available within IIS, after clicking on your Web Server.

Now that both of these are installed and configured on IIS, you will now install Silk Central 17.0, using the Silk Central 17.0 available through http://supportline.microfocus.com.

During the installation you will be presented with a notification to say you have IIS enabled on your system.

If this is available it does not mean that all the pre-requisites for the installation are enabled, so please ensure you have verified this before selecting to use IIS.

Once the installation has completed the installation of Silk Central, you should verify that this has been configured correctly in IIS.

Open IIS, and on the hostname of the machine, select the Application Request Routing feature and open Server Proxy Settings…

At the very bottom of this you should have a Proxy Chain setting which shows the proxy server which this routes requests:

On the Default Web Site as well in IIS now you should also see the URL Rewrite available:

By selecting the rule and under actions click edit, you will see the properties of the redirect:

If all of this is now configured correctly if you browse to http://{Hostname}/, hostname the machine you installed Silk Central on, you should now be presented with the system administration page to connect your database:

Tags: url, IIS, Silk Central, configuration, ARR, Silk, Proxy, installation, install

↧

Silk Central Test Manager -ArrayIndexOutOfBoundsException

September 15, 2016, 8:21 am

≫ Next: Support NGINX | Silk Central HTTP to HTTPS URL redirect

≪ Previous: Installing Silk Central 17.0 using IIS

Current Revision posted to Silk Central Knowledge Base by LeeM on 9/15/2016 10:21:01 AM

Whilst in the Issues Reports.

There is a known permanent restriction, users have encountered the following error.

"java.lang.ArrayIndexOutOfBoundsException"

From an existing report with two criteria specified I performed a copy and paste as child on the parent folder and the mentioned error was generated.

This is down to being an issue with the Parameters tab.

There is a confirmed solution for this and follow the steps below:-

- Select the report to be copied ("Your report name")
- Select tab "Parameters"
- Click on button "Edit Parameters"
- In the dialog click on "OK"

Now try again to copy this report.

If the above did not resolve the problem open the edit parameter dialog again, change the priority/usage from example:- high to low. Click ok. Afterwards open the parameter dialog again and set priority back to what it should be, example:- high again.

Then retry to copy.

↧

Support NGINX | Silk Central HTTP to HTTPS URL redirect

September 21, 2016, 6:59 pm

≫ Next: Silk Central Install | Configure Image on Login Screen

≪ Previous: Silk Central Test Manager -ArrayIndexOutOfBoundsException

Current Revision posted to Silk Central Knowledge Base by Matthew McGibbon on 9/21/2016 8:59:09 PM

Silk Central now makes it easier than ever to redirect your installation(s) from HTTP to HTTPS, using the NGINX configuration file.

As NGINX now directs all the traffic on the Silk Central installation if you have multiple instances configured, you only need to make the change in one file to support URL redirects for all the instances.

Once you have configured SSL using the following article, Enable SSL you will want to ensure that all users who go to the default port 19120, are redirected to your SSL url.

To do this we will modify the nginx.conf.template in your installation directory:

C:\Program Files (x86)\Silk\Silk Central 17.0\instanceadministration\nginxFiles\conf

This file is copied over to the install directory on restart of the Instance Administration service, and picked up on a restart of the Silk Central services.

Modify this file to look like the following:

There will now be two server configurations, one for the old HTTP port which will redirect the HTTPS port, which will be configured with your cert and key.

Once configured recycle the Instance Administration service:

This will recycle the NGINX service, and we will now want to recycle the Silk Central services in the instance administration cllient:

Once the stop and start are performed, all users will now be re-direct to the https url if they access Silk Central over port 19120.

Any issues or questions on this, please contact Micro Focus Support.

Tags: url, Silk Central, security, HTTPS, HTTP, nginx, Silk, SSL

↧