From: MedeBay on
Did you ever find a resolution. I am having the same problem.

Brian

"MrEd" wrote:

> I am having a similar experience. I upgraded to R2 and promoted a new server
> to be the RMS. After I did that I started getting this error.
>
> Event Type: Error
> Event Source: Health Service Modules
> Event Category: Data Warehouse
> Event ID: 31552
> Date: 7/29/2009
> Time: 6:25:33 AM
> User: N/A
> Computer: OPMGR
> Description:
> Failed to store data in the Data Warehouse. Exception 'SqlException':
> Timeout expired. The timeout period elapsed prior to completion of the
> operation or the server is not responding.
>
> One or more workflows were affected by this.
>
> Workflow name:
> Microsoft.SystemCenter.DataWarehouse.StandardDataSetMaintenance
> Instance name: State data set
> Instance ID: {FB2C874C-F774-A9E5-EB99-23BA24544B07}
> Management group: OpsMgr
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
>
>
> --
> Ed
>
>
> "David" wrote:
>
> > Hello,
> >
> > I am working on a project to keep track of the items in a warehouse. I am
> > modifying the "Inventory Control" template from the MS website. I am trying
> > to solve a location issue. The issue is -- we receive some items (e.g. 10
> > pallets of paper having 40 cases each). Which then goes into 10 areas of the
> > warehouse (which I have set up as tables -- Warehouse, Section, Bin, and
> > shelf). Then as requests are made for the items, they might need to be moved
> > to another location as we use them (or just moved to more organize the space
> > available). The manager occasionally wants a "current location" report to
> > print - so if we are looking for something, we can print the report and know
> > its (final) location and quantity. I have been using the Inventory
> > Transactions table to keep track of what comes in and what goes out - but not
> > sure how to handle the "internal" moves - from one location to another. And
> > how to report the 'final' location of something.
> >