dumb question...

After configuring exactly as specified in reporting services custom security, when I try to hit report manager, I keep on getting the error:

Invalid URI: The format of the URI could not be determined.

It does not redirct me to UILogin.aspx page but forwards me to Pages/Folder.aspx and gives this error.

Please if possible let me know ASAP.

I have the following in "rsreportserver.config" file

<UrlRoot>http://<computername>/reportserver</UrlRoot>

I have tried using "localhost" instead of computer name in the above line. Secondly, when I hit report manager, I thought it should redirect me to UILogin.aspx. It does not. And even if it did, I would like to know how it would do that because in report server, you specify the url in the <forms> tag. here there is no such tag that would make it redirect to UILogon.aspx.

I have the following in Web.config file of Report Manager

<authentication mode="Windows" />
<identity impersonate="false" />

I have the following in RsWebApplication.config file

<UI>
<ReportServerUrl></ReportServerUrl>
<ReportServerVirtualDirectory>ReportServer</ReportServerVirtualDirectory>
<CustomAuthenticationUI>
<loginUrl>UILogin.aspx</loginUrl>
<UseSSL>False</UseSSL>
</CustomAuthenticationUI>
</UI>

Thanks.

Thanks.

Solved it

There were 2 issues

the UILogon.aspx file was not under pages(wonder what that would do?)

Secondly, changed the ordering in RSWebApplication.config file to

<UI>
<CustomAuthenticationUI>
<loginUrl>/Pages/UILogon.aspx</loginUrl>
<UseSSL>False</UseSSL>
</CustomAuthenticationUI>
<ReportServerUrl>http://<computername>/ReportServer</ReportServerUrl>
</UI>

Finally, in the url requested

http://<computername>/Reports

|||

I been trying to get my own sql reporting services going... but i have so many issues..

the dumb question: does SQL 2005 Reporting Services require IIS 6.0 ? Windows 2003?

thanks

|||

Should work on xp pro . no need for windows 2003. For production deployment however, consider deploying enterprise version on windows server 2003.

Also always use iis6.0

|||

so, iis5 does not work?

DTS/ SQL Agent question

We're having to install new SQL servers on a new naming convention. We
know the changes we have to make on the applications that hit the SQL boxes.
However, we are not sure what DTS or SQL Agent jobs would need to be
changed.
Is there a way that we can search the DTS & SQL Agent jobs for a literal
that would refer to our old SQL server name and could identify & change
it to run on the new one?
Or,
is there a way to pass a parameter into the DTS or the Agent jobs that
would point them to the new server?
We're running Windows 2000, SQL 2000. We'll be moving to Windows 2003
and SQL 2000.
Any ideas appreciated.
Thanks,
BCFor the agent jobs, you can script them out and search through the SQL that
is created. For DTS, you could probably save it as a VB file and search
through that.
Hope this helps!
Chuck Heinzelman
MCSD, MCDBA
I support the Professional Association for SQL Server (www.sqlpass.org)
This posting is not an endoresment of any product.
Information is provided as-is, and carries no warranties - either express or
implied.
Please respond in newsgroups only.
"Blasting Cap" <goober@.christian.net> wrote in message
news:OtNNUaXaGHA.4780@.TK2MSFTNGP02.phx.gbl...
> We're having to install new SQL servers on a new naming convention. We
> know the changes we have to make on the applications that hit the SQL
> boxes.
> However, we are not sure what DTS or SQL Agent jobs would need to be
> changed.
> Is there a way that we can search the DTS & SQL Agent jobs for a literal
> that would refer to our old SQL server name and could identify & change it
> to run on the new one?
> Or,
> is there a way to pass a parameter into the DTS or the Agent jobs that
> would point them to the new server?
> We're running Windows 2000, SQL 2000. We'll be moving to Windows 2003 and
> SQL 2000.
> Any ideas appreciated.
> Thanks,
> BC

DTS/ SQL Agent question

We're having to install new SQL servers on a new naming convention. We
know the changes we have to make on the applications that hit the SQL boxes.
However, we are not sure what DTS or SQL Agent jobs would need to be
changed.
Is there a way that we can search the DTS & SQL Agent jobs for a literal
that would refer to our old SQL server name and could identify & change
it to run on the new one?
Or,
is there a way to pass a parameter into the DTS or the Agent jobs that
would point them to the new server?
We're running Windows 2000, SQL 2000. We'll be moving to Windows 2003
and SQL 2000.
Any ideas appreciated.
Thanks,
BCFor the agent jobs, you can script them out and search through the SQL that
is created. For DTS, you could probably save it as a VB file and search
through that.
Hope this helps!
Chuck Heinzelman
MCSD, MCDBA
I support the Professional Association for SQL Server (www.sqlpass.org)
This posting is not an endoresment of any product.
Information is provided as-is, and carries no warranties - either express or
implied.
Please respond in newsgroups only.
"Blasting Cap" <goober@.christian.net> wrote in message
news:OtNNUaXaGHA.4780@.TK2MSFTNGP02.phx.gbl...
> We're having to install new SQL servers on a new naming convention. We
> know the changes we have to make on the applications that hit the SQL
> boxes.
> However, we are not sure what DTS or SQL Agent jobs would need to be
> changed.
> Is there a way that we can search the DTS & SQL Agent jobs for a literal
> that would refer to our old SQL server name and could identify & change it
> to run on the new one?
> Or,
> is there a way to pass a parameter into the DTS or the Agent jobs that
> would point them to the new server?
> We're running Windows 2000, SQL 2000. We'll be moving to Windows 2003 and
> SQL 2000.
> Any ideas appreciated.
> Thanks,
> BC

DTS/ SQL Agent question

We're having to install new SQL servers on a new naming convention. We
know the changes we have to make on the applications that hit the SQL boxes.
However, we are not sure what DTS or SQL Agent jobs would need to be
changed.
Is there a way that we can search the DTS & SQL Agent jobs for a literal
that would refer to our old SQL server name and could identify & change
it to run on the new one?
Or,
is there a way to pass a parameter into the DTS or the Agent jobs that
would point them to the new server?
We're running Windows 2000, SQL 2000. We'll be moving to Windows 2003
and SQL 2000.
Any ideas appreciated.
Thanks,
BCFor the agent jobs, you can script them out and search through the SQL that
is created. For DTS, you could probably save it as a VB file and search
through that.
Hope this helps!
--
Chuck Heinzelman
MCSD, MCDBA
I support the Professional Association for SQL Server (www.sqlpass.org)
This posting is not an endoresment of any product.
Information is provided as-is, and carries no warranties - either express or
implied.
Please respond in newsgroups only.
"Blasting Cap" <goober@.christian.net> wrote in message
news:OtNNUaXaGHA.4780@.TK2MSFTNGP02.phx.gbl...
> We're having to install new SQL servers on a new naming convention. We
> know the changes we have to make on the applications that hit the SQL
> boxes.
> However, we are not sure what DTS or SQL Agent jobs would need to be
> changed.
> Is there a way that we can search the DTS & SQL Agent jobs for a literal
> that would refer to our old SQL server name and could identify & change it
> to run on the new one?
> Or,
> is there a way to pass a parameter into the DTS or the Agent jobs that
> would point them to the new server?
> We're running Windows 2000, SQL 2000. We'll be moving to Windows 2003 and
> SQL 2000.
> Any ideas appreciated.
> Thanks,
> BC