cancel
Showing results for 
Search instead for 
Did you mean: 

Could not find stored procedure “ts_GetPublishingQueue”

Former Member
0 Kudos

We installed uPerform 4.42.0.  When I go to Administration > Server Administration > Publishing > View Publishing Queue

Report Name displays, then immediately an error message window pops up "Object reference not set to an instance of an object."  Clicking "OK" reveals this message:

You have generated an error!

This error has been recorded in the system log.

     Could not find stored procedure ’ts_GetPublishingQueue’.

     Reports.shtml

     Line Number 0

Any ideas on how to fix it?

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi Michael,

Please follow the below steps.

1)#Stop Message Queuing service on the uPerform Web Application server.

2)#Stop RWD Monitoring service on the uPerform Web Application server.

3)#Stop WWW Publishing service on the uPerform Web Application server.

4)#Stop Vignette Collaboration service on the uPerform Web Application server.

5)#Stop the Common Apache SOLR service on the uPerform Search server.

6)#Start Message Queuing service on the uPerform Web Application server.

7)#Start RWD Monitoring service on the uPerform Web Application server.

8)#Start WWW Publishing service on the uPerform Web Application server.

9)#Start the Common Apache SOLR service on the uPerform Search server.

10)#Open http://<servername>:8983 in Internet Explorer. You should see the Welcome to SOLR screen once this is successful.

11)#Start Vignette Collaboration service on the uPerform Web Application server.

12)#Enter http://<uPerformWebAppURL>:8080

13)#You should see a Vignette Collaboration Login screen (Do Not Login);

if not, enter the command in Step (12) a few times until you see it.

14)#All the services have been successfully restarted once you can see the correct screens in Step (10) and (13).

15)#Now logon onto the uPerform website as an administrator (or yourself if you have admin rights)

16)#Please let us know whether you can see the normal uPerform website?

Failing this, you should check if there are any interesting errors in the following logs.

##Servererrors.xml log in Collaboration\www\uPerformWS\log\

##CollabConsole.txt from \\Collaboration\logs

##Gilog.txt from  \\Collaboration\logs

Kind Regards,

Matthew

liushu
Advisor
Advisor
0 Kudos

make sure the DB user has ONLY "public" rights.