The smsysprocess table may have an entry. Login into DB Administration Tool, while it may tell you can’t run it while other SDE apps are running, it will clear out any orphan smsysprocess records that are more than 90 seconds old (all SDE apps check in every 60 seconds). Then attempt the Integration Console login
If you still get that error, look in the namsysprocess table for the latest running integration console record and note the PID value and server name.
Then look in the smsysprocess table for the same PID and server combination. You can then go to the server to see if there is an actual running integration engine running from somewhere else and stop it if necessary.
QReset - A Simplified AD Password Reset Solution
Click the QReset icon below for a product overview video.
RjR INNOVATIONS INC. | Connect your Business … all of IT
A BMC Premier Partner and BMC Certified Support Provider for SDE/Remedy/Footprints
<http://www.youtube.com/user/rjrinnovations>[Description: linkedin]<http://www.linkedin.com/groups?gid=2908077&trk=myg_ugrp_ovr>[Description: twitter]<http://twitter.com/RjRInnovations>[Description: google]<http://www.google.com/profiles/rjrinnovations>[Description: rss]<http://rjrinnovationsnews.blogspot.com/>[Description: facebook]<http://www.facebook.com/pages/RjR-Innovations/107107129324171?ref=nf>
I've tried logging into the DB Administration tool, it did tell me it was in use. When I try to run the Integration Engine service it's still logging that message. I have tried to run 'select * from dbo.namsysprocess' from SQL Server Management Studio and it reports: "Invalid object name 'dbo.namsysprocess'."
Looking in smsysprocess, I see an entry for "(101) Metadata Library[TSDE(pid:3780)]" with a processid of 3535. Looking on that server I do see a process with id 3780 (w3wp.exe), but not one with 3535. Stopping the World Wide Web Publishing Service ends the process 3780, but doesn't remove the entry from the database. I have manually removed it, but still get the error in the Integration Engine log file.
Dbo.Smsysprocess. I don’t see me original email so I apologize if I gave you the wrong table
you mentioned both, one exists and the other doesn't. In either case we still have the error when dbo.smsysprocess is completely empty.
1 of 1 people found this helpful
Please check this
Follow the steps below to fix this issue:
1. Login to SQL Server Management Studio.
2. Search for the SDE database under databases.
3. Open the table INTEGRATION_ENGINES | Update the Integration Server name to the correct value.
4. Restart the SDE Integration Engine Service in Windows services.
5. Verify that the error does not appear in the log.
Instead of updating to the correct value or what you think it is, just delete the row and restart the service. It will automatically put in the correct value
That explains it. I changed it from FQDN to just server name, and then it started with no issue. I went to test Ron's suggestion of deleting the row, and found that after stopping the integration engine the table was empty. I will be updating our restore script to truncate the table instead of updating it.
Thanks all...we were having the issue on our Development instance and this fixed it for us. Much appreciated