Problem passing a parameter in URL to a report

Hi all.
I have that problem. I need to pass a parameter to a report. That parameter
is a user in a windows domain, so I have the problem that is stored in
"DOMAIN\USER" format, and I can't pass the backslash to the url.
How can I solve that?
--
Regards,
Diego F.I ask myself. I can encode \ with %5C.
I'm embarrased for that stupid question...
--
Regards,
Diego F.
"Diego F." <diegofrNO@.terra.es> escribió en el mensaje
news:OUA34HxMGHA.344@.TK2MSFTNGP11.phx.gbl...
> Hi all.
> I have that problem. I need to pass a parameter to a report. That
> parameter is a user in a windows domain, so I have the problem that is
> stored in "DOMAIN\USER" format, and I can't pass the backslash to the url.
> How can I solve that?
> --
> Regards,
> Diego F.
>
>|||Also, you might not even need to do this. Look at the global variables in
the expression builder User!UserID, it is the user running the report.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Diego F." <diegofrNO@.terra.es> wrote in message
news:OTaydMxMGHA.720@.TK2MSFTNGP14.phx.gbl...
>I ask myself. I can encode \ with %5C.
> I'm embarrased for that stupid question...
> --
> Regards,
> Diego F.
>
> "Diego F." <diegofrNO@.terra.es> escribió en el mensaje
> news:OUA34HxMGHA.344@.TK2MSFTNGP11.phx.gbl...
>> Hi all.
>> I have that problem. I need to pass a parameter to a report. That
>> parameter is a user in a windows domain, so I have the problem that is
>> stored in "DOMAIN\USER" format, and I can't pass the backslash to the
>> url.
>> How can I solve that?
>> --
>> Regards,
>> Diego F.
>>
>|||... or you can use POST instead of GET. In other words, you can pass
parameters in a form instead of passing by querystring.

Problem installing SQL 2005 on a Windows 2003 DC

Hello to all,

we try to install an SQL 2005 server on a Windows 2003 server that is also a Domain controller. In discussions of july last year, Dan Jones said :"Unfortunately in setup you cannot change the default account for all services. So there is absolutely no work around for this problem. This will absolutely be fixed by RTM - "

Can anybody help me in that way. We tried installing with our latest CDs (december 2005)

It's not clear what your problem is. Are you having trouble installing? If so, what is the behavior you're seeing.|||The problem is during installing. Despite the fact that we allocate a domain user account as user for the service accounts, we have a error message "Failure creating local group SQLServer2005SQLBrowserUser$<servername> and the installation does not continue.|||The user that your running setup as doesn't have the correct permissions on the DC to create a new group. To work around this have the group created prior to running setup. In addition, if you don't have permission to add users to a group you can add the domain user to the group prior to running setup. During setup it'll check for the existence of the group and that the user is part of the group. If you set this up prior to running setup you don't need the create group and add to group permissions.|||

I set up different security groups having the name of the desired groups:

SQLServer2005DTSUser$SRV05FIL01

SQLServer2005MSFTEUser$SRV05FIL01$MSSQLSERVER

SQLServer2005MSOLAPUser$SRV05FIL01$MSSQLSERVER

SQLServer2005MSSQLServerADHelperUser$SRV05FIL01

SQLServer2005MSSQLUser$SRV05FIL01$MSSQLSERVER

SQLServer2005NotificationServicesUser$SRV05FIL01

SQLServer2005ReportingServicesWebServiceUser$SRV05FIL01$MSSQLSER

SQLServer2005ReportServerUser$SRV05FIL01$MSSQLSERVER

SQLServer2005SQLAgentUser$SRV05FIL01$MSSQLSERVER

SQLServer2005SQLBrowserUser$SRV05FIL01

Those groups have as members the user that is running the setup, domain-user and domain-admin. The problem is still the same: error message: "Failure creating local group SQLServer2005SQLAgentUser$SRV05FIL01$MSSQLSERVER".

As we have a DC, there is no way to declare local groups.

I can send you the logfile if desired.

|||Go ahead and log a bug using: http://lab.msdn.microsoft.com/ProductFeedback/|||

Create those groups on you 1st domain controller , force a replication of AD and you have all these groups on your new server . the installation of sql will now find these groups and set the security on it..

Gtz

Problem installing SQL 2005 on a Windows 2003 DC

Hello to all,

we try to install an SQL 2005 server on a Windows 2003 server that is also a Domain controller. In discussions of july last year, Dan Jones said :"Unfortunately in setup you cannot change the default account for all services. So there is absolutely no work around for this problem. This will absolutely be fixed by RTM - "

Can anybody help me in that way. We tried installing with our latest CDs (december 2005)

It's not clear what your problem is. Are you having trouble installing? If so, what is the behavior you're seeing.|||The problem is during installing. Despite the fact that we allocate a domain user account as user for the service accounts, we have a error message "Failure creating local group SQLServer2005SQLBrowserUser$<servername> and the installation does not continue.|||The user that your running setup as doesn't have the correct permissions on the DC to create a new group. To work around this have the group created prior to running setup. In addition, if you don't have permission to add users to a group you can add the domain user to the group prior to running setup. During setup it'll check for the existence of the group and that the user is part of the group. If you set this up prior to running setup you don't need the create group and add to group permissions.|||

I set up different security groups having the name of the desired groups:

SQLServer2005DTSUser$SRV05FIL01

SQLServer2005MSFTEUser$SRV05FIL01$MSSQLSERVER

SQLServer2005MSOLAPUser$SRV05FIL01$MSSQLSERVER

SQLServer2005MSSQLServerADHelperUser$SRV05FIL01

SQLServer2005MSSQLUser$SRV05FIL01$MSSQLSERVER

SQLServer2005NotificationServicesUser$SRV05FIL01

SQLServer2005ReportingServicesWebServiceUser$SRV05FIL01$MSSQLSER

SQLServer2005ReportServerUser$SRV05FIL01$MSSQLSERVER

SQLServer2005SQLAgentUser$SRV05FIL01$MSSQLSERVER

SQLServer2005SQLBrowserUser$SRV05FIL01

Those groups have as members the user that is running the setup, domain-user and domain-admin. The problem is still the same: error message: "Failure creating local group SQLServer2005SQLAgentUser$SRV05FIL01$MSSQLSERVER".

As we have a DC, there is no way to declare local groups.

I can send you the logfile if desired.

|||Go ahead and log a bug using: http://lab.msdn.microsoft.com/ProductFeedback/|||

Create those groups on you 1st domain controller , force a replication of AD and you have all these groups on your new server . the installation of sql will now find these groups and set the security on it..

Gtz

Problem installing Advanced Services on Domain Controller

I try to install SQL Express Edition with Advanced Services on Small Business Server 2003 Standard Edition. Actually I install it without any problems.

I set database service (SQL SERVER (SQLEXPRESS)) to use domain account (administrator of domain). I configure report server windows identity to domain account (administrator of domain). When I try to access page Reports I have following problem . Error is

Unable to connect to the remote server.

Please, can somebody help me?

this is I found in log file

w3wp!ui!1!25.4.2006-08:00:35:: e ERROR: Unable to connect to the remote server
w3wp!ui!1!25.4.2006-08:00:37:: e ERROR: HTTP status code --> 500
-Details--
System.Net.WebException: Unable to connect to the remote server > System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it
at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
at System.Net.Sockets.Socket.InternalConnect(EndPoint remoteEP)
at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Int32 timeout, Exception& exception)
End of inner exception stack trace
at System.Net.HttpWebRequest.GetRequestStream()
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at Microsoft.SqlServer.ReportingServices2005.ReportingService2005.ListSecureMethods()
at Microsoft.SqlServer.ReportingServices2005.RSConnection.ValidateConnection()
at Microsoft.ReportingServices.UI.ReportingPage.EnsureHttpsLevel(HttpsLevel level)
at Microsoft.ReportingServices.UI.ReportingPage.ReportingPage_Init(Object sender, EventArgs args)
at System.EventHandler.Invoke(Object sender, EventArgs e)
at System.Web.UI.Control.OnInit(EventArgs e)
at System.Web.UI.Page.OnInit(EventArgs e)
at System.Web.UI.Control.InitRecursive(Control namingContainer)
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
w3wp!ui!1!25.4.2006-08:00:38:: e ERROR: Exception in ShowErrorPage: System.Threading.ThreadAbortException: Thread was being aborted.
at System.Threading.Thread.AbortInternal()
at System.Threading.Thread.Abort(Object stateInfo)
at System.Web.HttpResponse.End()
at System.Web.HttpServerUtility.Transfer(String path, Boolean preserveForm)
at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String errMsg) at at System.Threading.Thread.AbortInternal()
at System.Threading.Thread.Abort(Object stateInfo)
at System.Web.HttpResponse.End()
at System.Web.HttpServerUtility.Transfer(String path, Boolean preserveForm)
at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String errMsg)

What Reports are you trying to access? Do they have anything to do with SQL Express? (Are you talking about SQL Reporting Services?)

Why are you trying to run SQL Express on a Domain Controller in the first place?

Regards,

Mike Wachal
SQL Express team

-
Please mark your thread as Answered when you get your solution.

|||

I try to access http://localhost/reports$sqlexpress. (Yes this is reporting services.)

I have only one server in domain (small business server 2003). I do not want to install SQL Express with Advanced Services on client computer.

|||

I'm moving this over to the Reporting Service forum as they'll have a better idea what is going on with this issue.

- Mike