Ok,
We have setup SQL2005 reporting services with MOSS integration. I have
created a datasource that points at our Project server 2003 SQL
database so that we can start to create project server reports. The
data source works just fine BUT its *doesnt* pick up any relationships
between tables from the Project2k3 SQL database.
This means that when you create a report builder report the first
table you selct becomes the primary and no others are visable :( not
very useful for creating meaningful reports.
Questions:
a) How does SQL2005RS read the relationships between table entities in
a remote DB so that they can be used together within the report
builder?
b) Does anyone have recommendations, URLs, How-tos on setting up
reporting services against Project server 2003?
Tips welcome
Al BlakeI have written many reports against the Project Server 2003 database. I have
found there are not relationships in the Project Server database. You always
have to create your own joins of the data.
Most of the time I will create a query using query analyzer, Then use SRS
to group ,filter and sum the data.
Hope this helps
--
Ray McCoppin
http://www.randsmanagement.com
Project Server reports.
"scubaal" wrote:
> Ok,
> We have setup SQL2005 reporting services with MOSS integration. I have
> created a datasource that points at our Project server 2003 SQL
> database so that we can start to create project server reports. The
> data source works just fine BUT its *doesnt* pick up any relationships
> between tables from the Project2k3 SQL database.
> This means that when you create a report builder report the first
> table you selct becomes the primary and no others are visable :( not
> very useful for creating meaningful reports.
> Questions:
> a) How does SQL2005RS read the relationships between table entities in
> a remote DB so that they can be used together within the report
> builder?
> b) Does anyone have recommendations, URLs, How-tos on setting up
> reporting services against Project server 2003?
> Tips welcome
> Al Blake
>|||Thanks for the feedback. I thought that was the case but wanted be
sure I hadnt missed something.
I am quite comfortable in making the queries through SQL QA until I
get the right result but then I am unclear as to how I get this into
the SQL2005RS environment through MOSS.
Are you saying I should define views within the SQL database and then
use report builder to make a report against that?
OR
is there some way to 'parameterise' the Report Model object when you
create it to use a SQL queiry with join as the basis of its model?
As far as I can see when I create a RB model the ONLY option I have is
the datasource I want to use......there doesnt seem to be any way to
create an RBM from a datasourse using
SELECT * FROM A,B WHERE A.ID=B.ID
or am I missing something again?
Regards
Showing posts with label reporting. Show all posts
Showing posts with label reporting. Show all posts
Friday, March 30, 2012
Monday, March 26, 2012
Relating Two DataSets
Hello,
I'm kind of new to reporting services and have gone thru a number of web
casts but no where did I come across this.
Say I have two datasets from two different database on servers.
I know a report can have multiple datasets but is there a way I can
associate the datasets.
For example - I have a dataset 'Master' (database -DB1 on Server S1)which
has a few columns and I have 'Child' (database DB2 on S2).
Master and Child have a common column Col1.
I want to use the Matrix or even List and be able to drill down to child
based on Master Col1 (also this will display other details)
Is there a way to relate Master and Child based on Col1 in the Report or
should this be done in the backed only'The way to do master-child relationships is with sub reports. I do this all
the time. A subreport can be with it's own table in your report or it can be
embedded in a list or a field of a table.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Rashmi Jagadish" <RashmiJagadish@.discussions.microsoft.com> wrote in
message news:B5DE61A3-5A45-4810-B21A-4EB811C2C3EA@.microsoft.com...
> Hello,
> I'm kind of new to reporting services and have gone thru a number of web
> casts but no where did I come across this.
> Say I have two datasets from two different database on servers.
> I know a report can have multiple datasets but is there a way I can
> associate the datasets.
> For example - I have a dataset 'Master' (database -DB1 on Server S1)which
> has a few columns and I have 'Child' (database DB2 on S2).
> Master and Child have a common column Col1.
> I want to use the Matrix or even List and be able to drill down to child
> based on Master Col1 (also this will display other details)
> Is there a way to relate Master and Child based on Col1 in the Report or
> should this be done in the backed only'
>|||What you're describing is one of the common uses of subreports. If you'd
rather not use subreports, then you'd have to do the join on the back-end,
as you suggested.
Mike G.
"Rashmi Jagadish" <RashmiJagadish@.discussions.microsoft.com> wrote in
message news:B5DE61A3-5A45-4810-B21A-4EB811C2C3EA@.microsoft.com...
> Hello,
> I'm kind of new to reporting services and have gone thru a number of web
> casts but no where did I come across this.
> Say I have two datasets from two different database on servers.
> I know a report can have multiple datasets but is there a way I can
> associate the datasets.
> For example - I have a dataset 'Master' (database -DB1 on Server S1)which
> has a few columns and I have 'Child' (database DB2 on S2).
> Master and Child have a common column Col1.
> I want to use the Matrix or even List and be able to drill down to child
> based on Master Col1 (also this will display other details)
> Is there a way to relate Master and Child based on Col1 in the Report or
> should this be done in the backed only'
>|||Thank you both - any tutorial you can point me to?
"Mike G." wrote:
> What you're describing is one of the common uses of subreports. If you'd
> rather not use subreports, then you'd have to do the join on the back-end,
> as you suggested.
> Mike G.
>
> "Rashmi Jagadish" <RashmiJagadish@.discussions.microsoft.com> wrote in
> message news:B5DE61A3-5A45-4810-B21A-4EB811C2C3EA@.microsoft.com...
> > Hello,
> > I'm kind of new to reporting services and have gone thru a number of web
> > casts but no where did I come across this.
> >
> > Say I have two datasets from two different database on servers.
> > I know a report can have multiple datasets but is there a way I can
> > associate the datasets.
> > For example - I have a dataset 'Master' (database -DB1 on Server S1)which
> > has a few columns and I have 'Child' (database DB2 on S2).
> >
> > Master and Child have a common column Col1.
> > I want to use the Matrix or even List and be able to drill down to child
> > based on Master Col1 (also this will display other details)
> >
> > Is there a way to relate Master and Child based on Col1 in the Report or
> > should this be done in the backed only'
> >
> >
>
>|||BOL is usually a good place to start:
http://msdn2.microsoft.com/en-us/library/ms159837.aspx
Mike G.
"Rashmi Jagadish" <RashmiJagadish@.discussions.microsoft.com> wrote in
message news:F3483B62-1669-438D-AEF9-C8025F450507@.microsoft.com...
> Thank you both - any tutorial you can point me to?
> "Mike G." wrote:
>> What you're describing is one of the common uses of subreports. If you'd
>> rather not use subreports, then you'd have to do the join on the
>> back-end,
>> as you suggested.
>> Mike G.
>>
>> "Rashmi Jagadish" <RashmiJagadish@.discussions.microsoft.com> wrote in
>> message news:B5DE61A3-5A45-4810-B21A-4EB811C2C3EA@.microsoft.com...
>> > Hello,
>> > I'm kind of new to reporting services and have gone thru a number of
>> > web
>> > casts but no where did I come across this.
>> >
>> > Say I have two datasets from two different database on servers.
>> > I know a report can have multiple datasets but is there a way I can
>> > associate the datasets.
>> > For example - I have a dataset 'Master' (database -DB1 on Server
>> > S1)which
>> > has a few columns and I have 'Child' (database DB2 on S2).
>> >
>> > Master and Child have a common column Col1.
>> > I want to use the Matrix or even List and be able to drill down to
>> > child
>> > based on Master Col1 (also this will display other details)
>> >
>> > Is there a way to relate Master and Child based on Col1 in the Report
>> > or
>> > should this be done in the backed only'
>> >
>> >
>>|||Bruce,
I've seen you mention sub-reports several times as a solution to displaying
content from different data sources, or parent/child records. I wonder,
however, if you've ever found a different approach for a related situation.
A field in dataset1 may contain any of 6 status codes, and a table in
dataset2 has the status codes and an accompanying text description. Most of
the data we want to display is over in dataset1, but we'd like to display the
text for the code from dataset2. So while a Switch() would work if this
situation were limited to one field in one case, we find that all of the
customized preferences for this "off-the-shelf" system are stored in
dataset2. We'd like to find a way to regularly refer to the code/descripton
lists. SQL stored procedures are only a last resort for us. dataset1 comes
from IBM DB2 and dataset2 comes from an Access MDB.
Your thoughts are appreciated.
"Bruce L-C [MVP]" wrote:
> The way to do master-child relationships is with sub reports. I do this all
> the time. A subreport can be with it's own table in your report or it can be
> embedded in a list or a field of a table.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
>|||Sub reports work for this. I use it this way. Create a report (to be used as
a subreport) that has a query parameter with a matching report parameter for
status code. Have a single field returned. Shorten all parts of the report
to show only the field. Remove the header line, no footer etc. Indeed, if
you are sure that only a single record is returned your report could have a
single text field, base it on an expression, the expression is set to the
field of the dataset and uses the First aggregate (which is this case is the
first and only).
Now, add a empty cell to the table control. Drop the subreport into the
cell. Right mouse click and set the parameter mapping.
Another option is to do a drill through. For the field with the status code
set it to blue and underlined, then right mouse click, properties,
navigation and set it to do a jump to report and jump to a report that
specifies what the code means.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Corvallis" <Corvallis@.discussions.microsoft.com> wrote in message
news:2209BB1C-E288-4B57-8723-7EE90DD81540@.microsoft.com...
> Bruce,
> I've seen you mention sub-reports several times as a solution to
> displaying
> content from different data sources, or parent/child records. I wonder,
> however, if you've ever found a different approach for a related
> situation.
> A field in dataset1 may contain any of 6 status codes, and a table in
> dataset2 has the status codes and an accompanying text description. Most
> of
> the data we want to display is over in dataset1, but we'd like to display
> the
> text for the code from dataset2. So while a Switch() would work if this
> situation were limited to one field in one case, we find that all of the
> customized preferences for this "off-the-shelf" system are stored in
> dataset2. We'd like to find a way to regularly refer to the
> code/descripton
> lists. SQL stored procedures are only a last resort for us. dataset1
> comes
> from IBM DB2 and dataset2 comes from an Access MDB.
> Your thoughts are appreciated.
> "Bruce L-C [MVP]" wrote:
>> The way to do master-child relationships is with sub reports. I do this
>> all
>> the time. A subreport can be with it's own table in your report or it can
>> be
>> embedded in a list or a field of a table.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
I'm kind of new to reporting services and have gone thru a number of web
casts but no where did I come across this.
Say I have two datasets from two different database on servers.
I know a report can have multiple datasets but is there a way I can
associate the datasets.
For example - I have a dataset 'Master' (database -DB1 on Server S1)which
has a few columns and I have 'Child' (database DB2 on S2).
Master and Child have a common column Col1.
I want to use the Matrix or even List and be able to drill down to child
based on Master Col1 (also this will display other details)
Is there a way to relate Master and Child based on Col1 in the Report or
should this be done in the backed only'The way to do master-child relationships is with sub reports. I do this all
the time. A subreport can be with it's own table in your report or it can be
embedded in a list or a field of a table.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Rashmi Jagadish" <RashmiJagadish@.discussions.microsoft.com> wrote in
message news:B5DE61A3-5A45-4810-B21A-4EB811C2C3EA@.microsoft.com...
> Hello,
> I'm kind of new to reporting services and have gone thru a number of web
> casts but no where did I come across this.
> Say I have two datasets from two different database on servers.
> I know a report can have multiple datasets but is there a way I can
> associate the datasets.
> For example - I have a dataset 'Master' (database -DB1 on Server S1)which
> has a few columns and I have 'Child' (database DB2 on S2).
> Master and Child have a common column Col1.
> I want to use the Matrix or even List and be able to drill down to child
> based on Master Col1 (also this will display other details)
> Is there a way to relate Master and Child based on Col1 in the Report or
> should this be done in the backed only'
>|||What you're describing is one of the common uses of subreports. If you'd
rather not use subreports, then you'd have to do the join on the back-end,
as you suggested.
Mike G.
"Rashmi Jagadish" <RashmiJagadish@.discussions.microsoft.com> wrote in
message news:B5DE61A3-5A45-4810-B21A-4EB811C2C3EA@.microsoft.com...
> Hello,
> I'm kind of new to reporting services and have gone thru a number of web
> casts but no where did I come across this.
> Say I have two datasets from two different database on servers.
> I know a report can have multiple datasets but is there a way I can
> associate the datasets.
> For example - I have a dataset 'Master' (database -DB1 on Server S1)which
> has a few columns and I have 'Child' (database DB2 on S2).
> Master and Child have a common column Col1.
> I want to use the Matrix or even List and be able to drill down to child
> based on Master Col1 (also this will display other details)
> Is there a way to relate Master and Child based on Col1 in the Report or
> should this be done in the backed only'
>|||Thank you both - any tutorial you can point me to?
"Mike G." wrote:
> What you're describing is one of the common uses of subreports. If you'd
> rather not use subreports, then you'd have to do the join on the back-end,
> as you suggested.
> Mike G.
>
> "Rashmi Jagadish" <RashmiJagadish@.discussions.microsoft.com> wrote in
> message news:B5DE61A3-5A45-4810-B21A-4EB811C2C3EA@.microsoft.com...
> > Hello,
> > I'm kind of new to reporting services and have gone thru a number of web
> > casts but no where did I come across this.
> >
> > Say I have two datasets from two different database on servers.
> > I know a report can have multiple datasets but is there a way I can
> > associate the datasets.
> > For example - I have a dataset 'Master' (database -DB1 on Server S1)which
> > has a few columns and I have 'Child' (database DB2 on S2).
> >
> > Master and Child have a common column Col1.
> > I want to use the Matrix or even List and be able to drill down to child
> > based on Master Col1 (also this will display other details)
> >
> > Is there a way to relate Master and Child based on Col1 in the Report or
> > should this be done in the backed only'
> >
> >
>
>|||BOL is usually a good place to start:
http://msdn2.microsoft.com/en-us/library/ms159837.aspx
Mike G.
"Rashmi Jagadish" <RashmiJagadish@.discussions.microsoft.com> wrote in
message news:F3483B62-1669-438D-AEF9-C8025F450507@.microsoft.com...
> Thank you both - any tutorial you can point me to?
> "Mike G." wrote:
>> What you're describing is one of the common uses of subreports. If you'd
>> rather not use subreports, then you'd have to do the join on the
>> back-end,
>> as you suggested.
>> Mike G.
>>
>> "Rashmi Jagadish" <RashmiJagadish@.discussions.microsoft.com> wrote in
>> message news:B5DE61A3-5A45-4810-B21A-4EB811C2C3EA@.microsoft.com...
>> > Hello,
>> > I'm kind of new to reporting services and have gone thru a number of
>> > web
>> > casts but no where did I come across this.
>> >
>> > Say I have two datasets from two different database on servers.
>> > I know a report can have multiple datasets but is there a way I can
>> > associate the datasets.
>> > For example - I have a dataset 'Master' (database -DB1 on Server
>> > S1)which
>> > has a few columns and I have 'Child' (database DB2 on S2).
>> >
>> > Master and Child have a common column Col1.
>> > I want to use the Matrix or even List and be able to drill down to
>> > child
>> > based on Master Col1 (also this will display other details)
>> >
>> > Is there a way to relate Master and Child based on Col1 in the Report
>> > or
>> > should this be done in the backed only'
>> >
>> >
>>|||Bruce,
I've seen you mention sub-reports several times as a solution to displaying
content from different data sources, or parent/child records. I wonder,
however, if you've ever found a different approach for a related situation.
A field in dataset1 may contain any of 6 status codes, and a table in
dataset2 has the status codes and an accompanying text description. Most of
the data we want to display is over in dataset1, but we'd like to display the
text for the code from dataset2. So while a Switch() would work if this
situation were limited to one field in one case, we find that all of the
customized preferences for this "off-the-shelf" system are stored in
dataset2. We'd like to find a way to regularly refer to the code/descripton
lists. SQL stored procedures are only a last resort for us. dataset1 comes
from IBM DB2 and dataset2 comes from an Access MDB.
Your thoughts are appreciated.
"Bruce L-C [MVP]" wrote:
> The way to do master-child relationships is with sub reports. I do this all
> the time. A subreport can be with it's own table in your report or it can be
> embedded in a list or a field of a table.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
>|||Sub reports work for this. I use it this way. Create a report (to be used as
a subreport) that has a query parameter with a matching report parameter for
status code. Have a single field returned. Shorten all parts of the report
to show only the field. Remove the header line, no footer etc. Indeed, if
you are sure that only a single record is returned your report could have a
single text field, base it on an expression, the expression is set to the
field of the dataset and uses the First aggregate (which is this case is the
first and only).
Now, add a empty cell to the table control. Drop the subreport into the
cell. Right mouse click and set the parameter mapping.
Another option is to do a drill through. For the field with the status code
set it to blue and underlined, then right mouse click, properties,
navigation and set it to do a jump to report and jump to a report that
specifies what the code means.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Corvallis" <Corvallis@.discussions.microsoft.com> wrote in message
news:2209BB1C-E288-4B57-8723-7EE90DD81540@.microsoft.com...
> Bruce,
> I've seen you mention sub-reports several times as a solution to
> displaying
> content from different data sources, or parent/child records. I wonder,
> however, if you've ever found a different approach for a related
> situation.
> A field in dataset1 may contain any of 6 status codes, and a table in
> dataset2 has the status codes and an accompanying text description. Most
> of
> the data we want to display is over in dataset1, but we'd like to display
> the
> text for the code from dataset2. So while a Switch() would work if this
> situation were limited to one field in one case, we find that all of the
> customized preferences for this "off-the-shelf" system are stored in
> dataset2. We'd like to find a way to regularly refer to the
> code/descripton
> lists. SQL stored procedures are only a last resort for us. dataset1
> comes
> from IBM DB2 and dataset2 comes from an Access MDB.
> Your thoughts are appreciated.
> "Bruce L-C [MVP]" wrote:
>> The way to do master-child relationships is with sub reports. I do this
>> all
>> the time. A subreport can be with it's own table in your report or it can
>> be
>> embedded in a list or a field of a table.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
Friday, March 23, 2012
Reinstalling Sql Reporting Services
Hi, I uninstalled Sql reporting services through Add/Remove Programs, now i'm trying to install it back but SQL Setup not allowing me to do this as all the checkboxes to select components to install are disabled. I'v tried both running via Add/Remove programs and directly running SQL setup exe. can u guys direct me to something?
regards
faraz
What SKU are you installing? Express with Advanced Services? Something else?
Thanks,
Sam Lester (MSFT)
reinstalling reporting services
so i uninstalled reporting services and rebooted
now when i run setup it doesnt even ask me for any options to fill out, it just runs for a minute and says done, but it doesn't really install anything (IIS sites, DB, etc...)
i deleted the DBs, the IIS sites, and the files left over. i did everything except delete stuff in the registry
what do i have to do to get it to reinstall from scratch?
i tried using the .ini file and using the command line utility with no luckwelcome to the hell that Reporting Services 2000. read chapter 7 of this...
http://www.awprofessional.com/articles/article.asp?p=357694&seqNum=1&rl=1
and then read the whole thing.
SQL 2005 reporting Services is a lot more agreeable.|||so i uninstalled reporting services and rebooted
now when i run setup it doesnt even ask me for any options to fill out, it just runs for a minute and says done, but it doesn't really install anything (IIS sites, DB, etc...)
i deleted the DBs, the IIS sites, and the files left over. i did everything except delete stuff in the registry
what do i have to do to get it to reinstall from scratch?
i tried using the .ini file and using the command line utility with no luck
Check your Sql server Service pack as well as Windows server service pack.It happened to me also.Reboot and Install it again...|||Check your Sql server Service pack as well as Windows server service pack.It happened to me also.Reboot and Install it again...
using all of the latest service packs, and i rebooted twice with the same results :o|||welcome to the hell that Reporting Services 2000. read chapter 7 of this...
http://www.awprofessional.com/articles/article.asp?p=357694&seqNum=1&rl=1
and then read the whole thing.
SQL 2005 reporting Services is a lot more agreeable.
i did read this chapter, and looked over the whole thing
i also read the entire sql reporting services book from the people at www.sqlreportingservices.net
none of their solutions helped
i think i am going to try an unattended installation to try to force it to use my ini file, after that i'm out of ideas|||Some info for your help...
Renaming a computer causes a corresponding name change for the Web server and SQL Server instance (if it is on the same computer).
In some cases, Reporting Services is not functional after a computer name change. If you are running a Windows 2000 server and the ReportServer Windows service runs as Local System, the ReportServer Windows service no longer starts automatically when you restart the computer. If you are running Windows Server 2003, the service will start, but you cannot connect to the report server database. To restore service after a computer name change, follow these steps:
Run rsconfig at the command line to update the encrypted connection information in the report server database. Use this syntax when running rsconfig (your values may be different).
rsconfig -s<NewServerName> -dreportserver -aSQL -uSA -p<SAPassword>
Reset IIS. To do this at the command line, type iisreset.
In the RSWebApplication.config file, modify the ReportServerURL setting to reflect the new server name.
In the RSReportServer.config file, modify the URLRoot setting to reflect the new server name.
Update the URL property of the program item used to access Report Manager from the Start menu. To do this, point to Start, point to Program Files, point to Microsoft SQL Server, point to Reporting Services, right-click on Report Manager. On the Web Document page, update the URL to the new server name.
Open Report Manager and update any shared data sources or report-specific data sources that contain references to the old computer name.
If you are running Windows 2000 server, perform these additional steps:
Manually start the ReportServer Windows service.
Run rsactivate at the command line. Use this syntax when running rsactivate (note that your actual values may be different if you did not install to the default path).
rsactivate -c"%installdir%\Reporting
Services\ReportServer\RSReportServer.config"
Reset IIS. To do this at the command line, type iisreset.
For a period of time, the report server and Report Manager may continue to be available under the previous name if you are using Windows Internet Naming Service (WINS) on your corporate network. WINS maps an IP address to each computer it services. Once WINS refreshes the IP address for the renamed computer, the old computer name can no longer be used to access a report server or Report Manager.|||i did this as well, the problem is that RSCONFIG does not support Named Instances as per Microsoft's website. plus the config files are envrypted - i dont think you can see server names listed in the config files, i remember checking before i did anything
it has to be reinstalled through the GUI which does support named instances
i solved the problem to my issue once again:
asp.net 2.0 was installed on this machine as well, which caused the registry key RootVer to be set to ASP 2.0. This is why the install package was saying that 1.1 was not installed (even though it was). YOu have to temporarily change the RootVer key to 1.1, install, and then set it back. This allows you to reinstall report server etc...
[\\HKLM\SOFTWARE\Microsoft\ASP.NET\RootVer] = "1.1.4322.573"
now when i run setup it doesnt even ask me for any options to fill out, it just runs for a minute and says done, but it doesn't really install anything (IIS sites, DB, etc...)
i deleted the DBs, the IIS sites, and the files left over. i did everything except delete stuff in the registry
what do i have to do to get it to reinstall from scratch?
i tried using the .ini file and using the command line utility with no luckwelcome to the hell that Reporting Services 2000. read chapter 7 of this...
http://www.awprofessional.com/articles/article.asp?p=357694&seqNum=1&rl=1
and then read the whole thing.
SQL 2005 reporting Services is a lot more agreeable.|||so i uninstalled reporting services and rebooted
now when i run setup it doesnt even ask me for any options to fill out, it just runs for a minute and says done, but it doesn't really install anything (IIS sites, DB, etc...)
i deleted the DBs, the IIS sites, and the files left over. i did everything except delete stuff in the registry
what do i have to do to get it to reinstall from scratch?
i tried using the .ini file and using the command line utility with no luck
Check your Sql server Service pack as well as Windows server service pack.It happened to me also.Reboot and Install it again...|||Check your Sql server Service pack as well as Windows server service pack.It happened to me also.Reboot and Install it again...
using all of the latest service packs, and i rebooted twice with the same results :o|||welcome to the hell that Reporting Services 2000. read chapter 7 of this...
http://www.awprofessional.com/articles/article.asp?p=357694&seqNum=1&rl=1
and then read the whole thing.
SQL 2005 reporting Services is a lot more agreeable.
i did read this chapter, and looked over the whole thing
i also read the entire sql reporting services book from the people at www.sqlreportingservices.net
none of their solutions helped
i think i am going to try an unattended installation to try to force it to use my ini file, after that i'm out of ideas|||Some info for your help...
Renaming a computer causes a corresponding name change for the Web server and SQL Server instance (if it is on the same computer).
In some cases, Reporting Services is not functional after a computer name change. If you are running a Windows 2000 server and the ReportServer Windows service runs as Local System, the ReportServer Windows service no longer starts automatically when you restart the computer. If you are running Windows Server 2003, the service will start, but you cannot connect to the report server database. To restore service after a computer name change, follow these steps:
Run rsconfig at the command line to update the encrypted connection information in the report server database. Use this syntax when running rsconfig (your values may be different).
rsconfig -s<NewServerName> -dreportserver -aSQL -uSA -p<SAPassword>
Reset IIS. To do this at the command line, type iisreset.
In the RSWebApplication.config file, modify the ReportServerURL setting to reflect the new server name.
In the RSReportServer.config file, modify the URLRoot setting to reflect the new server name.
Update the URL property of the program item used to access Report Manager from the Start menu. To do this, point to Start, point to Program Files, point to Microsoft SQL Server, point to Reporting Services, right-click on Report Manager. On the Web Document page, update the URL to the new server name.
Open Report Manager and update any shared data sources or report-specific data sources that contain references to the old computer name.
If you are running Windows 2000 server, perform these additional steps:
Manually start the ReportServer Windows service.
Run rsactivate at the command line. Use this syntax when running rsactivate (note that your actual values may be different if you did not install to the default path).
rsactivate -c"%installdir%\Reporting
Services\ReportServer\RSReportServer.config"
Reset IIS. To do this at the command line, type iisreset.
For a period of time, the report server and Report Manager may continue to be available under the previous name if you are using Windows Internet Naming Service (WINS) on your corporate network. WINS maps an IP address to each computer it services. Once WINS refreshes the IP address for the renamed computer, the old computer name can no longer be used to access a report server or Report Manager.|||i did this as well, the problem is that RSCONFIG does not support Named Instances as per Microsoft's website. plus the config files are envrypted - i dont think you can see server names listed in the config files, i remember checking before i did anything
it has to be reinstalled through the GUI which does support named instances
i solved the problem to my issue once again:
asp.net 2.0 was installed on this machine as well, which caused the registry key RootVer to be set to ASP 2.0. This is why the install package was saying that 1.1 was not installed (even though it was). YOu have to temporarily change the RootVer key to 1.1, install, and then set it back. This allows you to reinstall report server etc...
[\\HKLM\SOFTWARE\Microsoft\ASP.NET\RootVer] = "1.1.4322.573"
Wednesday, March 21, 2012
ReInstalling Katmai.
I cannot reinstall Katmai.
Somehow, I created a situation where Management Studio could not connect to reporting services. Being unable to diagnose why, I decided to uninstall and reinstall. I had installed everything. After running about 10 uninstalls, I went to C:/Program Files/ and blasted the whole Microsoft SQL Server tree. I went to the registry and did the same thing in HKLM/Software/Microsoft/Microsoft SQL Server.
I rebooted. The error message: An instance with the same name is already installed on this computer. I'm guessing the setup program detected MSSQLSERVER in some registry key, and not another instance, but if I knew which one, I wouldn't be posting to this forum.
Somehow, I created a situation where Management Studio could not connect to reporting services. Being unable to diagnose why, I decided to uninstall and reinstall. I had installed everything. After running about 10 uninstalls, I went to C:/Program Files/ and blasted the whole Microsoft SQL Server tree. I went to the registry and did the same thing in HKLM/Software/Microsoft/Microsoft SQL Server.
I rebooted. The error message: An instance with the same name is already installed on this computer. I'm guessing the setup program detected MSSQLSERVER in some registry key, and not another instance, but if I knew which one, I wouldn't be posting to this forum.
It may be that Control Panel|Administrative Tools|Services has an SQL Server(InstanceName) entry.
sql
Reinstall RS Client?
Hi,
I have purchased a new copy of SQL Server for running Reporting Service as
the Evaluation copy has expired.
I have installed Visual Studio with RS client on a workstation as I don't
want to install Report Designer on the Server.
I would like to know is it necessary for me to uninstall the Evaluation Copy
RS Client on my workstation before installing the new RS Client ?
Your advice is sought.I am pretty sure the evaluation expiration is only the server part of RS,
not the design tools. Are you getting a message saying that it has expired
when you try to design? You should still be able to design and preview. If
that is the case (I am trying to remember what I did but I don't think I did
anything with the client tools). Unless you have a problem my suggestion is
to leave the designer alone. After installing the new server you should
download SP2 and install that at both the server and the client.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Peter" <Peter@.discussions.microsoft.com> wrote in message
news:%239RZUnfsFHA.3424@.TK2MSFTNGP14.phx.gbl...
> Hi,
> I have purchased a new copy of SQL Server for running Reporting Service as
> the Evaluation copy has expired.
> I have installed Visual Studio with RS client on a workstation as I don't
> want to install Report Designer on the Server.
> I would like to know is it necessary for me to uninstall the Evaluation
> Copy RS Client on my workstation before installing the new RS Client ?
> Your advice is sought.
>
I have purchased a new copy of SQL Server for running Reporting Service as
the Evaluation copy has expired.
I have installed Visual Studio with RS client on a workstation as I don't
want to install Report Designer on the Server.
I would like to know is it necessary for me to uninstall the Evaluation Copy
RS Client on my workstation before installing the new RS Client ?
Your advice is sought.I am pretty sure the evaluation expiration is only the server part of RS,
not the design tools. Are you getting a message saying that it has expired
when you try to design? You should still be able to design and preview. If
that is the case (I am trying to remember what I did but I don't think I did
anything with the client tools). Unless you have a problem my suggestion is
to leave the designer alone. After installing the new server you should
download SP2 and install that at both the server and the client.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Peter" <Peter@.discussions.microsoft.com> wrote in message
news:%239RZUnfsFHA.3424@.TK2MSFTNGP14.phx.gbl...
> Hi,
> I have purchased a new copy of SQL Server for running Reporting Service as
> the Evaluation copy has expired.
> I have installed Visual Studio with RS client on a workstation as I don't
> want to install Report Designer on the Server.
> I would like to know is it necessary for me to uninstall the Evaluation
> Copy RS Client on my workstation before installing the new RS Client ?
> Your advice is sought.
>
Re-install Reporting Services
Hi,
I had to re-install IIS for an unrelated development issue.
As a result, I now need to re-register reporting services (and its webs
etc) in IIS.
I can't seem to do this through simply "Add/Remove" because I get the
error:
"The setup failed to read IIsMimeMap table. The error code is
-2147024893"
Does anyone have any ideas on how to proceed?
Many thanks for your feedback!
LuvicThis has been reported as a bug.
http://lab.msdn.microsoft.com/productfeedback/viewfeedback.aspx?feedbackid=735b5260-f6bf-4ea5-94b2-6c41ae387a9a
There are a few posted workarounds. Google for your error message - you have
several to choose from.
Good luck.
<luvic.vangool@.gmail.com> wrote in message
news:1148053449.781220.187920@.y43g2000cwc.googlegroups.com...
> Hi,
> I had to re-install IIS for an unrelated development issue.
> As a result, I now need to re-register reporting services (and its webs
> etc) in IIS.
> I can't seem to do this through simply "Add/Remove" because I get the
> error:
> "The setup failed to read IIsMimeMap table. The error code is
> -2147024893"
> Does anyone have any ideas on how to proceed?
> Many thanks for your feedback!
> Luvic
>sql
I had to re-install IIS for an unrelated development issue.
As a result, I now need to re-register reporting services (and its webs
etc) in IIS.
I can't seem to do this through simply "Add/Remove" because I get the
error:
"The setup failed to read IIsMimeMap table. The error code is
-2147024893"
Does anyone have any ideas on how to proceed?
Many thanks for your feedback!
LuvicThis has been reported as a bug.
http://lab.msdn.microsoft.com/productfeedback/viewfeedback.aspx?feedbackid=735b5260-f6bf-4ea5-94b2-6c41ae387a9a
There are a few posted workarounds. Google for your error message - you have
several to choose from.
Good luck.
<luvic.vangool@.gmail.com> wrote in message
news:1148053449.781220.187920@.y43g2000cwc.googlegroups.com...
> Hi,
> I had to re-install IIS for an unrelated development issue.
> As a result, I now need to re-register reporting services (and its webs
> etc) in IIS.
> I can't seem to do this through simply "Add/Remove" because I get the
> error:
> "The setup failed to read IIsMimeMap table. The error code is
> -2147024893"
> Does anyone have any ideas on how to proceed?
> Many thanks for your feedback!
> Luvic
>sql
Reinstall Reporting Services
Does anyone know of a way to completely reinstall reporting services?
I tried to do it through the SQL Server 2005 install and at somepoint
it told me the only way to modify/reinstall an existing installation
for this component was to do it through Control Panel > Add/Remove
Programs. I tried that, it ran through it's setup, but didn't really
reinstall anything or give me any installation config options. I've
messed up my reporting services pretty good and would like to
completely uninstall then reinstall if possible.
Thanks,
MattMark
Before uninstalling RS you should remove 2 RS components manually. Follow this
Launch Component Service MMC snap-in from Administrative Tools.
Navigate down to Components Services | Computers | <My Computer>| COM+
Applications, you fill find at least a pair of IIS application for RS &
Reports. You have to remove them, in order to do so you will ned to select
each applications properties dialog and Uncheck Diable deletion on the
Protection tab. This will delete them.
Thanks
Azhar
"Matt Karp" wrote:
> Does anyone know of a way to completely reinstall reporting services?
> I tried to do it through the SQL Server 2005 install and at somepoint
> it told me the only way to modify/reinstall an existing installation
> for this component was to do it through Control Panel > Add/Remove
> Programs. I tried that, it ran through it's setup, but didn't really
> reinstall anything or give me any installation config options. I've
> messed up my reporting services pretty good and would like to
> completely uninstall then reinstall if possible.
> Thanks,
> Matt
>
I tried to do it through the SQL Server 2005 install and at somepoint
it told me the only way to modify/reinstall an existing installation
for this component was to do it through Control Panel > Add/Remove
Programs. I tried that, it ran through it's setup, but didn't really
reinstall anything or give me any installation config options. I've
messed up my reporting services pretty good and would like to
completely uninstall then reinstall if possible.
Thanks,
MattMark
Before uninstalling RS you should remove 2 RS components manually. Follow this
Launch Component Service MMC snap-in from Administrative Tools.
Navigate down to Components Services | Computers | <My Computer>| COM+
Applications, you fill find at least a pair of IIS application for RS &
Reports. You have to remove them, in order to do so you will ned to select
each applications properties dialog and Uncheck Diable deletion on the
Protection tab. This will delete them.
Thanks
Azhar
"Matt Karp" wrote:
> Does anyone know of a way to completely reinstall reporting services?
> I tried to do it through the SQL Server 2005 install and at somepoint
> it told me the only way to modify/reinstall an existing installation
> for this component was to do it through Control Panel > Add/Remove
> Programs. I tried that, it ran through it's setup, but didn't really
> reinstall anything or give me any installation config options. I've
> messed up my reporting services pretty good and would like to
> completely uninstall then reinstall if possible.
> Thanks,
> Matt
>
Reinstall problem with Report Services
I have been playing with my Standard version of SQL Server with no problems. Now I wanted to start exploring Reporting Services, however whenever I tried to connect to the instance through the Management Studio, it would fail. I did notice that the folder in IIS was not present so I am thinking it was something I failed to do in the initial setup.
I have uninstalled everything, but when it gets to Reporting Services, I get an error message "The setup failed to read IISMiniMap table. Error Code -2147024893." I did a search on various newsgroups and forums and found a message about installing and running some Microsoft Cleanup utility. I did this, but I am still getting the error message and then the uninstall rolls everything back.
What do I need to do here, short of doing a total reformat of the harddrive and just reinstall everything?
Thanks for the information.
To add to this problem, I uninstalled all that I could with my original instance of SQL Server (minus Reporting Services). Now I have reinstalled a new instance that also created a new instance of Reporting Services. However when I go to IIS, it says that the Report Server is stopped and I cannot restart it. I get the error "The request is not supported".
What is up with this?
Friday, March 9, 2012
regular expression
Hi all,
I m able to use regular expression in a Vbs script, but how can I use them
(if it's possible ) in reporting service code ?
I havent found any subjects like this in the my books (even in "MRS in
action" by Téo Lachev :) )
ThanksFirst, add a function to do your Regular expression in the report level
Code (Report --> Properties --> Code) . Here's an example:
----
Public Function RegExTest () as Object
Dim Str As String = "<expressiontext>the text the returned by
the regular expression</expressiontext>"
Dim expressiontext As String
Dim regexexpressiontext As System.Text.RegularExpressions.Regex
= New
System.Text.RegularExpressions.Regex("<expressiontext>(?<expressiontext>[^<]+)</expressiontext>",
System.Text.RegularExpressions.RegexOptions.IgnoreCase)
expressiontext =regexexpressiontext.Match(Str).Groups("expressiontext").Value
RegExTest = expressiontext
End Function
----
Now your text box will refer to the code in a fashion similar to this:
=Code.RegExTest
And low and behold, regular expressions in Reporting Services.
Andy Potter|||OK.
Thanks a lot !
"Potter" wrote:
> First, add a function to do your Regular expression in the report level
> Code (Report --> Properties --> Code) . Here's an example:
> ----
> Public Function RegExTest () as Object
> Dim Str As String = "<expressiontext>the text the returned by
> the regular expression</expressiontext>"
> Dim expressiontext As String
> Dim regexexpressiontext As System.Text.RegularExpressions.Regex
> = New
> System.Text.RegularExpressions.Regex("<expressiontext>(?<expressiontext>[^<]+)</expressiontext>",
> System.Text.RegularExpressions.RegexOptions.IgnoreCase)
> expressiontext => regexexpressiontext.Match(Str).Groups("expressiontext").Value
> RegExTest = expressiontext
> End Function
> ----
> Now your text box will refer to the code in a fashion similar to this:
> =Code.RegExTest
> And low and behold, regular expressions in Reporting Services.
> Andy Potter
>
I m able to use regular expression in a Vbs script, but how can I use them
(if it's possible ) in reporting service code ?
I havent found any subjects like this in the my books (even in "MRS in
action" by Téo Lachev :) )
ThanksFirst, add a function to do your Regular expression in the report level
Code (Report --> Properties --> Code) . Here's an example:
----
Public Function RegExTest () as Object
Dim Str As String = "<expressiontext>the text the returned by
the regular expression</expressiontext>"
Dim expressiontext As String
Dim regexexpressiontext As System.Text.RegularExpressions.Regex
= New
System.Text.RegularExpressions.Regex("<expressiontext>(?<expressiontext>[^<]+)</expressiontext>",
System.Text.RegularExpressions.RegexOptions.IgnoreCase)
expressiontext =regexexpressiontext.Match(Str).Groups("expressiontext").Value
RegExTest = expressiontext
End Function
----
Now your text box will refer to the code in a fashion similar to this:
=Code.RegExTest
And low and behold, regular expressions in Reporting Services.
Andy Potter|||OK.
Thanks a lot !
"Potter" wrote:
> First, add a function to do your Regular expression in the report level
> Code (Report --> Properties --> Code) . Here's an example:
> ----
> Public Function RegExTest () as Object
> Dim Str As String = "<expressiontext>the text the returned by
> the regular expression</expressiontext>"
> Dim expressiontext As String
> Dim regexexpressiontext As System.Text.RegularExpressions.Regex
> = New
> System.Text.RegularExpressions.Regex("<expressiontext>(?<expressiontext>[^<]+)</expressiontext>",
> System.Text.RegularExpressions.RegexOptions.IgnoreCase)
> expressiontext => regexexpressiontext.Match(Str).Groups("expressiontext").Value
> RegExTest = expressiontext
> End Function
> ----
> Now your text box will refer to the code in a fashion similar to this:
> =Code.RegExTest
> And low and behold, regular expressions in Reporting Services.
> Andy Potter
>
Wednesday, March 7, 2012
Registry read in Reporting Services
Hello. I am trying to get the machine name in a Reporting Services 2000
report. I thought I would put this in the registry and read it from a
function in the custom code. Here is my first attempt:
Public Function GetMachineName
On Error Resume Next
Dim WshShell
Set WshShell = WScript.CreateObject("WScript.Shell")
Return WshShell.RegRead("HKLM\Software\Something\MachineName")
End Function
This gives a build error: Let and set are no longer supported. OK, so I take
out the set on line 3. Then it says "WScript" is not declared. I'm pretty
sure this is valid code. I got it from Windows Script Host 2.0 Documentation.
Does Reporting Services support using the WScript functionality? Thanks in
advance.I tried to do the same thing with SRS 2005 and VS 2005 but I get the error
message listed below.
'Read reg key value
my.computer.registry.GetValue(myPath, "RegKeyName", Nothing)
Error: Unhandled exception: Request for permission of type
'System.Security.Permissions.RegistryPermission
To get around this, you can do one of two things:
1. Use "Reg Query" command to read the registry and set a variable to the
the computer name
2. Use an HTA front end which will use VBScript to read the machine name and
then use the /v to pass the machine name variable from either step above.
I have an HTA front end for this very same issue so send me an email if you
want a copy.
Hope this helps!
Rafael
"Justin30519" <Justin30519@.discussions.microsoft.com> wrote in message
news:81784CFA-B08F-4CCE-85F3-C855EE8CFC7D@.microsoft.com...
> Hello. I am trying to get the machine name in a Reporting Services 2000
> report. I thought I would put this in the registry and read it from a
> function in the custom code. Here is my first attempt:
> Public Function GetMachineName
> On Error Resume Next
> Dim WshShell
> Set WshShell = WScript.CreateObject("WScript.Shell")
> Return WshShell.RegRead("HKLM\Software\Something\MachineName")
> End Function
> This gives a build error: Let and set are no longer supported. OK, so I
> take
> out the set on line 3. Then it says "WScript" is not declared. I'm pretty
> sure this is valid code. I got it from Windows Script Host 2.0
> Documentation.
> Does Reporting Services support using the WScript functionality? Thanks in
> advance.
report. I thought I would put this in the registry and read it from a
function in the custom code. Here is my first attempt:
Public Function GetMachineName
On Error Resume Next
Dim WshShell
Set WshShell = WScript.CreateObject("WScript.Shell")
Return WshShell.RegRead("HKLM\Software\Something\MachineName")
End Function
This gives a build error: Let and set are no longer supported. OK, so I take
out the set on line 3. Then it says "WScript" is not declared. I'm pretty
sure this is valid code. I got it from Windows Script Host 2.0 Documentation.
Does Reporting Services support using the WScript functionality? Thanks in
advance.I tried to do the same thing with SRS 2005 and VS 2005 but I get the error
message listed below.
'Read reg key value
my.computer.registry.GetValue(myPath, "RegKeyName", Nothing)
Error: Unhandled exception: Request for permission of type
'System.Security.Permissions.RegistryPermission
To get around this, you can do one of two things:
1. Use "Reg Query" command to read the registry and set a variable to the
the computer name
2. Use an HTA front end which will use VBScript to read the machine name and
then use the /v to pass the machine name variable from either step above.
I have an HTA front end for this very same issue so send me an email if you
want a copy.
Hope this helps!
Rafael
"Justin30519" <Justin30519@.discussions.microsoft.com> wrote in message
news:81784CFA-B08F-4CCE-85F3-C855EE8CFC7D@.microsoft.com...
> Hello. I am trying to get the machine name in a Reporting Services 2000
> report. I thought I would put this in the registry and read it from a
> function in the custom code. Here is my first attempt:
> Public Function GetMachineName
> On Error Resume Next
> Dim WshShell
> Set WshShell = WScript.CreateObject("WScript.Shell")
> Return WshShell.RegRead("HKLM\Software\Something\MachineName")
> End Function
> This gives a build error: Let and set are no longer supported. OK, so I
> take
> out the set on line 3. Then it says "WScript" is not declared. I'm pretty
> sure this is valid code. I got it from Windows Script Host 2.0
> Documentation.
> Does Reporting Services support using the WScript functionality? Thanks in
> advance.
Saturday, February 25, 2012
registering SQL Server not in domain
Hi all,
We have standardized on Hyperion as our reporting tool. So far I have
only set up a couple of Access databases as data sources for it. Now
there is a request to report off our eOn (telephony management) SQL
Server database using Hyperion. The eOn SQL Server box is in a
workgroup that is not part of the rest of our domain. (We only have
one domain because we don't have a "forest", whatever that means.) It
is behind a router owned by eOn along with a PBX and some other stuff.
Setting up a data source for Hyperion requires creating a special data
source file called an .oce on the box where the Hyperion fat client
(required for most administrative tasks) resides, and also setting up a
different special data source file called a .das on the server where
the Hyperion services run. (The analysts and end-users do not have the
fat client, their access is web-based.)
I have to register the eOn SQL Server by using the IP address and SQL
Server authentication. (I was told that I can't use Windows
authentication because it is not in the domain.) From the box on
which the Hyperion fat client resides, I cannot register the eOn SQL
Server. The error message is "timeout expired". Tracerting indicates
there are no intermediate hops when attempting to connect from this
VLAN. From my desktop, which is on a different VLAN, I can connect to
and register it. This trip includes one hop at our 6509. From one of
my servers which is on the same VLAN as the fat-client box, I am able
to connect and register. On the fat-client box I tried deleting and
re-registering another SQL Server and there was no problem.
The IP address I have to use to connect to the eOn SQL Server is *NOT*
the actual IP address of the box it resides on, but rather the eOn
router, which translates it to the address of the server. We have no
control over this, eOn creates this setup. I'm not sure how it knows
which of the devices behind it a given message is for.
Ideas?Hi
Which version of SQL Server is on the telephony management system? At a
guess it is MSDE with no network protocols installed! Use svrnetcn.exe to
enable the network protcols. If they are running you may want to use the
SQLRecon tool to see what servers are available on your network
http://www.sqlsecurity.com/DesktopDefault.aspx?tabid=26
John
"Ellen K" wrote:
> Hi all,
> We have standardized on Hyperion as our reporting tool. So far I have
> only set up a couple of Access databases as data sources for it. Now
> there is a request to report off our eOn (telephony management) SQL
> Server database using Hyperion. The eOn SQL Server box is in a
> workgroup that is not part of the rest of our domain. (We only have
> one domain because we don't have a "forest", whatever that means.) It
> is behind a router owned by eOn along with a PBX and some other stuff.
>
> Setting up a data source for Hyperion requires creating a special data
> source file called an .oce on the box where the Hyperion fat client
> (required for most administrative tasks) resides, and also setting up a
> different special data source file called a .das on the server where
> the Hyperion services run. (The analysts and end-users do not have the
> fat client, their access is web-based.)
> I have to register the eOn SQL Server by using the IP address and SQL
> Server authentication. (I was told that I can't use Windows
> authentication because it is not in the domain.) From the box on
> which the Hyperion fat client resides, I cannot register the eOn SQL
> Server. The error message is "timeout expired". Tracerting indicates
> there are no intermediate hops when attempting to connect from this
> VLAN. From my desktop, which is on a different VLAN, I can connect to
> and register it. This trip includes one hop at our 6509. From one of
> my servers which is on the same VLAN as the fat-client box, I am able
> to connect and register. On the fat-client box I tried deleting and
> re-registering another SQL Server and there was no problem.
> The IP address I have to use to connect to the eOn SQL Server is *NOT*
> the actual IP address of the box it resides on, but rather the eOn
> router, which translates it to the address of the server. We have no
> control over this, eOn creates this setup. I'm not sure how it knows
> which of the devices behind it a given message is for.
> Ideas?
>|||Hi John,
Thanks for your response. I will check the version and also check
which network protocols are enabled on it, assuming I can get to the
box. But if the problem were no network protocols installed on the eOn
box then how would the other two boxes that CAN register it be able to
do so?
Thanks,
Ellen|||Hi
I hadn't realised that it could be registered elsewhere! This indicates that
there are network protocols, but they still may not be the same as the ones
on the client that can't register!! You may still want to try running
SQLRecon and also try to telnet into the port being used.
John
"Ellen K" wrote:
> Hi John,
> Thanks for your response. I will check the version and also check
> which network protocols are enabled on it, assuming I can get to the
> box. But if the problem were no network protocols installed on the eOn
> box then how would the other two boxes that CAN register it be able to
> do so?
> Thanks,
> Ellen
>|||Hi John,
Yes, I mentioned in my original post that I could register it from both
my desktop and from one of "my" servers.
The network protocols are the same on the eOn box as on "my" servers:
named pipes and tcp. Since the fat client can connect to "my" servers,
I think it's safe to say this isn't the problem.
I have now succeeded in creating an ODBC connection, which would not
have been my first choice, but right now if it works I'm happy.
Thanks,
Ellen
We have standardized on Hyperion as our reporting tool. So far I have
only set up a couple of Access databases as data sources for it. Now
there is a request to report off our eOn (telephony management) SQL
Server database using Hyperion. The eOn SQL Server box is in a
workgroup that is not part of the rest of our domain. (We only have
one domain because we don't have a "forest", whatever that means.) It
is behind a router owned by eOn along with a PBX and some other stuff.
Setting up a data source for Hyperion requires creating a special data
source file called an .oce on the box where the Hyperion fat client
(required for most administrative tasks) resides, and also setting up a
different special data source file called a .das on the server where
the Hyperion services run. (The analysts and end-users do not have the
fat client, their access is web-based.)
I have to register the eOn SQL Server by using the IP address and SQL
Server authentication. (I was told that I can't use Windows
authentication because it is not in the domain.) From the box on
which the Hyperion fat client resides, I cannot register the eOn SQL
Server. The error message is "timeout expired". Tracerting indicates
there are no intermediate hops when attempting to connect from this
VLAN. From my desktop, which is on a different VLAN, I can connect to
and register it. This trip includes one hop at our 6509. From one of
my servers which is on the same VLAN as the fat-client box, I am able
to connect and register. On the fat-client box I tried deleting and
re-registering another SQL Server and there was no problem.
The IP address I have to use to connect to the eOn SQL Server is *NOT*
the actual IP address of the box it resides on, but rather the eOn
router, which translates it to the address of the server. We have no
control over this, eOn creates this setup. I'm not sure how it knows
which of the devices behind it a given message is for.
Ideas?Hi
Which version of SQL Server is on the telephony management system? At a
guess it is MSDE with no network protocols installed! Use svrnetcn.exe to
enable the network protcols. If they are running you may want to use the
SQLRecon tool to see what servers are available on your network
http://www.sqlsecurity.com/DesktopDefault.aspx?tabid=26
John
"Ellen K" wrote:
> Hi all,
> We have standardized on Hyperion as our reporting tool. So far I have
> only set up a couple of Access databases as data sources for it. Now
> there is a request to report off our eOn (telephony management) SQL
> Server database using Hyperion. The eOn SQL Server box is in a
> workgroup that is not part of the rest of our domain. (We only have
> one domain because we don't have a "forest", whatever that means.) It
> is behind a router owned by eOn along with a PBX and some other stuff.
>
> Setting up a data source for Hyperion requires creating a special data
> source file called an .oce on the box where the Hyperion fat client
> (required for most administrative tasks) resides, and also setting up a
> different special data source file called a .das on the server where
> the Hyperion services run. (The analysts and end-users do not have the
> fat client, their access is web-based.)
> I have to register the eOn SQL Server by using the IP address and SQL
> Server authentication. (I was told that I can't use Windows
> authentication because it is not in the domain.) From the box on
> which the Hyperion fat client resides, I cannot register the eOn SQL
> Server. The error message is "timeout expired". Tracerting indicates
> there are no intermediate hops when attempting to connect from this
> VLAN. From my desktop, which is on a different VLAN, I can connect to
> and register it. This trip includes one hop at our 6509. From one of
> my servers which is on the same VLAN as the fat-client box, I am able
> to connect and register. On the fat-client box I tried deleting and
> re-registering another SQL Server and there was no problem.
> The IP address I have to use to connect to the eOn SQL Server is *NOT*
> the actual IP address of the box it resides on, but rather the eOn
> router, which translates it to the address of the server. We have no
> control over this, eOn creates this setup. I'm not sure how it knows
> which of the devices behind it a given message is for.
> Ideas?
>|||Hi John,
Thanks for your response. I will check the version and also check
which network protocols are enabled on it, assuming I can get to the
box. But if the problem were no network protocols installed on the eOn
box then how would the other two boxes that CAN register it be able to
do so?
Thanks,
Ellen|||Hi
I hadn't realised that it could be registered elsewhere! This indicates that
there are network protocols, but they still may not be the same as the ones
on the client that can't register!! You may still want to try running
SQLRecon and also try to telnet into the port being used.
John
"Ellen K" wrote:
> Hi John,
> Thanks for your response. I will check the version and also check
> which network protocols are enabled on it, assuming I can get to the
> box. But if the problem were no network protocols installed on the eOn
> box then how would the other two boxes that CAN register it be able to
> do so?
> Thanks,
> Ellen
>|||Hi John,
Yes, I mentioned in my original post that I could register it from both
my desktop and from one of "my" servers.
The network protocols are the same on the eOn box as on "my" servers:
named pipes and tcp. Since the fat client can connect to "my" servers,
I think it's safe to say this isn't the problem.
I have now succeeded in creating an ODBC connection, which would not
have been my first choice, but right now if it works I'm happy.
Thanks,
Ellen
registering SQL Server not in domain
Hi all,
We have standardized on Hyperion as our reporting tool. So far I have
only set up a couple of Access databases as data sources for it. Now
there is a request to report off our eOn (telephony management) SQL
Server database using Hyperion. The eOn SQL Server box is in a
workgroup that is not part of the rest of our domain. (We only have
one domain because we don't have a "forest", whatever that means.) It
is behind a router owned by eOn along with a PBX and some other stuff.
Setting up a data source for Hyperion requires creating a special data
source file called an .oce on the box where the Hyperion fat client
(required for most administrative tasks) resides, and also setting up a
different special data source file called a .das on the server where
the Hyperion services run. (The analysts and end-users do not have the
fat client, their access is web-based.)
I have to register the eOn SQL Server by using the IP address and SQL
Server authentication. (I was told that I can't use Windows
authentication because it is not in the domain.) From the box on
which the Hyperion fat client resides, I cannot register the eOn SQL
Server. The error message is "timeout expired". Tracerting indicates
there are no intermediate hops when attempting to connect from this
VLAN. From my desktop, which is on a different VLAN, I can connect to
and register it. This trip includes one hop at our 6509. From one of
my servers which is on the same VLAN as the fat-client box, I am able
to connect and register. On the fat-client box I tried deleting and
re-registering another SQL Server and there was no problem.
The IP address I have to use to connect to the eOn SQL Server is *NOT*
the actual IP address of the box it resides on, but rather the eOn
router, which translates it to the address of the server. We have no
control over this, eOn creates this setup. I'm not sure how it knows
which of the devices behind it a given message is for.
Ideas?
Hi
Which version of SQL Server is on the telephony management system? At a
guess it is MSDE with no network protocols installed! Use svrnetcn.exe to
enable the network protcols. If they are running you may want to use the
SQLRecon tool to see what servers are available on your network
http://www.sqlsecurity.com/DesktopDefault.aspx?tabid=26
John
"Ellen K" wrote:
> Hi all,
> We have standardized on Hyperion as our reporting tool. So far I have
> only set up a couple of Access databases as data sources for it. Now
> there is a request to report off our eOn (telephony management) SQL
> Server database using Hyperion. The eOn SQL Server box is in a
> workgroup that is not part of the rest of our domain. (We only have
> one domain because we don't have a "forest", whatever that means.) It
> is behind a router owned by eOn along with a PBX and some other stuff.
>
> Setting up a data source for Hyperion requires creating a special data
> source file called an .oce on the box where the Hyperion fat client
> (required for most administrative tasks) resides, and also setting up a
> different special data source file called a .das on the server where
> the Hyperion services run. (The analysts and end-users do not have the
> fat client, their access is web-based.)
> I have to register the eOn SQL Server by using the IP address and SQL
> Server authentication. (I was told that I can't use Windows
> authentication because it is not in the domain.) From the box on
> which the Hyperion fat client resides, I cannot register the eOn SQL
> Server. The error message is "timeout expired". Tracerting indicates
> there are no intermediate hops when attempting to connect from this
> VLAN. From my desktop, which is on a different VLAN, I can connect to
> and register it. This trip includes one hop at our 6509. From one of
> my servers which is on the same VLAN as the fat-client box, I am able
> to connect and register. On the fat-client box I tried deleting and
> re-registering another SQL Server and there was no problem.
> The IP address I have to use to connect to the eOn SQL Server is *NOT*
> the actual IP address of the box it resides on, but rather the eOn
> router, which translates it to the address of the server. We have no
> control over this, eOn creates this setup. I'm not sure how it knows
> which of the devices behind it a given message is for.
> Ideas?
>
|||Hi John,
Thanks for your response. I will check the version and also check
which network protocols are enabled on it, assuming I can get to the
box. But if the problem were no network protocols installed on the eOn
box then how would the other two boxes that CAN register it be able to
do so?
Thanks,
Ellen
|||Hi
I hadn't realised that it could be registered elsewhere! This indicates that
there are network protocols, but they still may not be the same as the ones
on the client that can't register!! You may still want to try running
SQLRecon and also try to telnet into the port being used.
John
"Ellen K" wrote:
> Hi John,
> Thanks for your response. I will check the version and also check
> which network protocols are enabled on it, assuming I can get to the
> box. But if the problem were no network protocols installed on the eOn
> box then how would the other two boxes that CAN register it be able to
> do so?
> Thanks,
> Ellen
>
|||Hi John,
Yes, I mentioned in my original post that I could register it from both
my desktop and from one of "my" servers.
The network protocols are the same on the eOn box as on "my" servers:
named pipes and tcp. Since the fat client can connect to "my" servers,
I think it's safe to say this isn't the problem.
I have now succeeded in creating an ODBC connection, which would not
have been my first choice, but right now if it works I'm happy.
Thanks,
Ellen
We have standardized on Hyperion as our reporting tool. So far I have
only set up a couple of Access databases as data sources for it. Now
there is a request to report off our eOn (telephony management) SQL
Server database using Hyperion. The eOn SQL Server box is in a
workgroup that is not part of the rest of our domain. (We only have
one domain because we don't have a "forest", whatever that means.) It
is behind a router owned by eOn along with a PBX and some other stuff.
Setting up a data source for Hyperion requires creating a special data
source file called an .oce on the box where the Hyperion fat client
(required for most administrative tasks) resides, and also setting up a
different special data source file called a .das on the server where
the Hyperion services run. (The analysts and end-users do not have the
fat client, their access is web-based.)
I have to register the eOn SQL Server by using the IP address and SQL
Server authentication. (I was told that I can't use Windows
authentication because it is not in the domain.) From the box on
which the Hyperion fat client resides, I cannot register the eOn SQL
Server. The error message is "timeout expired". Tracerting indicates
there are no intermediate hops when attempting to connect from this
VLAN. From my desktop, which is on a different VLAN, I can connect to
and register it. This trip includes one hop at our 6509. From one of
my servers which is on the same VLAN as the fat-client box, I am able
to connect and register. On the fat-client box I tried deleting and
re-registering another SQL Server and there was no problem.
The IP address I have to use to connect to the eOn SQL Server is *NOT*
the actual IP address of the box it resides on, but rather the eOn
router, which translates it to the address of the server. We have no
control over this, eOn creates this setup. I'm not sure how it knows
which of the devices behind it a given message is for.
Ideas?
Hi
Which version of SQL Server is on the telephony management system? At a
guess it is MSDE with no network protocols installed! Use svrnetcn.exe to
enable the network protcols. If they are running you may want to use the
SQLRecon tool to see what servers are available on your network
http://www.sqlsecurity.com/DesktopDefault.aspx?tabid=26
John
"Ellen K" wrote:
> Hi all,
> We have standardized on Hyperion as our reporting tool. So far I have
> only set up a couple of Access databases as data sources for it. Now
> there is a request to report off our eOn (telephony management) SQL
> Server database using Hyperion. The eOn SQL Server box is in a
> workgroup that is not part of the rest of our domain. (We only have
> one domain because we don't have a "forest", whatever that means.) It
> is behind a router owned by eOn along with a PBX and some other stuff.
>
> Setting up a data source for Hyperion requires creating a special data
> source file called an .oce on the box where the Hyperion fat client
> (required for most administrative tasks) resides, and also setting up a
> different special data source file called a .das on the server where
> the Hyperion services run. (The analysts and end-users do not have the
> fat client, their access is web-based.)
> I have to register the eOn SQL Server by using the IP address and SQL
> Server authentication. (I was told that I can't use Windows
> authentication because it is not in the domain.) From the box on
> which the Hyperion fat client resides, I cannot register the eOn SQL
> Server. The error message is "timeout expired". Tracerting indicates
> there are no intermediate hops when attempting to connect from this
> VLAN. From my desktop, which is on a different VLAN, I can connect to
> and register it. This trip includes one hop at our 6509. From one of
> my servers which is on the same VLAN as the fat-client box, I am able
> to connect and register. On the fat-client box I tried deleting and
> re-registering another SQL Server and there was no problem.
> The IP address I have to use to connect to the eOn SQL Server is *NOT*
> the actual IP address of the box it resides on, but rather the eOn
> router, which translates it to the address of the server. We have no
> control over this, eOn creates this setup. I'm not sure how it knows
> which of the devices behind it a given message is for.
> Ideas?
>
|||Hi John,
Thanks for your response. I will check the version and also check
which network protocols are enabled on it, assuming I can get to the
box. But if the problem were no network protocols installed on the eOn
box then how would the other two boxes that CAN register it be able to
do so?
Thanks,
Ellen
|||Hi
I hadn't realised that it could be registered elsewhere! This indicates that
there are network protocols, but they still may not be the same as the ones
on the client that can't register!! You may still want to try running
SQLRecon and also try to telnet into the port being used.
John
"Ellen K" wrote:
> Hi John,
> Thanks for your response. I will check the version and also check
> which network protocols are enabled on it, assuming I can get to the
> box. But if the problem were no network protocols installed on the eOn
> box then how would the other two boxes that CAN register it be able to
> do so?
> Thanks,
> Ellen
>
|||Hi John,
Yes, I mentioned in my original post that I could register it from both
my desktop and from one of "my" servers.
The network protocols are the same on the eOn box as on "my" servers:
named pipes and tcp. Since the fat client can connect to "my" servers,
I think it's safe to say this isn't the problem.
I have now succeeded in creating an ODBC connection, which would not
have been my first choice, but right now if it works I'm happy.
Thanks,
Ellen
registering SQL Server not in domain
Hi all,
We have standardized on Hyperion as our reporting tool. So far I have
only set up a couple of Access databases as data sources for it. Now
there is a request to report off our eOn (telephony management) SQL
Server database using Hyperion. The eOn SQL Server box is in a
workgroup that is not part of the rest of our domain. (We only have
one domain because we don't have a "forest", whatever that means.) It
is behind a router owned by eOn along with a PBX and some other stuff.
Setting up a data source for Hyperion requires creating a special data
source file called an .oce on the box where the Hyperion fat client
(required for most administrative tasks) resides, and also setting up a
different special data source file called a .das on the server where
the Hyperion services run. (The analysts and end-users do not have the
fat client, their access is web-based.)
I have to register the eOn SQL Server by using the IP address and SQL
Server authentication. (I was told that I can't use Windows
authentication because it is not in the domain.) From the box on
which the Hyperion fat client resides, I cannot register the eOn SQL
Server. The error message is "timeout expired". Tracerting indicates
there are no intermediate hops when attempting to connect from this
VLAN. From my desktop, which is on a different VLAN, I can connect to
and register it. This trip includes one hop at our 6509. From one of
my servers which is on the same VLAN as the fat-client box, I am able
to connect and register. On the fat-client box I tried deleting and
re-registering another SQL Server and there was no problem.
The IP address I have to use to connect to the eOn SQL Server is *NOT*
the actual IP address of the box it resides on, but rather the eOn
router, which translates it to the address of the server. We have no
control over this, eOn creates this setup. I'm not sure how it knows
which of the devices behind it a given message is for.
Ideas?From your description I pulled this sentence.
"From my desktop, which is on a different VLAN, I can connect to
and register it."
This indicates that you have a valid SQL login, password, protocol, and ip
address. Analyse you desktop and figure out what these are. In particular
the protocol.
The protocol, Network routing, and possibly the firewall will be the issue.
The two most common protocols for SQL is Named Pipes and TCP.
If you can get to the SQL Server from your desktop, look at the SQL Server
Log for what protocols are supported.
From the Hyperion services server use this information to configure an ODBC
DSN and test the connection. You may want to install the SQL client only
option on your Hyperion server to give you more control over the connection
setup (AKA a SQL Alias)
"Ellen K" <ekaye2002@.yahoo.com> wrote in message
news:1129150328.960539.76600@.g47g2000cwa.googlegro ups.com...
> Hi all,
> We have standardized on Hyperion as our reporting tool. So far I have
> only set up a couple of Access databases as data sources for it. Now
> there is a request to report off our eOn (telephony management) SQL
> Server database using Hyperion. The eOn SQL Server box is in a
> workgroup that is not part of the rest of our domain. (We only have
> one domain because we don't have a "forest", whatever that means.) It
> is behind a router owned by eOn along with a PBX and some other stuff.
>
> Setting up a data source for Hyperion requires creating a special data
> source file called an .oce on the box where the Hyperion fat client
> (required for most administrative tasks) resides, and also setting up a
> different special data source file called a .das on the server where
> the Hyperion services run. (The analysts and end-users do not have the
> fat client, their access is web-based.)
> I have to register the eOn SQL Server by using the IP address and SQL
> Server authentication. (I was told that I can't use Windows
> authentication because it is not in the domain.) From the box on
> which the Hyperion fat client resides, I cannot register the eOn SQL
> Server. The error message is "timeout expired". Tracerting indicates
> there are no intermediate hops when attempting to connect from this
> VLAN. From my desktop, which is on a different VLAN, I can connect to
> and register it. This trip includes one hop at our 6509. From one of
> my servers which is on the same VLAN as the fat-client box, I am able
> to connect and register. On the fat-client box I tried deleting and
> re-registering another SQL Server and there was no problem.
> The IP address I have to use to connect to the eOn SQL Server is *NOT*
> the actual IP address of the box it resides on, but rather the eOn
> router, which translates it to the address of the server. We have no
> control over this, eOn creates this setup. I'm not sure how it knows
> which of the devices behind it a given message is for.
> Ideas?|||Hi,
Thanks very much for your response. :)
I think network routing has been eliminated as the cause because I was
able to register the eOn server from one of "my" SQL Servers which is
on the same VLAN as the fat client box that can't register it. And it
can't be a firewall issue because the eOn box is behind our firewall,
it's just not in our domain. I did not think to check the protocols,
that is definitely worth a try. It did occur to me to set up the eOn
database as an ODBC connection for Hyperion instead of using the SQL
Server option, which if it works would solve the current problem.
However, I am also concerned because I am meanwhile building a data
warehouse in SQL Server for which Hyperion is supposed to be the
reporting tool and I would hate to have make a choice that I know up
front is going to diminish performance.
Thanks again, I will report back.
Ellen|||Hi again,
Well, it's not the network protocols.
I did notice that the eOn box is running the original version of SQL
Server, i.e. no service packs have been applied. I will take care of
that, but would be surprised if it's causing the problem.
Meanwhile I did succeed in setting up an ODBC connection, so I've
solved my immediate problem.
Thanks again,
Ellen
registering SQL Server not in domain
Hi all,
We have standardized on Hyperion as our reporting tool. So far I have
only set up a couple of Access databases as data sources for it. Now
there is a request to report off our eOn (telephony management) SQL
Server database using Hyperion. The eOn SQL Server box is in a
workgroup that is not part of the rest of our domain. (We only have
one domain because we don't have a "forest", whatever that means.) It
is behind a router owned by eOn along with a PBX and some other stuff.
Setting up a data source for Hyperion requires creating a special data
source file called an .oce on the box where the Hyperion fat client
(required for most administrative tasks) resides, and also setting up a
different special data source file called a .das on the server where
the Hyperion services run. (The analysts and end-users do not have the
fat client, their access is web-based.)
I have to register the eOn SQL Server by using the IP address and SQL
Server authentication. (I was told that I can't use Windows
authentication because it is not in the domain.) From the box on
which the Hyperion fat client resides, I cannot register the eOn SQL
Server. The error message is "timeout expired". Tracerting indicates
there are no intermediate hops when attempting to connect from this
VLAN. From my desktop, which is on a different VLAN, I can connect to
and register it. This trip includes one hop at our 6509. From one of
my servers which is on the same VLAN as the fat-client box, I am able
to connect and register. On the fat-client box I tried deleting and
re-registering another SQL Server and there was no problem.
The IP address I have to use to connect to the eOn SQL Server is *NOT*
the actual IP address of the box it resides on, but rather the eOn
router, which translates it to the address of the server. We have no
control over this, eOn creates this setup. I'm not sure how it knows
which of the devices behind it a given message is for.
Ideas?Hi
Which version of SQL Server is on the telephony management system? At a
guess it is MSDE with no network protocols installed! Use svrnetcn.exe to
enable the network protcols. If they are running you may want to use the
SQLRecon tool to see what servers are available on your network
http://www.sqlsecurity.com/DesktopDefault.aspx?tabid=26
John
"Ellen K" wrote:
> Hi all,
> We have standardized on Hyperion as our reporting tool. So far I have
> only set up a couple of Access databases as data sources for it. Now
> there is a request to report off our eOn (telephony management) SQL
> Server database using Hyperion. The eOn SQL Server box is in a
> workgroup that is not part of the rest of our domain. (We only have
> one domain because we don't have a "forest", whatever that means.) It
> is behind a router owned by eOn along with a PBX and some other stuff.
>
> Setting up a data source for Hyperion requires creating a special data
> source file called an .oce on the box where the Hyperion fat client
> (required for most administrative tasks) resides, and also setting up a
> different special data source file called a .das on the server where
> the Hyperion services run. (The analysts and end-users do not have the
> fat client, their access is web-based.)
> I have to register the eOn SQL Server by using the IP address and SQL
> Server authentication. (I was told that I can't use Windows
> authentication because it is not in the domain.) From the box on
> which the Hyperion fat client resides, I cannot register the eOn SQL
> Server. The error message is "timeout expired". Tracerting indicates
> there are no intermediate hops when attempting to connect from this
> VLAN. From my desktop, which is on a different VLAN, I can connect to
> and register it. This trip includes one hop at our 6509. From one of
> my servers which is on the same VLAN as the fat-client box, I am able
> to connect and register. On the fat-client box I tried deleting and
> re-registering another SQL Server and there was no problem.
> The IP address I have to use to connect to the eOn SQL Server is *NOT*
> the actual IP address of the box it resides on, but rather the eOn
> router, which translates it to the address of the server. We have no
> control over this, eOn creates this setup. I'm not sure how it knows
> which of the devices behind it a given message is for.
> Ideas?
>|||Hi John,
Thanks for your response. I will check the version and also check
which network protocols are enabled on it, assuming I can get to the
box. But if the problem were no network protocols installed on the eOn
box then how would the other two boxes that CAN register it be able to
do so?
Thanks,
Ellen|||Hi
I hadn't realised that it could be registered elsewhere! This indicates that
there are network protocols, but they still may not be the same as the ones
on the client that can't register!! You may still want to try running
SQLRecon and also try to telnet into the port being used.
John
"Ellen K" wrote:
> Hi John,
> Thanks for your response. I will check the version and also check
> which network protocols are enabled on it, assuming I can get to the
> box. But if the problem were no network protocols installed on the eOn
> box then how would the other two boxes that CAN register it be able to
> do so?
> Thanks,
> Ellen
>|||Hi John,
Yes, I mentioned in my original post that I could register it from both
my desktop and from one of "my" servers.
The network protocols are the same on the eOn box as on "my" servers:
named pipes and tcp. Since the fat client can connect to "my" servers,
I think it's safe to say this isn't the problem.
I have now succeeded in creating an ODBC connection, which would not
have been my first choice, but right now if it works I'm happy.
Thanks,
Ellen
We have standardized on Hyperion as our reporting tool. So far I have
only set up a couple of Access databases as data sources for it. Now
there is a request to report off our eOn (telephony management) SQL
Server database using Hyperion. The eOn SQL Server box is in a
workgroup that is not part of the rest of our domain. (We only have
one domain because we don't have a "forest", whatever that means.) It
is behind a router owned by eOn along with a PBX and some other stuff.
Setting up a data source for Hyperion requires creating a special data
source file called an .oce on the box where the Hyperion fat client
(required for most administrative tasks) resides, and also setting up a
different special data source file called a .das on the server where
the Hyperion services run. (The analysts and end-users do not have the
fat client, their access is web-based.)
I have to register the eOn SQL Server by using the IP address and SQL
Server authentication. (I was told that I can't use Windows
authentication because it is not in the domain.) From the box on
which the Hyperion fat client resides, I cannot register the eOn SQL
Server. The error message is "timeout expired". Tracerting indicates
there are no intermediate hops when attempting to connect from this
VLAN. From my desktop, which is on a different VLAN, I can connect to
and register it. This trip includes one hop at our 6509. From one of
my servers which is on the same VLAN as the fat-client box, I am able
to connect and register. On the fat-client box I tried deleting and
re-registering another SQL Server and there was no problem.
The IP address I have to use to connect to the eOn SQL Server is *NOT*
the actual IP address of the box it resides on, but rather the eOn
router, which translates it to the address of the server. We have no
control over this, eOn creates this setup. I'm not sure how it knows
which of the devices behind it a given message is for.
Ideas?Hi
Which version of SQL Server is on the telephony management system? At a
guess it is MSDE with no network protocols installed! Use svrnetcn.exe to
enable the network protcols. If they are running you may want to use the
SQLRecon tool to see what servers are available on your network
http://www.sqlsecurity.com/DesktopDefault.aspx?tabid=26
John
"Ellen K" wrote:
> Hi all,
> We have standardized on Hyperion as our reporting tool. So far I have
> only set up a couple of Access databases as data sources for it. Now
> there is a request to report off our eOn (telephony management) SQL
> Server database using Hyperion. The eOn SQL Server box is in a
> workgroup that is not part of the rest of our domain. (We only have
> one domain because we don't have a "forest", whatever that means.) It
> is behind a router owned by eOn along with a PBX and some other stuff.
>
> Setting up a data source for Hyperion requires creating a special data
> source file called an .oce on the box where the Hyperion fat client
> (required for most administrative tasks) resides, and also setting up a
> different special data source file called a .das on the server where
> the Hyperion services run. (The analysts and end-users do not have the
> fat client, their access is web-based.)
> I have to register the eOn SQL Server by using the IP address and SQL
> Server authentication. (I was told that I can't use Windows
> authentication because it is not in the domain.) From the box on
> which the Hyperion fat client resides, I cannot register the eOn SQL
> Server. The error message is "timeout expired". Tracerting indicates
> there are no intermediate hops when attempting to connect from this
> VLAN. From my desktop, which is on a different VLAN, I can connect to
> and register it. This trip includes one hop at our 6509. From one of
> my servers which is on the same VLAN as the fat-client box, I am able
> to connect and register. On the fat-client box I tried deleting and
> re-registering another SQL Server and there was no problem.
> The IP address I have to use to connect to the eOn SQL Server is *NOT*
> the actual IP address of the box it resides on, but rather the eOn
> router, which translates it to the address of the server. We have no
> control over this, eOn creates this setup. I'm not sure how it knows
> which of the devices behind it a given message is for.
> Ideas?
>|||Hi John,
Thanks for your response. I will check the version and also check
which network protocols are enabled on it, assuming I can get to the
box. But if the problem were no network protocols installed on the eOn
box then how would the other two boxes that CAN register it be able to
do so?
Thanks,
Ellen|||Hi
I hadn't realised that it could be registered elsewhere! This indicates that
there are network protocols, but they still may not be the same as the ones
on the client that can't register!! You may still want to try running
SQLRecon and also try to telnet into the port being used.
John
"Ellen K" wrote:
> Hi John,
> Thanks for your response. I will check the version and also check
> which network protocols are enabled on it, assuming I can get to the
> box. But if the problem were no network protocols installed on the eOn
> box then how would the other two boxes that CAN register it be able to
> do so?
> Thanks,
> Ellen
>|||Hi John,
Yes, I mentioned in my original post that I could register it from both
my desktop and from one of "my" servers.
The network protocols are the same on the eOn box as on "my" servers:
named pipes and tcp. Since the fat client can connect to "my" servers,
I think it's safe to say this isn't the problem.
I have now succeeded in creating an ODBC connection, which would not
have been my first choice, but right now if it works I'm happy.
Thanks,
Ellen
Subscribe to:
Posts (Atom)