After completing the WSS and MOSS SP1 installation on a server farm I am getting the error shown belowin the application event log on the application server. I have 2 WFEs that do not register this error. Not sure if it matters but this is the standard edition of MOSS 2007. All of the sites and search functionality appear to be working. Any ideas? Source: Office SharePoint Server Category: Office Server General. Event ID: 7888 A runtime exception was detected. Details follow. Message: Invalid object name 'AR_CacheCounters'. Transaction count after EXECUTE indicates that a COMMIT or ROLLBACK TRANSACTION statement is missing. Previous count = 0, current count = 1. Techinal Details: System.Data.SqlClient.SqlException: Invalid object name 'AR_CacheCounters'. Transaction count after EXECUTE indicates that a COMMIT or ROLLBACK TRANSACTION statement is missing. Previous count = 0, current count = 1. at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString) at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result) at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe) at System.Data.SqlClient.SqlCommand.ExecuteNonQuery() at Microsoft.Office.Server.Data.SqlSession.ExecuteNonQuery(SqlCommand command) at Microsoft.Office.Server.ApplicationRegistry.MetadataModel.DataAccess.AbstractMaterializer.DistributedCacheInvalidate(Type metadataObjectType, Boolean objectCache) at Microsoft.Office.Server.ApplicationRegistry.MetadataModel.DataAccess.AbstractMaterializer.DistributedCacheInvalidate() at Microsoft.Office.Server.ApplicationRegistry.Infrastructure.SqlSessionProvider.SetSharedResourceProviderToUse(String sharedResourceProviderName) at Microsoft.Office.Server.UserProfiles.BDCConnector.RefreshConfiguration(String sspName) For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

I am also having the same error and out profile importing no longer works. Everythign else but this works perfectly. This only started failing after the update to office 2007 SP1 and wss SP1

I am getting the same error on a single-server installation after updating to SP1 of WSS and MOSS. Seems to correspond with when I am doing an incremental import of profiles, but I'm not seeing any problems with the profile importing.

One more point: before the SP1 update, I used to get Event ID: 7888 - "could not find store procedure 'proc_ar_BumpCacheInvalidationCounter'" at around the same time. I was told by Microsoft that I could ignore that error. I wonder if in fixing the BumpCache error, this other variation on Event ID 7888 is happening with SP1.

RichRockwell wrote: One more point: before the SP1 update, I used to get Event ID: 7888 - "could not find store procedure 'proc_ar_BumpCacheInvalidationCounter'" at around the same time. I was told by Microsoft that I could ignore that error. I wonder if in fixing the BumpCache error, this other variation on Event ID 7888 is happening with SP1. Same here, MS told me the BumpCache error would be fixed in SP1.Sounds likethey broke something else in the process of fixing that. Obviously both the bump cache and the new error are related to the profile import. And if you look in the trace logs you'll see the below entry about a Cache Invalidation Check immediately before theSQL error occurs. 01/09/2008 10:30:01.75 mssdmn.exe (0x0F84) 0x0D2CSharePoint Portal Server Business Data 79bvHigh Initiating BDC Cache Invalidation Check in AppDomain 'DefaultDomain'

I have the same exact 'AR_CacheCounters' error Mike reported in his post, and the interesting part about it is - I have yet to install Service Pack 1. It only happens when my profile import job is scheduled to run; however, another interesting things is, the profile import job appears to complete more or less successfully anyway. I'velived with the issue for six months without any visible related errors, but that's not to say I haven't had other long term issues. Without warning, sometimes the dreaded memory issue crops up again - bringing down any management ability one used to have from the IIS6 console. For those of you who havent experienced it, any IIS console that attempts to connect to the afflicted SharePoint box simply freezes. A simple, yet obtrusive and on occasional unsuccessful, restart of the SharePoint services temporarily resolves the issue. I don't know if it has anything to do with the 'AR_CacheCounters' stored procedure issue though. Those are my only two enduring issues with SharePoint according to Event Viewer that I have.

I am also seeing the profiles slowly import. It seems somethig was changed that screws up an incrimental import.

What's worse about this is that the Sharepoint support team at Microsoft is backlogged. I called in about this and my assigned engineer already missed our first scheduled time. Sounds like SP1 is causing a lot more support calls than they expected.

Any news about this subject? Having the same "problem" MOSS 3.0 SP1. Event occures during incremental profile update.

MarcodeGroot wrote: Any news about this subject? Having the same "problem" MOSS 3.0 SP1. Event occures during incremental profile update. I called MS support on this...they told me they're aware of the problem and will be releasing a KB article shortly to address it. They wouldn't give me an ETA, the most I got was "soon".

I've also noticed this problem on our Sharepoint server - is the fix available yet? We've got a problem where DLs / Security Groups that have been moved in AD are being duplicated in the portal (I posted on this a few months ago here: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2877114&SiteID=1). Could this fault be causing the problem? Cheers,

Hi MSDNers Any updated news on this one?I just enabled incremental user profile importing on my post-sp1 MOSS 2007 install - and I have started getting this error in the event viewer...Any KB yet?Thanks,Tod.

I am having the same issue... Has a KB been release?

Hello all, we faces the same Problem in two Farms. I see this Error in one AllInOneServerand in a midsized Farm with dedicated Servers for WFE, APP and SQL. For me it looks like SharePoint is not able to find this stored procedure in SQL-Server... I looked in the Databases and did not find any Stored Procedure which start with AR_ !!! I hope some of the Microsoft Support Guys read this, otherwise i will open a B-Case on Microsoft Premier Support. (andreas.haist@avanade.com) Thanks,Andreas

Yes,opening MPS caseis ofcourse what MS preffer.... But my observations confirm same behavior. Before Sp1 there was this "bump..." errror and now after SP1 this "AR_cache counters". And it happens only on MOSS 2007 standard. So,i am also waiting for solution.

Anyone have any update or news on this?

Does anyone have an update or fix for this? Below is the complete dump. I too started seeing this after SP1. Event Type:ErrorEvent Source:Office SharePoint ServerEvent Category:Office Server General Event ID:7888 Description:A runtime exception was detected. Details follow. Message: Invalid object name 'AR_CacheCounters'.Transaction count after EXECUTE indicates that a COMMIT or ROLLBACK TRANSACTION statement is missing. Previous count = 0, current count = 1. Techinal Details:System.Data.SqlClient.SqlException: Invalid object name 'AR_CacheCounters'.Transaction count after EXECUTE indicates that a COMMIT or ROLLBACK TRANSACTION statement is missing. Previous count = 0, current count = 1. at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString) at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result) at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe) at System.Data.SqlClient.SqlCommand.ExecuteNonQuery() at Microsoft.Office.Server.Data.SqlSession.ExecuteNonQuery(SqlCommand command) at Microsoft.Office.Server.ApplicationRegistry.MetadataModel.DataAccess.AbstractMaterializer.DistributedCacheInvalidate(Type metadataObjectType, Boolean objectCache) at Microsoft.Office.Server.ApplicationRegistry.MetadataModel.DataAccess.AbstractMaterializer.DistributedCacheInvalidate() at Microsoft.Office.Server.ApplicationRegistry.Infrastructure.SqlSessionProvider.SetSharedResourceProviderToUse(String sharedResourceProviderName) at Microsoft.Office.Server.UserProfiles.BDCConnector.RefreshConfiguration(String sspName) For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Ive got the same Eventid 7888 after updating to sp1 and iuAny news out there?

I have the same issueon MOSS (Enterprise) with a SQL2005 backend, this is SP1 and the server build was aided by MS as we had issues during the installation, we cannot really afford another 199 support call!Event ID; 7888A runtime exception was detected. Details follow. Message: Invalid object name 'AR_CacheCounters'.Transaction count after EXECUTE indicates that a COMMIT or ROLLBACK TRANSACTION statement is missing. Previous count = 0, current count = 1. Techinal Details:System.Data.SqlClient.SqlException: Invalid object name 'AR_CacheCounters'.Transaction count after EXECUTE indicates that a COMMIT or ROLLBACK TRANSACTION statement is missing. Previous count = 0, current count = 1. at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString) at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result) at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe) at System.Data.SqlClient.SqlCommand.ExecuteNonQuery() at Microsoft.Office.Server.Data.SqlSession.ExecuteNonQuery(SqlCommand command) at Microsoft.Office.Server.ApplicationRegistry.MetadataModel.DataAccess.AbstractMaterializer.DistributedCacheInvalidate(Type metadataObjectType, Boolean objectCache) at Microsoft.Office.Server.ApplicationRegistry.MetadataModel.DataAccess.AbstractMaterializer.DistributedCacheInvalidate() at Microsoft.Office.Server.ApplicationRegistry.Infrastructure.SqlSessionProvider.SetSharedResourceProviderToUse(String sharedResourceProviderName) at Microsoft.Office.Server.UserProfiles.BDCConnector.RefreshConfiguration(String sspName)

We have the same exact error. We have Moss 2007 w/SP1and installed the two infrastrucure updates that came out in July thinking this would resolve things. It did not. Anybody have an update on this?http://technet.microsoft.com/en-us/office/sharepointserver/bb735839.aspxtrimetal4

proc_ar_BumpCacheInvalidationCounter | AR_CacheCounters. Crazy, I have the same issue and I have install all 9 recommended ypgrades/updates on our farm. I will say that all other errors have stopped except this troublesome error. I wish MS would give us a day to day blog of the issues that they're aware of and working on. This way I wouldn't have to spend time researching an issue that there is no fix for. I mean come on! Just provide a simple forum to relay the info.Build It!

I agree this error is very annoying and wish there was some detailed information about it provided. Spooter

Hi,did anyone solve the problem ?

Affraid notI understand its a event log that can be ignored but its pretty anoyying to have.Spooter

This error is driving me crazy. I really wish Microsoft would address this.

I used to getproc_ar_BumpCacheInvalidationCounter. After bringing the server to the latest version (12.0.0.6332), now I am gettingAR_CacheCounters.Note, I am only seeing this now in my Index server. I have a mid size farm (2WFEs, 1 Indexer, 1SQL). Ultragc

I thought I'd reply and bump this thread up. I am also receiving this same Application Event ID error on my SSP server (it's a 7 host farm). This farm does not have any cumulative updates after SP1 on it. Has anyone seen this go away after applying any of the cumulative updates?I'm crossing my fingers for SP2.-PlateSpinner

Im fully upto date with patchs and still have the event log message. Im expecting it to go in the next service pack.RegardsSpooter

isnt there any solution yet? SP2?

SP2 didn't fix the problem in our dev (single server) farm. We're also still experiencing the error in both of our other multi-server farms. I think it's unacceptable that Microsoft hasn't fixed this problem in over a year and a half, regardless of the impact of the bug. -JP

I get the same error in an enterprice environment. Have microsoft made a offical statment on that this error can be ignored?

I've have the same problem. Yestarday we've installed September CU2009 for MOSS and problem still exists (mid size farm).

Same problem here, newly installed farm (1x front end, 1x database)with MOSS 2007 SP2 + cumulative updates.MCTS in Web Application Development in .NET 2.0

Somehow it looks like I fixed it. I think it was because I stopped the search service, recreated the index and then started it again. Try the following stsadm commands:stsadm -o execadmsvcjobs stsadm -o osearch -action start (just to be sure it's started) stsadm -o osearch -action stopIt'll ask you if you really want to lose your index, answer "y" (in the dutch version it states [j/n], but answering 'y' doesn't work).Now start the service via central administration again and make sure you reattach your SSP to the indexer service, because it will get detached when you stop it. After I've done this, the errors seemed to have disappeared from log, but I'm not 100% sure yet.MCTS in Web Application Development in .NET 2.0

Somehow it looks like I fixed it. I think it was because I stopped the search service, recreated the index and then started it again. Try the following stsadm commands:stsadm -o execadmsvcjobs stsadm -o osearch -action start (just to be sure it's started) stsadm -o osearch -action stopIt'll ask you if you really want to lose your index, answer "y" (in the dutch version it states [j/n], but answering 'y' doesn't work).Now start the service via central administration again and make sure you reattach your SSP to the indexer service, because it will get detached when you stop it. After I've done this, the errors seemed to have disappeared from log, but I'm not 100% sure yet. MCTS in Web Application Development in .NET 2.0 Is this the final solution?

Any solution for this issue? I have the same exact error on the Index server. We have a medium farm Moss 2007 w/SP2. 1 WFE + 1 Index + 1 SQL Server.