HASP - Business Studio Login-Editing Order - Burning Keys

8
Date: Aug 04, 2010 #TN_HASP SRM BS#1: Revision A Distribution : Technical Support Product : HASP SRM Title : Impossible to work with Business Studio because of communication\general errors In case you are experiencing problems to login to Business Studio Database or errors while working with your HL licenses in Business Studio (like Editing Orders or Burning Keys), please read this guide. Problem 1: You are connected to Business Studio and you get one of the following errors

description

HASP - Business Studio Login-Editing Order - Burning Keys

Transcript of HASP - Business Studio Login-Editing Order - Burning Keys

Page 1: HASP - Business Studio Login-Editing Order - Burning Keys

Date: Aug 04, 2010

#TN_HASP SRM BS#1: Revision A

Distribution : Technical Support

Product : HASP SRM

Title : Impossible to work with Business Studio because of communication\general errors

In case you are experiencing problems to login to Business Studio Database or errors while working with your HL licenses in Business Studio (like Editing Orders or Burning Keys), please read this guide.

Problem 1: You are connected to Business Studio and you get one of the following

errors

Page 2: HASP - Business Studio Login-Editing Order - Burning Keys

Solution 1: 1) Close Business Studio

2) Restart the following Windows Services and ensure they are in “started” status:

• HASP License Manager or Sentinel HASP License Manager

• HASP SRM Business Studio Server or Sentinel HASP SRM Business Studio

Server

• SQL Server (HASPSRMDATABASE)

• SQL Server Browser

3) Using Admin Control Center at http://localhost:1947 , verify that you see your HASP

keys (Master key and HASP HL keys)

4) Register the two COM DLL files by running the following with Administrator rights:

a. “regsvr32 C:\Program Files\Aladdin\HASP

SRM\API\Runtime\Com\hasp_com_windows.dll”

b. “regsvr32 C:\Program Files\Aladdin\HASP

SRM\VendorTools\Common\Factory\hasp_com_factory.dll”

Page 3: HASP - Business Studio Login-Editing Order - Burning Keys

5) Ensure you have introduced your Master Key (through Sentinel MasterHASP Wizard)

and you have the proper libraries initialized. In case you work with multiple Vendor

codes, check that you have selected the proper one:

Problem 2: If error 80400 is returned

Solution 2: Go to “C:\Program Files\Aladdin\HASP SRM Server\Servers\HASP SRM Server” and

check existence of the file “hasp_windows_master.dll”. If not, copy it from another machine, or

re-install HASP suite.

Problem 3: If error 7102 and 7103 are returned in the Business Studio logs

Solution 3: You have used unsupported characters for the SQL password. Since Business Studio

DB is partially written in Perl, there are some limitations like the following characters:

$ dollar sign

‘ single quotation mark

“ quotation mark

; Semicolon

Problem 4: If Business Studio login fails from the Server

Solution 4: Note: After every execution of each below step, please check if the problem is solved.

It is highly recommended to be accompanied with system administrator for the following

steps.

1) Restart the following Windows Services and ensure they are in “started” status:

• HASP License Manager or Sentinel HASP License Manager

• HASP SRM Business Studio Server or Sentinel HASP SRM Business Studio

Server

• SQL Server (HASPSRMDATABASE)

Page 4: HASP - Business Studio Login-Editing Order - Burning Keys

• SQL Server Browser

2) Type the following link in a Internet Explorer (case sensitive!):

https://localhost/HASPLogin?test

And press on “Continue to this WebSite (not recommended)”.

You should get “database connection: passed”.

3) Check what is the port number “CLIENT_PORT=” within the following file:

%ProgramFiles%\Aladdin\HASP SRM Server\Servers\HASP SRM Server\hasp_svr.cfg

4) Before login to the BS, press on “Options”, change the Server Address into “localhost”,

verify that the port is defined as per above CLIENT_PORT value, try to login.

5) In order to check whether the CLIENT_PORT is occupied by the BS, follow the next steps:

a. run from command-line “netstat –ano”

b. Under “Local Address” column check for “0.0.0.0:<CLIENT_PORT>”, and see on the

same line what is the PID (the process ID number).

There should be only one line with that port!

c. Open Task Manager, choose “Processes” and add “PID” in the menu “view” ->

“select columns”. Now check the process-name with the PID found above. It should

be “hasp_svr.exe”.

Page 5: HASP - Business Studio Login-Editing Order - Burning Keys

6) Use the free Microsoft tool “SQL Server Management Studio Express”, and check if you

can connect to <BS server>\<HASPSRMDATABASE>.

Go to Databases -> SRMServer -> Tables, right click on “dbo.ServiceData and choose

“Open Table”. Verify that both the server name and the port number are correct.

7) Register the two COM DLL files by running the following with Administrator rights:

c. “regsvr32 C:\Program Files\Aladdin\HASP SRM\API\Runtime\Com\hasp_com_windows.dll”

d. “regsvr32 C:\Program Files\Aladdin\HASP

SRM\VendorTools\Common\Factory\hasp_com_factory.dll”

8) Go to the following folder and run “HaspBssSample.exe”:

“%Program Files\Aladdin\HASP

SRM\Samples\BusinessStudioServer\Local\HaspBssSample\bin\Release”.

Check if you can login to BS DB using BS API (such as: “HASP”, “HASP” “localhost”, 443)

9) Check in the Task Manager that there is at least one hasp_cld process. If no hasp_cld

process exist, from cmd-line go to “C:\Program Files\Aladdin\HASP SRM

Page 6: HASP - Business Studio Login-Editing Order - Burning Keys

Server\Servers\HASP SRM Server”, run hasp_cld.exe and check if the process is showed

up.

If it does, try to login again to BS DB.

10) Open Internet Explorer -> tools -> Internet Options, go to “Connection” tab, press on

“Lan Settings”. In case “Use a proxy server for your LAN” is checked, the “Bypass Proxy

server for local addresses” should be checked as well.

11) Disable any firewall, antivirus and protection tools, and try to login again.

Re- Enable them if it didn’t help.

12) If you are not using the latest SRM software and the login failure is not resolved using

this documentation, please upgrade to the latest Sentinel HASP SRM suite and check

again.

www.hasp.com/srm

Problem 5: If Business Studio login fails only from clients and it works from the

server

Solution 5: Note: After every execution of each below step, please check if the problem is solved.

It is highly recommended to be accompanied with system administrator for the following

steps.

1. Open ACC at http://localhost:1947 on the client, connect any HASP key and check if the

key is displayed.

If ACC page is not displayed:

• Restart the “Sentinel HASP License Manager” Windows Services on the client

machine and check if it stays up and running.

• If ACC page is still not displayed, uninstall the Sentinel HASP Run-time and then

Install the Sentinel HASP Run-time

If ACC page is showed but the HASP key is not listed:

• Check another HASP key

• If the other key also fails to be detected, uninstall and install the HASP Run-time

2. If the Windows system date\time on the client machine is earlier than the server’s one,

then the client will not be able to login (it can be in a different time zone, but accurate

on time and date).

Page 7: HASP - Business Studio Login-Editing Order - Burning Keys

Please make sure time settings are correct.

3. Go to the server, and check the port numbers within the following file on the server:

%ProgramFiles%\Aladdin\HASP SRM Server\Servers\HASP SRM Server\hasp_svr.cfg

Take note about the port number reported in the “CHILD_PORT=”

Take note about the port number reported in the “CLIENT_PORT=”

Make sure you are using the specific CLIENT_PORT to login to Business Studio.

4. Go to the client, and check the connection between the client and the server:

a. Ping from the client to the server NAME

b. Ping from the client to the server’s IP Address

If (b) works but (a) doesn’t, please consult your system administrator as it seems to

be an issue of name resolving (DNS issues). Possible solutions can be:

i. Ask your system administrator to fix the DNS setting (recommended).

ii. Fix the DNS settings local by editing the host file on the local PC with the

help of your system administrator.

If (a) & (b) don’t work, please consult your system administrator and also check

routing settings

c. Check port CLIENT_PORT connection from the client to the server using “telnet” in

cmd-line: telnet <BS server Host name> <Port Number>

Make sure no error is displayed:

d. Check the network connection issue with IT in your organization (firewall, protection

software like Anti Virus, administration rights, network configuration, and so on).

Page 8: HASP - Business Studio Login-Editing Order - Burning Keys

5. Use the free Microsoft tool “SQL Server Management Studio Express”:

a. From the client, connect to: <BS server>\<HASP SRM DATABASE>.

(Note: the default name of the HASP database is “HASPSRMDATABASE”, if you

have set another name you need to enter the correct credentials)

If it fails, please consult your DBA about the SQL connectivity issues.

b. Go to Databases -> SRMServer -> Tables - right click on “dbo.ServiceData and

choose “Open Table”. Check that both the server-name and the port-number

are the right ones.

ATTENTION: The server name must not be “localhost”

6. Register the two COM DLL files by running the following:

e. “regsvr32 C:\Program Files\Aladdin\HASP SRM\API\Runtime\Com\hasp_com_windows.dll”

f. “regsvr32 C:\Program Files\Aladdin\HASP

SRM\VendorTools\Common\Factory\hasp_com_factory.dll”

7. Go to the following folder and run “HaspBssSample.exe”:

“%Program Files\Aladdin\HASP

SRM\Samples\BusinessStudioServer\Local\HaspBssSample\bin\Release”.

Try to login using BS API instead of the GUI (like “HASP”, “HASP”, <BS server name>,

<port number>)

8. Verify the versions of the Business Studio application and Business Studio Server: if the

BS application has a higher version you should at least upgrade it to the BS Server

version.

9. If you are not using the latest SRM software and the login failure is not resolved using

this documentation, please upgrade to the latest Sentinel HASP SRM software and

check again.

www.hasp.com/srm