Classification has been delayed because the routing information...

Any ideas on why I get this message in the transmission status:

Classification has been delayed because the routing information is currently being updated.

I did create/drop some routes because I had pointed them to the wrong service, but that was some time ago.

I also just tried to restart the sql instance and it hung on stopping so I'm assuming something with the routing caused the issue.

Any ideas?

Thanks.

This error is cause by lock timeouts on reading the routing table (sys.routes) in the database where you're sending from and/or lock timeouts in the tempdb (where information about all SSB services in the SQL instance is stored). If you're hitting this, it means there must be some transaction holding a long lock on a route or on tempdb.

I would recommend using sys.dm_tran_locks, sys.syslockinfo or sp_lock to identify the lock that is blocking the SSB router from classifying messages.

|||

Thanks. I figured it out later on that I had inadventantly started a transaction to send a message and didn't commit it and after that I changed some of the routes so this held everything up.

Thanks.

Classification crosstab query - 2000

Hello --

I think this is the term for what I want (something that could be generated
in ACCESS using a pivot table, or, maybe Yukon).

We have data for sales by sales people in sales regions. More than one
person sells in a region.

We want to display data as follows:

salesperson's names
---- ---- ---- ---- ----
- ----
region 1
region 2 row/column values are sales amounts for person in
that region
region 3

We will add a WHERE clause for the period of time covered.

I don't want to have to change the query if a new salesperson or new region
is added.

Can this be done in SQL Server 2000, Analysis Services, OLAP, anywhere?

Can someone direct me to examples of how to do this?

Thanks for any direction.

Larry MehlHi

This previous post should help:
http://tinyurl.com/6rhsj

John

"L Mehl" <mehl_nospam@.cyvest.com> wrote in message
news:96uyd.7239$9j5.4696@.newsread3.news.pas.earthl ink.net...
> Hello --
> I think this is the term for what I want (something that could be
> generated
> in ACCESS using a pivot table, or, maybe Yukon).
> We have data for sales by sales people in sales regions. More than one
> person sells in a region.
> We want to display data as follows:
> salesperson's names
> ---- ---- ---- ---- ----
> - ----
> region 1
> region 2 row/column values are sales amounts for person
> in
> that region
> region 3
> We will add a WHERE clause for the period of time covered.
> I don't want to have to change the query if a new salesperson or new
> region
> is added.
> Can this be done in SQL Server 2000, Analysis Services, OLAP, anywhere?
> Can someone direct me to examples of how to do this?
> Thanks for any direction.
> Larry Mehl|||John --

Thanks for pointing me to this article.

It worked right out of the box.

Larry

"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:41cace16$0$15616$afc38c87@.news.easynet.co.uk. ..
> Hi
> This previous post should help:
> http://tinyurl.com/6rhsj
> John
> "L Mehl" <mehl_nospam@.cyvest.com> wrote in message
> news:96uyd.7239$9j5.4696@.newsread3.news.pas.earthl ink.net...
> > Hello --
> > I think this is the term for what I want (something that could be
> > generated
> > in ACCESS using a pivot table, or, maybe Yukon).
> > We have data for sales by sales people in sales regions. More than one
> > person sells in a region.
> > We want to display data as follows:
> > salesperson's names
> ---- ---- ---- ---- ---
-
> > - ----
> > region 1
> > region 2 row/column values are sales amounts for person
> > in
> > that region
> > region 3
> > We will add a WHERE clause for the period of time covered.
> > I don't want to have to change the query if a new salesperson or new
> > region
> > is added.
> > Can this be done in SQL Server 2000, Analysis Services, OLAP, anywhere?
> > Can someone direct me to examples of how to do this?
> > Thanks for any direction.
> > Larry Mehlsqlsql