Personal Experiences ...

Wednesday, September 3, 2014

HP Fortify Software Security Center (SSC) install - Error while trying to seed process templates

Seeding a New Fortify Software Security Center (SSC) Database

In SSC configuration tool, option database setup, Seed process Templates was giving an unexpected error.

The HP-Fortify-Server-WAR\logs\ssc-configuration.log file had the below

INFO 2014-09-03 22:55:20,586 [com.fortify.server.configuration.db.DBUtil] - Error occurred during initialization of VM
Could not reserve enough space for object heap

ERROR 2014-09-03 22:55:20,596 [com.fortify.server.configuration.db.DBUtil] - Error seeding db

ERROR 2014-09-03 22:55:20,596 [com.fortify.server.configuration.db.DBUtil] - Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.

After a lot of googling, found that the java VM is not able to allocate enough memory while starting from the host OS. Turns out all I had to do to fix is to edit the "ssc-configuration.cmd" file in "HP-Fortify-Server-WAR" folder and change MAX_MEMORY & MAX_PERMGEN to 512M from the default of 1024M. The seeding process went fine after this update :)

Wednesday, August 6, 2014

With only ASPX (asp.net) code, connect to SQL server database, and list table contents with query (no compilation or dll needed)

Mypage.aspx

<html xmlns="http://www.w3.org/1999/xhtml">
<head><title></title></head>
<body>
    <form id="form1" runat="server">
        <asp:GridView ID="GridView1" runat="server" DataSourceID="SqlDataSource1" EnableModelValidation="True" AllowPaging="True" AutoGenerateColumns="true">            
        </asp:GridView>
        <asp:SqlDataSource ID="SqlDataSource1" runat="server" ConnectionString="<%$ ConnectionStrings:maniConnectionString %>" SelectCommand="SELECT * FROM [Server_Capacity_1]"></asp:SqlDataSource>
    </form>
</body>
</html>

Sample web.config connecting to SQL Server

<?xml version="1.0"?>
<configuration>
  <connectionStrings>
    <add name="MyConnectionString" connectionString="Data Source=myservername.com;Initial Catalog=MyDBName;Persist Security Info=True;User ID=myuserid;Password=myPassword"
      providerName="System.Data.SqlClient" />
  </connectionStrings>
</configuration>

Hyperion interactive reporting studio BQY file grows large/huge over a period of time

If you use Brio to develop reports and save the file multiple time's you may have noticed that the file have grown huge over a period of time, and hence takes a long time to save. To reduce the file size, follow the below steps:

Warning: You will temporarily lose all data saved in the report (ie; generated report). Please don't try if you cannot generate it back and this data is important

Open the bqy file in hyperion interactive reporting studio (I have tied this on 11.1.2)
File --> Save Options --> Save Query Results with Document
A small popup will open. In the left box that say query results, uncheck all boxes and hit OK
Save the document. Now if you see the file size, it will be much smaller
Close the report (or if you want, you can close the hyperion interactive reporting studio itself)
Follow the below steps if you need to save the data as well
Re-open the bqy report
Process your report again so it will generate results
File --> Save Options --> Save Query Results with Document
A small popup will open. In the left box that say query results, check all boxes and hit OK
Save the file
You should have the data back, and the file size will be still much lower

Thursday, May 15, 2014

Creating a self signed certificate for development with subject alternative names

this is for IIS and assumption is Visual Studio is installed

cd C:\Program Files (x86)\Microsoft SDKs\Windows\v7.1A\Bin

makecert.exe -n "CN=My Development Root CA,O=My,OU=Development,L=Houston,S=TX,C=US" -pe -ss Root -sr LocalMachine -sky exchange -m 120 -a sha1 -len 2048 -r

makecert.exe -n "CN=mypc01, CN=mypc01.mydomain.net, CN=localhost, CN=mypc01.mycompany.com" -pe -ss My -sr LocalMachine -sky exchange -m 120 -in "My Development Root CA" -is Root -ir LocalMachine -a sha1 -eku 1.3.6.1.5.5.7.3.1

Saturday, April 26, 2014

ZyXEL NSA320 resetting admin password

Locate the reset button hole between the power connector and Ethernet cable at the back of the NSA box. Take a small pin and push the button until you hear a single beep (it will beep in about 1 or 2 seconds). Now remove the pin (ie; dont push anymore). Now, you can login with your default admin userid/password of admin/1234

None of your data or settings are lost by doing this!

Saturday, March 8, 2014

Provider load failure on SQL Server 2008 R2 reporting services (SSRS) installation

Below was the error on the log:

2014-03-09 03:08:36 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\Microsoft SQL Server\MSRS10_50.MSSQLSERVER\Setup
2014-03-09 03:08:36 Slp: Sco: Attempting to get registry value SQLPath
2014-03-09 03:08:36 RS: Setting InstanceId.
2014-03-09 03:08:36 RS: Setting Authentication Type.
2014-03-09 03:08:36 Slp: Sco: Attempting to get account sid for user account NT AUTHORITY\NETWORK SERVICE
2014-03-09 03:08:36 Slp: Sco: Attempting to get sid for user account NT AUTHORITY\NETWORK SERVICE
2014-03-09 03:08:36 Slp: Sco: GetSidForAccount normalized accountName NT AUTHORITY\NETWORK SERVICE parameter to NT AUTHORITY\NETWORK SERVICE
2014-03-09 03:08:36 RS: Setting AsOleDb folder.
2014-03-09 03:08:36 RS: Persisting configurations.
2014-03-09 03:08:36 Slp: Configuration action failed for feature RS_Server_Adv during timing ConfigRC and scenario ConfigRC.
2014-03-09 03:08:36 Slp: Provider load failure
2014-03-09 03:08:37 Slp: The configuration failure category of current exception is ConfigurationFailure
2014-03-09 03:08:37 Slp: Configuration action failed for feature RS_Server_Adv during timing ConfigRC and scenario ConfigRC.
2014-03-09 03:08:37 Slp: System.Management.ManagementException: Provider load failure
2014-03-09 03:08:37 Slp: at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
2014-03-09 03:08:37 Slp: at System.Management.ManagementObjectCollection.ManagementObjectEnumerator.MoveNext()
2014-03-09 03:08:37 Slp: at Microsoft.ReportingServices.WmiProvider.WmiProviders.GetInstance(String machineName, String instanceName, RSWmiNamespaces rsNamespace, ConnectionOptions connOptions, ObjectGetOptions getOptions)
2014-03-09 03:08:37 Slp: at Microsoft.ReportingServices.WmiProvider.WmiProviders.GetReportServerAdmin(String machineName, String instanceName, ConnectionOptions connOptions, ObjectGetOptions getOptions)
2014-03-09 03:08:37 Slp: at Microsoft.ReportingServices.WmiProvider.WmiProviders.GetReportServerAdmin(String machineName, String instanceName)
2014-03-09 03:08:37 Slp: at Microsoft.SqlServer.Configuration.RSExtension.Configuration.ConfigurationWMI.Connect(String instanceName)
2014-03-09 03:08:37 Slp: at Microsoft.SqlServer.Configuration.RSExtension.Configuration.ConfigurationAPI..ctor(String configFilePath, String instanceName)
2014-03-09 03:08:37 Slp: at Microsoft.SqlServer.Configuration.RSExtension.Configuration.ReportServerConfiguration.GetConfigurationAPI(String instanceName)
2014-03-09 03:08:37 Slp: at Microsoft.SqlServer.Configuration.RSExtension.Configuration.ReportServerConfiguration.Persist(String instanceID, String instanceName)
2014-03-09 03:08:37 Slp: at Microsoft.SqlServer.Configuration.RSExtension.SQLRSConfigurationPrivate.Install_ConfigRC(Dictionary`2 actionData, PublicConfigurationBase spcb)
2014-03-09 03:08:37 Slp: at Microsoft.SqlServer.Configuration.RSExtension.SQLRSConfigurationPrivate.InstallImpl(ConfigActionTiming timing, Dictionary`2 actionData, PublicConfigurationBase spcb)
2014-03-09 03:08:37 Slp: at Microsoft.SqlServer.Configuration.RSExtension.SQLRSConfigurationPrivate.Install(ConfigActionTiming timing, Dictionary`2 actionData, PublicConfigurationBase spcb)
2014-03-09 03:08:37 Slp: at Microsoft.SqlServer.Configuration.SqlConfigBase.PrivateConfigurationBase.Execute(ConfigActionScenario scenario, ConfigActionTiming timing, ConfigBaseAction action, Dictionary`2 actionData, PublicConfigurationBase spcbCurrent)
2014-03-09 03:08:37 Slp: at Microsoft.SqlServer.Configuration.SqlConfigBase.SqlFeatureConfigBase.Execute(ConfigActionScenario scenario, ConfigActionTiming timing, ConfigBaseAction action, Dictionary`2 actionData, PublicConfigurationBase spcbCurrent)
2014-03-09 03:08:37 Slp: at Microsoft.SqlServer.Configuration.SqlConfigBase.SlpConfigAction.ExecuteAction(String actionId)
2014-03-09 03:08:37 Slp: at Microsoft.SqlServer.Configuration.SqlConfigBase.SlpConfigAction.Execute(String actionId, TextWriter errorStream)
2014-03-09 03:08:37 Slp: Exception: System.Management.ManagementException.
2014-03-09 03:08:37 Slp: Source: System.Management.
2014-03-09 03:08:37 Slp: Message: Provider load failure .

Turns out http://support.microsoft.com/kb/980142 describes the same error.

Solved by

running SQL Server R2 installation, do not select Reporting services at this time, select something else (eg: client utilities), complete install
Install SQL Server R2 Service Pack 2 (SP2)
Go back to R2 install, this time select Reporting Services, complete install (no error this time - yay)
Install SP2 again and complete install

Sunday, February 23, 2014

Clumsy Ninja, level 22, bounce the ninja off the trampoline sideways

Get a trampoline, drag the Ninja and smash him onto the trampoline so he bounces off outside and lands on feet. that's it

It wont work if the ninja lands on the trampoline and the white circle appears around the trampoline indicating the ninja has started to do the "regular" bouncing. In this case, even if he lands on his feet left/right, you wont pass it. Key is not to start the regular bounce and have him jump off to side and land on feet