Cannot connect to the Report Mgr.

Hi All,
I'm experiencing the error referenced in the following link to MS
Support
http://support.microsoft.com/Default.aspx?kbid=922656
I implemented the workaround but I'm still getting the error. Actually
when I started I was receiving "error message 1" and then when I
updated my RSWebApplication.config file to use the fully qualified URL
using the IP Address that is assigned to the Default Web Site's "IP
Address" property.
My config file now looks like this...
<ReportServerUrl>http://10.0.0.102:80/Reports</ReportServerUrl>
<ReportServerVirtualDirectory></ReportServerVirtualDirectory>
The server is a Windows 2003 server and the Reporting Services was
installed with SQL2005 but not configured. I was able to configure the
Reports server (from what I can tell) using the "Reporting Services
Configuration" tool).
Any idea as to what may still be causing the problem?
Thanks in advance for any help you can offer.
Mike Gorgone
Senior Software Engineer
PictureU PromotionsOn Aug 21, 2:06 pm, Mike <m_gorg...@.hotmail.com> wrote:
> Hi All,
> I'm experiencing the error referenced in the following link to MS
> Support
> http://support.microsoft.com/Default.aspx?kbid=922656
> I implemented the workaround but I'm still getting the error. Actually
> when I started I was receiving "error message 1" and then when I
> updated my RSWebApplication.config file to use the fully qualified URL
> using the IP Address that is assigned to the Default Web Site's "IP
> Address" property.
> My config file now looks like this...
> <ReportServerUrl>http://10.0.0.102:80/Reports</ReportServerUrl>
> <ReportServerVirtualDirectory></ReportServerVirtualDirectory>
> The server is a Windows 2003 server and the Reporting Services was
> installed with SQL2005 but not configured. I was able to configure the
> Reports server (from what I can tell) using the "Reporting Services
> Configuration" tool).
> Any idea as to what may still be causing the problem?
> Thanks in advance for any help you can offer.
> Mike Gorgone
> Senior Software Engineer
> PictureU Promotions
The last response in this link might be helpful.
http://www.sqlreportingservices.net/Ask/1730.aspx
Regards,
Enrique Martinez
Sr. Software Consultant|||On Aug 21, 9:55 pm, EMartinez <emartinez...@.gmail.com> wrote:
> On Aug 21, 2:06 pm, Mike <m_gorg...@.hotmail.com> wrote:
>
> > Hi All,
> > I'm experiencing the error referenced in the following link to MS
> > Support
> >http://support.microsoft.com/Default.aspx?kbid=922656
> > I implemented the workaround but I'm still getting the error. Actually
> > when I started I was receiving "error message 1" and then when I
> > updated my RSWebApplication.config file to use the fully qualified URL
> > using the IP Address that is assigned to the Default Web Site's "IP
> > Address" property.
> > My config file now looks like this...
> > <ReportServerUrl>http://10.0.0.102:80/Reports</ReportServerUrl>
> > <ReportServerVirtualDirectory></ReportServerVirtualDirectory>
> > The server is a Windows 2003 server and the Reporting Services was
> > installed with SQL2005 but not configured. I was able to configure the
> > Reports server (from what I can tell) using the "Reporting Services
> > Configuration" tool).
> > Any idea as to what may still be causing the problem?
> > Thanks in advance for any help you can offer.
> > Mike Gorgone
> > Senior Software Engineer
> > PictureU Promotions
> The last response in this link might be helpful.http://www.sqlreportingservices.net/Ask/1730.aspx
> Regards,
> Enrique Martinez
> Sr. Software Consultant
Hi Enrique,
Thanks for the link. I've seen some information along those same lines
but I can't set the IP Address property to "All Addresses" the IP
needs to be set to the specific address we have in there.
Is there any war around that?
Mike

cannot connect to sql server 2005 from xp client when trying to create ODBC dsn

Newbie here,

I am trying to link tables from an access 2003 frontend to sql server 2005 backend.

I am doing this in a vmware test environment. I am using vmware server and running sbs 2003 and xp sp2 client. Both virtaul machine can talk to each other(using local host connection).

I have tried to create a dsn to the sql server but i cannot connect. I can ping the sbs server through the command interface but the error i get when i try to connect is :

Connection failed:
Sql state: hyt00
sqlserver error: 0
microsoft odbc sql server driver timeout expired.

spent a day trying various combinations - still no joy.

Any help would be much appreciatedvirtual machines are nothing but trouble. open a query window and execute SELECT @.@.SERVERNAME|||Thank you for your reply,

I would agree vmware is not the best scenario - but as i am new to sql server - and i am about to upsize an access mdb backend to sql server 2005 so I thought some sort of test environment was required. I didn't fancy multiple installs on our production sbs until i got it right.

So from your post - is it possible to create a linked table between access 2003 and sql server 2005 from an access 2003 query window? If so, what would the syntax be if the sbs server was called 'sbs1' and the database on the sql server's default instance was named 'db1'? Or was your code to simply test the connectivity of the sql server?

The ultimate goal is a distributed access mde residing on xp sp2 clients created from an access mdb stored on a restricted network share that has linked tables to sql server 2005.

I do not even wish to go down the dsn road - would prefer the dsn-less road if possible - but i cannot proceed much further with that until i learn more about server logins, user id's and application roles etc and how passwords and user id's will be transferred accross network or stored on local machines. Hence I'm starting with dsn's and testing how to link the tables.

Any advice/guidance would be appreciated.|||I was eventually able to connect using named pipes - syntax had eluded me until i got lucky - server name 'sbs1' and pipe name was 'sbs1'.

So thats one hurdle - the next is which dsn settings to use - which server logins to use and which server roles to use.

The ultimate goal is a distributed access mde residing on xp sp2 clients created from an access mdb stored on a restricted network share that has linked tables to sql server 2005. Approx 4 users will have the abilty to link and import tables from sql server - all other users will be using an mde.

Any advice?