linking or installing reports into 05 repoting servier

I'm upgrading from SQL 2000 to SQL 05, cannot figure how to add/link reports
in SQL 05 reporting services. The process in not the same as in SQL 2000.
Mike2005 works like 2000.
can you explain what do you try to do? or what you found different.
"Mike" <Mike@.discussions.microsoft.com> wrote in message
news:02A5E05A-6B57-4CDA-9DBD-8814388601F1@.microsoft.com...
> I'm upgrading from SQL 2000 to SQL 05, cannot figure how to add/link
> reports
> in SQL 05 reporting services. The process in not the same as in SQL 2000.
> Mike|||Hi Jeie, well for starters in 2000 I went to the web interface and installed
the reporting scripts. When I instaklled the reporting services for 2000 it
created a web link on the desktop I would click on the link to connect,
pretty staright forward from there.
I guess basically I've not found the interface to install the scripts.
"Jeje" wrote:
> 2005 works like 2000.
> can you explain what do you try to do? or what you found different.
> "Mike" <Mike@.discussions.microsoft.com> wrote in message
> news:02A5E05A-6B57-4CDA-9DBD-8814388601F1@.microsoft.com...
> > I'm upgrading from SQL 2000 to SQL 05, cannot figure how to add/link
> > reports
> > in SQL 05 reporting services. The process in not the same as in SQL 2000.
> >
> > Mike
>|||well, there is no link created anywhere.
you have to add it in your favorites by yourself.
by default the URL is:
http://server/reports
does it what you need?
"Mike" <Mike@.discussions.microsoft.com> wrote in message
news:147C2D38-E8EC-4697-B053-217B7FA97DBD@.microsoft.com...
> Hi Jeie, well for starters in 2000 I went to the web interface and
> installed
> the reporting scripts. When I instaklled the reporting services for 2000
> it
> created a web link on the desktop I would click on the link to connect,
> pretty staright forward from there.
> I guess basically I've not found the interface to install the scripts.
> "Jeje" wrote:
>> 2005 works like 2000.
>> can you explain what do you try to do? or what you found different.
>> "Mike" <Mike@.discussions.microsoft.com> wrote in message
>> news:02A5E05A-6B57-4CDA-9DBD-8814388601F1@.microsoft.com...
>> > I'm upgrading from SQL 2000 to SQL 05, cannot figure how to add/link
>> > reports
>> > in SQL 05 reporting services. The process in not the same as in SQL
>> > 2000.
>> >
>> > Mike
>>

servers

After upgrading a SQL Server 2000 SP3 server from Windows 2000 to Windows
2003 we get this message when trying to use a linked server...
Could not create an instance of OLE DB provider 'SQLOLEDB'.
OLE DB error trace [Non-interface error: CoCreate of DSO for SQLOLEDB
returned 0x8007007f].
Any thoughts?
Questar,
See these threads:
http://groups.google.com/groups?q=jczypinski+oledb32r
http://groups.google.com/groups?q=ko...b32.dll+solved
A wrong version of oledb32.dll might be the issue.
Steve Kass
Drew University
Questar wrote:

>After upgrading a SQL Server 2000 SP3 server from Windows 2000 to Windows
>2003 we get this message when trying to use a linked server...
>Could not create an instance of OLE DB provider 'SQLOLEDB'.
>OLE DB error trace [Non-interface error: CoCreate of DSO for SQLOLEDB
>returned 0x8007007f].
>Any thoughts?
>
>
|||Good call. Problem solved. Thank you!
"Steve Kass" wrote:

> Questar,
> See these threads:
> http://groups.google.com/groups?q=jczypinski+oledb32r
> http://groups.google.com/groups?q=ko...b32.dll+solved
> A wrong version of oledb32.dll might be the issue.
> Steve Kass
> Drew University
> Questar wrote:
>

servers

After upgrading a SQL Server 2000 SP3 server from Windows 2000 to Windows
2003 we get this message when trying to use a linked server...
Could not create an instance of OLE DB provider 'SQLOLEDB'.
OLE DB error trace [Non-interface error: CoCreate of DSO for SQLOLEDB
returned 0x8007007f].
Any thoughts?Questar,
See these threads:
http://groups.google.com/groups?q=jczypinski+oledb32r
http://groups.google.com/groups?q=kotuby+oledb32.dll+solved
A wrong version of oledb32.dll might be the issue.
Steve Kass
Drew University
Questar wrote:
>After upgrading a SQL Server 2000 SP3 server from Windows 2000 to Windows
>2003 we get this message when trying to use a linked server...
>Could not create an instance of OLE DB provider 'SQLOLEDB'.
>OLE DB error trace [Non-interface error: CoCreate of DSO for SQLOLEDB
>returned 0x8007007f].
>Any thoughts?
>
>|||Good call. Problem solved. Thank you!
"Steve Kass" wrote:
> Questar,
> See these threads:
> http://groups.google.com/groups?q=jczypinski+oledb32r
> http://groups.google.com/groups?q=kotuby+oledb32.dll+solved
> A wrong version of oledb32.dll might be the issue.
> Steve Kass
> Drew University
> Questar wrote:
> >After upgrading a SQL Server 2000 SP3 server from Windows 2000 to Windows
> >2003 we get this message when trying to use a linked server...
> >
> >Could not create an instance of OLE DB provider 'SQLOLEDB'.
> >OLE DB error trace [Non-interface error: CoCreate of DSO for SQLOLEDB
> >returned 0x8007007f].
> >
> >Any thoughts?
> >
> >
> >
>

servers

After upgrading a SQL Server 2000 SP3 server from Windows 2000 to Windows
2003 we get this message when trying to use a linked server...
Could not create an instance of OLE DB provider 'SQLOLEDB'.
OLE DB error trace [Non-interface error: CoCreate of DSO for SQLOLEDB
returned 0x8007007f].
Any thoughts?Questar,
See these threads:
http://groups.google.com/groups?q=jczypinski+oledb32r
http://groups.google.com/groups?q=k...db32.dll+solved
A wrong version of oledb32.dll might be the issue.
Steve Kass
Drew University
Questar wrote:

>After upgrading a SQL Server 2000 SP3 server from Windows 2000 to Windows
>2003 we get this message when trying to use a linked server...
>Could not create an instance of OLE DB provider 'SQLOLEDB'.
>OLE DB error trace [Non-interface error: CoCreate of DSO for SQLOLEDB
>returned 0x8007007f].
>Any thoughts?
>
>|||Good call. Problem solved. Thank you!
"Steve Kass" wrote:

> Questar,
> See these threads:
> http://groups.google.com/groups?q=jczypinski+oledb32r
> http://groups.google.com/groups?q=k...db32.dll+solved
> A wrong version of oledb32.dll might be the issue.
> Steve Kass
> Drew University
> Questar wrote:
>
>