Have you tried using localhost in your url?

And that is relative, why?;-)

Pravasis S (9/30/2011)

---

May be. But the question is, how do we solve this!!

The only option I can think of is to reinstall sqlserver and then try again.

If you guys...

I would hope that MS gets that fixed soon!!

As magoo has said, there are better methods for this type of query than a recursive cte.

GilaMonster (9/29/2011)

---

SQLRNNR (9/29/2011)

---

Grant Fritchey (9/29/2011)

---

Evil Kraig F (9/29/2011)

---

GilaMonster (9/29/2011)

---

Wooooooooot!!!!!!!!!!!!!!!!!!

2 years, many, many weekends, late nights and a mad rush to the end (and I'm not even counting the ones Jonathan...

Grant Fritchey (9/29/2011)

---

Evil Kraig F (9/29/2011)

---

GilaMonster (9/29/2011)

---

Wooooooooot!!!!!!!!!!!!!!!!!!

2 years, many, many weekends, late nights and a mad rush to the end (and I'm not even counting the ones Jonathan did), it's...

@SQLFRNDZ (9/29/2011)

---

sql_novice_2007 (9/29/2011)

---

It shows 150 MB free space out of 3.1 GB. Can I create any free space on it?

In fact I ran into space issue. Thats why I wanted...

3 GB is a tiny database. Defrag and update stats.

This really seems like a permissions escalation issue with Vista.

There is nothing else that comes to mind that could be relevant from the SSRS side.

Correct

Your browser is throwing an error for 1 of 2 reasons - memory leak or the query takes too long.

By fixing your datasets to eliminate parameter sniffing you are helping...

Rather than a new window - try it from a new tab - to eliminate permissions escalation issue.

There could be a memory leak being revealed when executing this report.

Other things you could try involve fixing the queries for the datasets to prevent parameter sniffing. Also, try...

My 2 bits - I like to use the method that Jack showed.