This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

1IM 6.1.2 Job queue Service getting the 50000 error 'Session Id for queue \nnn does not agree

Hi,

Working on a new Installation of 1IM v 6.1.2, getting the below error even though I only have one queue.

 

Error excerpt:

[821002] Error requesting queue '\FIMINFWWADV28' for database 'fiminfwwadv28\DEVD1IM_1'.
    [810023] Error during execution of statement: exec vid_JobGetForCache_3 N'\FIMINFWWADV28', 90, -1, 0, N'', N'652d44e5-890a-4537-8177-4f2d9a089521'
    [810143] Database error 50000: detected in (SRV=FIMINFWWADV28, DB=DEVD1IM_1) Procedure vid_JobGetForCache_3, Line 31
    [810143] Database error 50000: Session ID for queue \FIMINFWWADV28 does not agree. DB: 13f8613c-01da-4904-84e5-784210e3b935 Query:652d44e5-890a-4537-8177-4f2d9a089521.



Recycle the service, made sure the job server is also configured in Designer:


Commit and compile after any changes. Still no go.

Does anyone have any ideas?

Thanks, Todd
Parents
  • Thanks for the thought Barry. I still cannot find any other Job service. The layout for this system is a stand alone 2012 R2 windows box, separate SQL server for the DB. One job service, the SQLserviceprovider, running everything. A test system to prove some things out. I had already had it running with the one queue, then tried to restore another DB to the SQL instance that was too large for the file systems and it blew up the SQL server. Hosted on a esxi wmware setup. So I rebuilt the SQLserver, new 1IM DB and redid the installation. I did not uninstall 1IM software.

    Now I am performing a full uninstall (manually removing the Quest directories) and starting over with the install including the service.

    I will post what happens. Thanks, Todd

Reply
  • Thanks for the thought Barry. I still cannot find any other Job service. The layout for this system is a stand alone 2012 R2 windows box, separate SQL server for the DB. One job service, the SQLserviceprovider, running everything. A test system to prove some things out. I had already had it running with the one queue, then tried to restore another DB to the SQL instance that was too large for the file systems and it blew up the SQL server. Hosted on a esxi wmware setup. So I rebuilt the SQLserver, new 1IM DB and redid the installation. I did not uninstall 1IM software.

    Now I am performing a full uninstall (manually removing the Quest directories) and starting over with the install including the service.

    I will post what happens. Thanks, Todd

Children
No Data