Installation directories

I have noticed that the directory path to the "executables" for reporting
services is different on different computers.
on one computer it is
C:\program files\Microsoft SQL Server\MSSQL.3\Reporting
Services\ReportServer\bin
and on another it is
C:\program files\Microsoft SQL Server\MSSQL.2\Reporting
Services\ReportServer\bin
So. one is under "MSSQL.2" and the other is under "MSSQL.3"
Why would this be the case?
I want to setup a vbscript to deploy my own assemblies and I need to copy
them to the appropriate location
How do I determine the location where they should be copied to?
Thanks
BobOn Mar 27, 6:21 pm, "Bob" <some...@.microsoft.com> wrote:
> I have noticed that the directory path to the "executables" for reporting
> services is different on different computers.
> on one computer it is
> C:\program files\Microsoft SQL Server\MSSQL.3\Reporting
> Services\ReportServer\bin
> and on another it is
> C:\program files\Microsoft SQL Server\MSSQL.2\Reporting
> Services\ReportServer\bin
> So. one is under "MSSQL.2" and the other is under "MSSQL.3"
> Why would this be the case?
> I want to setup a vbscript to deploy my own assemblies and I need to copy
> them to the appropriate location
> How do I determine the location where they should be copied to?
> Thanks
> Bob
Don't quote me on this; but, I believe it's based on how many SQL
Server services you install on your system. So if you install Analysis
Services, etc your MSSQL folder might be a different one for SSRS,
etc.
Regards,
Enrique Martinez
Sr. Software Consultant|||"EMartinez" <emartinez.pr1@.gmail.com> wrote in message
news:1175049750.874707.272910@.n76g2000hsh.googlegroups.com...
> On Mar 27, 6:21 pm, "Bob" <some...@.microsoft.com> wrote:
>> I have noticed that the directory path to the "executables" for reporting
>> services is different on different computers.
>> on one computer it is
>> C:\program files\Microsoft SQL Server\MSSQL.3\Reporting
>> Services\ReportServer\bin
>> and on another it is
>> C:\program files\Microsoft SQL Server\MSSQL.2\Reporting
>> Services\ReportServer\bin
>> So. one is under "MSSQL.2" and the other is under "MSSQL.3"
>> Why would this be the case?
>> I want to setup a vbscript to deploy my own assemblies and I need to copy
>> them to the appropriate location
>> How do I determine the location where they should be copied to?
>> Thanks
>> Bob
>
> Don't quote me on this; but, I believe it's based on how many SQL
> Server services you install on your system. So if you install Analysis
> Services, etc your MSSQL folder might be a different one for SSRS,
> etc.
> Regards,
> Enrique Martinez
> Sr. Software Consultant
>
Thanks Enrique,
I sort of guessed that. This particualr server had the SQL database
instaled on it, and then several weeks later I installed Reporting Services.
If I now install OLAP services I suspect that I will get the ".3" directory.
If all services had been installed at one time then the direcories would be
.1 = SQL databse
.2 = OLAP
.3 = Reporting Services
but instead I have
.1 = SQL Database
.2 = reporting Services
.3 = would be OLAP
My question really is "how do I detect (using a script) which directory
contains Reporting Services" ?
Cheers|||On Mar 27, 10:17 pm, "Bob" <some...@.microsoft.com> wrote:
> "EMartinez" <emartinez...@.gmail.com> wrote in message
> news:1175049750.874707.272910@.n76g2000hsh.googlegroups.com...
>
> > On Mar 27, 6:21 pm, "Bob" <some...@.microsoft.com> wrote:
> >> I have noticed that the directory path to the "executables" for reporting
> >> services is different on different computers.
> >> on one computer it is
> >> C:\program files\Microsoft SQL Server\MSSQL.3\Reporting
> >> Services\ReportServer\bin
> >> and on another it is
> >> C:\program files\Microsoft SQL Server\MSSQL.2\Reporting
> >> Services\ReportServer\bin
> >> So. one is under "MSSQL.2" and the other is under "MSSQL.3"
> >> Why would this be the case?
> >> I want to setup a vbscript to deploy my own assemblies and I need to copy
> >> them to the appropriate location
> >> How do I determine the location where they should be copied to?
> >> Thanks
> >> Bob
> > Don't quote me on this; but, I believe it's based on how many SQL
> > Server services you install on your system. So if you install Analysis
> > Services, etc your MSSQL folder might be a different one for SSRS,
> > etc.
> > Regards,
> > Enrique Martinez
> > Sr. Software Consultant
> Thanks Enrique,
> I sort of guessed that. This particualr server had the SQL database
> instaled on it, and then several weeks later I installed Reporting Services.
> If I now install OLAP services I suspect that I will get the ".3" directory.
> If all services had been installed at one time then the direcories would be
> .1 = SQL databse
> .2 = OLAP
> .3 = Reporting Services
> but instead I have
> .1 = SQL Database
> .2 = reporting Services
> .3 = would be OLAP
> My question really is "how do I detect (using a script) which directory
> contains Reporting Services" ?
> Cheers
You might want to loop through the folders at the dos command (via
OSQL or xp_cmdshell) and try to find a folder like ReportingServices.
Hope this helps.
Regards,
Enrique Martinez
Sr. Software Consultant|||"EMartinez" <emartinez.pr1@.gmail.com> wrote in message
news:1175054192.210026.261520@.p15g2000hsd.googlegroups.com...
> On Mar 27, 10:17 pm, "Bob" <some...@.microsoft.com> wrote:
>> "EMartinez" <emartinez...@.gmail.com> wrote in message
>> news:1175049750.874707.272910@.n76g2000hsh.googlegroups.com...
>>
>> > On Mar 27, 6:21 pm, "Bob" <some...@.microsoft.com> wrote:
>> >> I have noticed that the directory path to the "executables" for
>> >> reporting
>> >> services is different on different computers.
>> >> on one computer it is
>> >> C:\program files\Microsoft SQL Server\MSSQL.3\Reporting
>> >> Services\ReportServer\bin
>> >> and on another it is
>> >> C:\program files\Microsoft SQL Server\MSSQL.2\Reporting
>> >> Services\ReportServer\bin
>> >> So. one is under "MSSQL.2" and the other is under "MSSQL.3"
>> >> Why would this be the case?
>> >> I want to setup a vbscript to deploy my own assemblies and I need to
>> >> copy
>> >> them to the appropriate location
>> >> How do I determine the location where they should be copied to?
>> >> Thanks
>> >> Bob
>> > Don't quote me on this; but, I believe it's based on how many SQL
>> > Server services you install on your system. So if you install Analysis
>> > Services, etc your MSSQL folder might be a different one for SSRS,
>> > etc.
>> > Regards,
>> > Enrique Martinez
>> > Sr. Software Consultant
>> Thanks Enrique,
>> I sort of guessed that. This particualr server had the SQL database
>> instaled on it, and then several weeks later I installed Reporting
>> Services.
>> If I now install OLAP services I suspect that I will get the ".3"
>> directory.
>> If all services had been installed at one time then the direcories would
>> be
>> .1 = SQL databse
>> .2 = OLAP
>> .3 = Reporting Services
>> but instead I have
>> .1 = SQL Database
>> .2 = reporting Services
>> .3 = would be OLAP
>> My question really is "how do I detect (using a script) which directory
>> contains Reporting Services" ?
>> Cheers
> You might want to loop through the folders at the dos command (via
> OSQL or xp_cmdshell) and try to find a folder like ReportingServices.
> Hope this helps.
> Regards,
> Enrique Martinez
> Sr. Software Consultant
>
Enrique,
I have written a vbs file to do just this, but then I got to thinking "How
does SSRS know where to find its binaries and how does the Service Pack
process know where to update them?"
Cheers
Bob

Installation - Only help file installs, No virtual directories or

Hi,
I am trying to install Reporting Services on Windows 2003 server (with no
service pack). Initially it says Visual Studio is not present which is fine,
i press next, then it goes into installation and there are no prompts for rs
components, sql database creation etc. once installation is finished, only
thing i can see is the reporting services help file in the menu. there are no
virtual directories.
Please help.
thanks
dhariwalWeird. I have two installations on 2003. Do you have IIS running. In 2003
you need to configure it to have asp.net applications supported. 2003 comes
much more locked down. You are correct that you can just ignore VS not being
present.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"K M Dhariwal" <KMDhariwal@.discussions.microsoft.com> wrote in message
news:E9F35571-D726-4F77-BE62-50BA9A363175@.microsoft.com...
> Hi,
> I am trying to install Reporting Services on Windows 2003 server (with no
> service pack). Initially it says Visual Studio is not present which is
> fine,
> i press next, then it goes into installation and there are no prompts for
> rs
> components, sql database creation etc. once installation is finished, only
> thing i can see is the reporting services help file in the menu. there are
> no
> virtual directories.
> Please help.
> thanks
> dhariwal|||Hi,
I also have Reporting Services running on 2003 at other customers and it
works like a charm. This is the first time i am stuck like this with RS. IIS
is up and running as well as asp.net, i have got front page extension
installed as well (do u think extensions are the culprit), one thing i
noticed is that there is default website as well as Microsoft Sharepoint
Administration. Do you think sharepoint is throwing this thing down.
If i re-install IIS, will it make any difference.
thanks
khalid
"Bruce L-C [MVP]" wrote:
> Weird. I have two installations on 2003. Do you have IIS running. In 2003
> you need to configure it to have asp.net applications supported. 2003 comes
> much more locked down. You are correct that you can just ignore VS not being
> present.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "K M Dhariwal" <KMDhariwal@.discussions.microsoft.com> wrote in message
> news:E9F35571-D726-4F77-BE62-50BA9A363175@.microsoft.com...
> > Hi,
> > I am trying to install Reporting Services on Windows 2003 server (with no
> > service pack). Initially it says Visual Studio is not present which is
> > fine,
> > i press next, then it goes into installation and there are no prompts for
> > rs
> > components, sql database creation etc. once installation is finished, only
> > thing i can see is the reporting services help file in the menu. there are
> > no
> > virtual directories.
> > Please help.
> > thanks
> > dhariwal
>
>|||I don't know. Seems like you should have gotten an error message. Sorry, no
brainstorms on what it might be.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"K M Dhariwal" <KMDhariwal@.discussions.microsoft.com> wrote in message
news:8D4C9377-EE84-4535-90D2-88BAA4809964@.microsoft.com...
> Hi,
> I also have Reporting Services running on 2003 at other customers and it
> works like a charm. This is the first time i am stuck like this with RS.
> IIS
> is up and running as well as asp.net, i have got front page extension
> installed as well (do u think extensions are the culprit), one thing i
> noticed is that there is default website as well as Microsoft Sharepoint
> Administration. Do you think sharepoint is throwing this thing down.
> If i re-install IIS, will it make any difference.
> thanks
> khalid
> "Bruce L-C [MVP]" wrote:
>> Weird. I have two installations on 2003. Do you have IIS running. In 2003
>> you need to configure it to have asp.net applications supported. 2003
>> comes
>> much more locked down. You are correct that you can just ignore VS not
>> being
>> present.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "K M Dhariwal" <KMDhariwal@.discussions.microsoft.com> wrote in message
>> news:E9F35571-D726-4F77-BE62-50BA9A363175@.microsoft.com...
>> > Hi,
>> > I am trying to install Reporting Services on Windows 2003 server (with
>> > no
>> > service pack). Initially it says Visual Studio is not present which is
>> > fine,
>> > i press next, then it goes into installation and there are no prompts
>> > for
>> > rs
>> > components, sql database creation etc. once installation is finished,
>> > only
>> > thing i can see is the reporting services help file in the menu. there
>> > are
>> > no
>> > virtual directories.
>> > Please help.
>> > thanks
>> > dhariwal
>>

Instalation SQL Server

In an instalation of sql server appears an error message saying sql server
can't work with directories with more than 39 characters. The operative
system is W2000 Server.
Thank you."Alberto" <alberto@.nospam.com> wrote in message
news:eAJRbaYxDHA.2136@.TK2MSFTNGP10.phx.gbl...
> In an instalation of sql server appears an error message saying sql server
> can't work with directories with more than 39 characters. The operative
> system is W2000 Server.
Does it install with a shorter folder name? You may have found a limitation,
I've never created a folder that long...
Steve|||If I try to change the directory of instalation, the system is locked.
Thanks.
"Steve Thompson" <SteveThompson@.nomail.please> escribió en el mensaje
news:O5ppb9YxDHA.2456@.TK2MSFTNGP12.phx.gbl...
> "Alberto" <alberto@.nospam.com> wrote in message
> news:eAJRbaYxDHA.2136@.TK2MSFTNGP10.phx.gbl...
> > In an instalation of sql server appears an error message saying sql
server
> > can't work with directories with more than 39 characters. The operative
> > system is W2000 Server.
> Does it install with a shorter folder name? You may have found a
limitation,
> I've never created a folder that long...
> Steve
>|||Are you installing with an account that has proper permissions (local
administrator)?
And, that you cannot change the installed folder if you choose the 'Custom'
install path?
Steve
"Alberto" <alberto@.nospam.com> wrote in message
news:u3BFb2gxDHA.1740@.TK2MSFTNGP12.phx.gbl...
> If I try to change the directory of instalation, the system is locked.
> Thanks.
> "Steve Thompson" <SteveThompson@.nomail.please> escribió en el mensaje
> news:O5ppb9YxDHA.2456@.TK2MSFTNGP12.phx.gbl...
> > "Alberto" <alberto@.nospam.com> wrote in message
> > news:eAJRbaYxDHA.2136@.TK2MSFTNGP10.phx.gbl...
> > > In an instalation of sql server appears an error message saying sql
> server
> > > can't work with directories with more than 39 characters. The
operative
> > > system is W2000 Server.
> >
> > Does it install with a shorter folder name? You may have found a
> limitation,
> > I've never created a folder that long...
> >
> > Steve
> >
> >
>