System.Data.SqlClient.SqlException (.Net SqlClient Data Provider): Could not find stored procedure

Products

• Patch Management Solution for Windows
• IT Management Suite
• IT Analytics
• Inventory Solution
• Asset Management Solution
• Deployment Solution
• CMDB Solution
• Task Server
• Altiris Network Discovery
• Software Management Solution

Issue/Introduction

After installing or upgrading IT Management Suite (ITMS), administrators may encounter SQL errors similar to:

System.Data.SqlClient.SqlException (.Net SqlClient Data Provider):

Could not find stored procedure 'StoredProcedureName'

 

Depending on the missing database object, symptoms may include:

• Console pages failing to load

• Reports failing to execute

• Solutions not functioning as expected

• Scheduled tasks not running

• Policy updates failing

Environment

ITMS 8.6.x, 8.7.x, 8.8.x

Cause

This error indicates that the SQL Server database for the Symantec Management Platform (SMP) is missing one or more stored procedures required by the platform or an installed solution.

This condition most commonly occurs due to:

• Incomplete upgrade execution

• Interrupted solution installation

• Failed database migration

• Manual database restore without reapplying platform schema updates

• Permissions issues preventing schema creation

• Database restored from backup without re-running configuration.

The issue is not typically caused by SQL Server corruption but rather by a schema mismatch between the installed binaries and the database.

 

Resolution

Perform the following steps:

Step 1 – Identify the Missing Stored Procedure

1. Navigate to:

   C:\ProgramData\Symantec\SMP\Logs

2. Open the most recent aXX.log file.

3. Search for:

   Could not find stored procedure

    

Example log entry:

System.Data.SqlClient.SqlException: Could not find stored procedure 'spXYZ_ReportExecution'

 

---

Step 2 – Verify Procedure in SQL Server

1. Open SQL Server Management Studio (SSMS).

2. Connect to the SQL instance hosting the Symantec_CMDB database.

3. Execute:

USE Symantec_CMDB
GO
SELECT name
FROM sys.objects
WHERE type = 'P'
AND name = 'spXYZ_ReportExecution'

 

Expected Result

Procedure is listed.

Actual Result (Issue)

No rows returned.

Check	Expected	Problem Indicator
Procedure exists	Listed in results	No rows returned
Schema	dbo	Missing or incorrect schema

---

Step 3 – Determine Owning Solution

Many stored procedures are solution-specific.

Examples:

• Reporting-related procedures → IT Analytics or Reporting components

• Inventory procedures → Inventory Solution

• Patch procedures → Patch Management Solution

How to Verify Installed Products 

Using Symantec Installation Manager (SIM)

1. Log on to the SMP Server.

2. Launch:
   
   Symantec Installation Manager

3. Go to :

   • Installed Products

4. Review:

   • Symantec Management Platform version

   • Installed Solutions

   • Installed versions
     
     

---

Step 4 – Run Solution Repair (Preferred Resolution)

If the stored procedure belongs to a specific solution:

1. The proper repair path in ITMS 8.7/8.8 is:

   1. Launch Symantec Installation Manager (SIM)

   2. Select:

      • Repair Installed Products

   3. Choose:

      • Affected solution

   4. Complete repair wizard

Allow repair to complete fully. Monitor:

C:\ProgramData\Symantec\SMP\Logs\aXX.log

 

Look for:

• Executing SQL Script
• Schema update completed

 

---

Step 5 – Run Platform Repair (If Solution Unknown)

If ownership cannot be determined:

1. Launch Symantec Installation Manager (SIM).

2. Select:

   • Repair Installed Products

3. Choose:

   • Symantec Management Platform

4. Complete repair wizard.

This revalidates database schema.

---

Step 6 – Verify SQL Permissions

Ensure the SMP service account:

• Has db_owner on Symantec_CMDB

• Is not denied CREATE PROCEDURE permission

Run in SQL:

USE Symantec_CMDB
EXEC sp_helprolemember 'db_owner'

 

Confirm SMP service account is listed.

---

Step 7 – Validation

After repair:

1. Re-run SQL query from Step 2.

2. Confirm stored procedure now exists.

3. Restart IIS:

    

   iisreset

    

4. Test:

   • Console page

   • Report execution

   • Solution functionality

Issue should no longer reproduce.

 

 

---

Troubleshooting Summary Table

Symptom	Likely Cause	Resolution
One procedure missing	Solution install failed	Repair specific solution
Many procedures missing	Platform upgrade incomplete	Platform repair
Procedure exists but error persists	Schema mismatch or permissions	Validate schema & permissions
Reoccurs after reboot	Database version mismatch	Validate DatabaseVersion table

---