Company: Link Technologies
Case No: L08740. Project: 08.20: LinkSOFT Version 8.2
Logged By: Rashna (Edge Business Solutions) on 09 Aug 2017 10:16AM
Priority: High
Product: Point of Sale
Group: Enhancement
Time Taken: 5.00 (Weight: 5.00)
Version: 8.290.0115
Assigned To: Sanjay (Link Technologies)
Circulation: Alvis, Development, Rashna
Resolve By: Thursday, 10 August 2017 12:00 AM [2898 days since logged date]
Status: Closed
Subject: Jobs are stopped with "Network" owners
Summary:    

There are scenarios where jobs, mainly replication jobs stop executing.

For example , LINKSOFT  schedule has owner as "VMQA1-WIN732\linkadmin".  The schedule stopped to run. Refer to Figure 1 below for details.

Improvement - By default set the "owner" of replication jobs to use the "Linked Server Username" that  is used to setup servers.Refer to Figure 2

Figure 1: Schedule Stops


Figure 2: Linked Server username

 

Test Plan

 Test NumberDescription   Results 
 1

 Setup replication servers for HQ and Branch.

Linked Server Username - Linkreplication 
Linked Server Password - Infotech0410

 
 2Enable the replication processes. Use "Replication" as the schedule name. Ensure processes run as timed 
 3

Verify all jobs fro replication has been created.

  • Replication
  • Replication Child Data OUT
  • Replication Parent Data OUT
  • Replication IN
 
 4 Verify the owner of the jobs is "Linkreplication" and all jobs are executing. 
 5 Verify that default database schedule is also running. 



Audit Notes:
11 Aug 201710:29AM Comment 1 by Sanjay (Link Technologies) Assigned To: Development Followup Date: 11-08-2017 10:29 AM Time Taken: 1.00
We will investigate why the windows user cannot be used as the schedule job.

11 Aug 201710:30AM Comment 2 by Alvis (Link Technologies) Case 8740 added to project 8.17
17 Aug 201711:35AM Comment 3 by Sanjay (Link Technologies) Assigned To: Rashna (Edge Business Solutions) Followup Date: 17-08-2017 11:35 AM Time Taken: 1.00
Development work for this case has been completed.
The change will be available in version: 8.17
Documentation update required(Yes/No. Add change details below): No
QA required(Yes/No.Include areas that require testing): Yes

1. The following changes were made(Include Database object names, Program classes and any other relevant information):|

  1. Changed New, Demo and Upgrade script to create the scheduled job with "LINKADMIN" owner.
  2. Changed "replication create" process to create the scheduled jobs with "LinkReplication" owner.
  3. Changed the "scheduled job create" process from processes menu to create the job with "LINKADMIN" owner.

22 Aug 201709:49AM Comment 4 by Rashna (Edge Business Solutions) Assigned To: Sanjay (Link Technologies) Followup Date: 22-08-2017 09:49 AM Time Taken: 3.00
QA for product and Patch Releases
Step 1 - Developer to system test changes until not issues are found - Alvis and Sanjay to sign off on System Test
Step 2 - Product expert allocated by Consulting Manager for Product QA.
               Consulting Manager to allocate resource
               Consulting Manager to sign off on UAT and Generic Test

STEP 1 - DETAILS OF QA can be entered in case comments. Summary to be maintained in the table below.

Case tested in QA1 with database LINKSOFT. Tested in 817 Beta 1

  1. Changed New, Demo and Upgrade script to create the scheduled job with "LINKADMIN" owner. Pass
  2. Changed "replication create" process to create the scheduled jobs with "LinkReplication" owner. Pass
  3. Changed the "scheduled job create" process from processes menu to create the job with "LINKADMIN" owner. Pass
Table 1 - Summarised list of issues
NoIssue Description Resolved? 
1 Demo database should have "Linkadmin" as the owner of schedule 1. Pass
2 Create replication with linkedserver name as "Link Replication". All Replication Jobs should have owner as "LinkReplication" Pass
3 Create a new schedule for health checks as "HealthCheck", assign this to process "POS System Health Check". Owner of jobs should be "linkadmin" Pass
4 Verify all jobs are running  Pass

WORKFLOW:

  1. Original case assigned to Development
  2. When the product is ready for release, System test details are entered into comments and the CASE HEADER Table updated.
  3. If system test passes, assign case to Consulting Manager for UAT
  4. If UAT Passes, Assign case for Documentation or close case

    09 Oct 201908:14AM Comment 5 by Sanjay (Link Technologies) Quality control status: Pass. QC Not required - This case was created before quality check was implemented in version 11 on 30/06/2019
    If you have any queries regarding this support incident, please email Support@LinkTechnologies.com.au and include the Case No: L08740 in the subject line of all emails regarding this issue.

    Document size: 11.3 KB
    For call complaints, please contact the Managing Director of the company using this form