"String constants must end with a double quote" error

Hi,
I've created a bunch of reports locally on my machine, where they all run
just fine, but when I try to deploy them to a server I run into some
problems.
I only have access to the server through a third party remote desktop
application (NetOp), so I have to do the deployment by manually uploading
the .rdl file in Report Manager. The reports uses MDX queries which I've had
to change into concatenated strings to allow for parameters, but when I try
to upload the files I only get the "BC30648 String constants must end with a
double quote." error.
If I remove the parameters, and the quotes around the whole query the files
upload just fine. Additionally, I've tried uploading the files manually both
on my own machine and a colleague's without getting this error. The reports
also run fine on these two machines after the upload (and configuration of
datasources).
Below is a sample of the query in a report that will throw the error on the
remote machine (for clarity this one doesn't use parameters):
<Query>
<DataSourceName>SullandGruppen</DataSourceName>
<CommandText>="SELECT
{[Measures].[Faktisk denne mnd]} ON COLUMNS,
{[Dato].[All Dato].[2004].[January]} ON ROWS
FROM Finanskube
WHERE
([Avdeling].[Salg],
[Avdelingsstruktur].[All Avdelingsstruktur].[3 Inntekter],
[Firma].[Gjovik Auto])"</CommandText>
<rd:UseGenericDesigner>true</rd:UseGenericDesigner>
</Query>
Does anyone have any idea why this might be happening? This is a fresh
install of Reporting Services, so I haven't tried deploying reports to it
before. It have only got the Server Components and .NET runtime installed.
Many thanks for any input!
-Christian NordbakkWell, my bad this one :o/
I had developed the reports on SP1 but forgotten to upgrade the server. That
caused the report to crash because of the query being split onto multiple
lines, which pre-SP1 doesn't support.
-Christian Nordbakk
"Christian Nordbakk" <cnordbakk@.gmail.com> wrote in message
news:%23hcuOyAwEHA.2172@.TK2MSFTNGP14.phx.gbl...
> Hi,
> I've created a bunch of reports locally on my machine, where they all run
> just fine, but when I try to deploy them to a server I run into some
> problems.
> I only have access to the server through a third party remote desktop
> application (NetOp), so I have to do the deployment by manually uploading
> the .rdl file in Report Manager. The reports uses MDX queries which I've
> had to change into concatenated strings to allow for parameters, but when
> I try to upload the files I only get the "BC30648 String constants must
> end with a double quote." error.
> If I remove the parameters, and the quotes around the whole query the
> files upload just fine. Additionally, I've tried uploading the files
> manually both on my own machine and a colleague's without getting this
> error. The reports also run fine on these two machines after the upload
> (and configuration of datasources).
> Below is a sample of the query in a report that will throw the error on
> the remote machine (for clarity this one doesn't use parameters):
> <Query>
> <DataSourceName>SullandGruppen</DataSourceName>
> <CommandText>="SELECT
> {[Measures].[Faktisk denne mnd]} ON COLUMNS,
> {[Dato].[All Dato].[2004].[January]} ON ROWS
> FROM Finanskube
> WHERE
> ([Avdeling].[Salg],
> [Avdelingsstruktur].[All Avdelingsstruktur].[3 Inntekter],
> [Firma].[Gjovik Auto])"</CommandText>
> <rd:UseGenericDesigner>true</rd:UseGenericDesigner>
> </Query>
>
> Does anyone have any idea why this might be happening? This is a fresh
> install of Reporting Services, so I haven't tried deploying reports to it
> before. It have only got the Server Components and .NET runtime installed.
> Many thanks for any input!
> -Christian Nordbakk
>

"Jump to Report" where the report is a linked report.

I setup a folder called _Master in Report Manager and I deploy all reports to
this folder. I setup additional folders through Report Manager that are
related to specific job functions: Sales, Customer Service, Marketing, etc.
Whenever I create a linked report using the "Jump to Report" feature in the
navigation tab, the linked report automatically defaults to the _Master
folder. Since I limit access to _Master solely to administrators, this means
I cannot use the "Jump to Report" drill down.
Is there any way to make the "Jump to Report" feature search for the report
in the current folder? I tried making references like ../Sales/Report1, but
this hard-coded Sales as the end folder. For instance, is there a way to do
../CurrentFolder/Report1 to make certain people in the Sales folder remain in
the Sales folder?
Sincerely,
Jonathan BaysThere is global variable Globals!ReportFolder
(http://msdn.microsoft.com/library/default.asp?url=/library/en-us/RSCREATE/htm/rcr_creating_expressions_v1_7ilv.asp
)
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Jonathan Bays" <JonathanBays@.discussions.microsoft.com> wrote in message
news:87926BDB-037E-419D-A591-22FF75B2F8A8@.microsoft.com...
>I setup a folder called _Master in Report Manager and I deploy all reports
>to
> this folder. I setup additional folders through Report Manager that are
> related to specific job functions: Sales, Customer Service, Marketing,
> etc.
> Whenever I create a linked report using the "Jump to Report" feature in
> the
> navigation tab, the linked report automatically defaults to the _Master
> folder. Since I limit access to _Master solely to administrators, this
> means
> I cannot use the "Jump to Report" drill down.
> Is there any way to make the "Jump to Report" feature search for the
> report
> in the current folder? I tried making references like ../Sales/Report1,
> but
> this hard-coded Sales as the end folder. For instance, is there a way to
> do
> ../CurrentFolder/Report1 to make certain people in the Sales folder remain
> in
> the Sales folder?
> Sincerely,
> Jonathan Bays

"HTTP status 400: Bad Request" - Reporting Services 2005

Has anyone ran into this error yet while testing Report Manager?
"The request failed with HTTP status 400: Bad Request."
I can deploy and access reports directly, but I receive the above error when
hitting the http://localhost/Reports URL (i.e. ReportManager)
Also, I'm seeing DCOM errors in the NT event log whenever this happens. A
search in the registry find CLSID references to network components (Network
Connection Manager Class, Network Connection Manager Connection Enumerator
Class, LAN Connection Manager Class, etc). Any ideas? Is there a security
configuration that I'm missing?
Here's an example entry:
Event Type: Error
Event Source: DCOM
Event Category: None
Event ID: 10016
Date: 11/8/2005
Time: 8:23:48 AM
User: NT AUTHORITY\NETWORK SERVICE
Computer: *SERVERNAME*
Description:
The application-specific permission settings do not grant Local Activation
permission for the COM Server application with CLSID
{BA126AD1-2166-11D1-B1D0-00805FC1270E}
to the user NT AUTHORITY\NETWORK SERVICE SID (S-1-5-20). This security
permission can be modified using the Component Services administrative tool.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.I have the same problem and it turns out that you need to change the IP
address of your default website to "(all Unassigned)", instead of
specifiying a specific IP address.
thuan wrote:
> Has anyone ran into this error yet while testing Report Manager?
> "The request failed with HTTP status 400: Bad Request."
> I can deploy and access reports directly, but I receive the above error when
> hitting the http://localhost/Reports URL (i.e. ReportManager)
> Also, I'm seeing DCOM errors in the NT event log whenever this happens. A
> search in the registry find CLSID references to network components (Network
> Connection Manager Class, Network Connection Manager Connection Enumerator
> Class, LAN Connection Manager Class, etc). Any ideas? Is there a security
> configuration that I'm missing?
> Here's an example entry:
> Event Type: Error
> Event Source: DCOM
> Event Category: None
> Event ID: 10016
> Date: 11/8/2005
> Time: 8:23:48 AM
> User: NT AUTHORITY\NETWORK SERVICE
> Computer: *SERVERNAME*
> Description:
> The application-specific permission settings do not grant Local Activation
> permission for the COM Server application with CLSID
> {BA126AD1-2166-11D1-B1D0-00805FC1270E}
> to the user NT AUTHORITY\NETWORK SERVICE SID (S-1-5-20). This security
> permission can be modified using the Component Services administrative tool.
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.

"Failed to open a rowset"

Help me... I have a report which I'm loading using the following code. When I deploy the application in a client's pc "Failed to open a rowset" is the error that appears. I am using an ODBC connection. Any help would be appreciated...

Dim cr As New crptCMR

Dim crtableLogoninfos As New TableLogOnInfos
Dim crtableLogoninfo As New TableLogOnInfo
Dim crConnectionInfo As New ConnectionInfo
Dim CrTables As Tables
Dim CrTable As Table
Dim TableCounter

Dim crReportDocument As New crptCMR

With crConnectionInfo
.ServerName = sname
.DatabaseName = dbname
.UserID = uid
.Password = pwd
End With

CrTables = crReportDocument.Database.Tables

For Each CrTable In CrTables
crtableLogoninfo = CrTable.LogOnInfo
crtableLogoninfo.ConnectionInfo = crConnectionInfo
CrTable.ApplyLogOnInfo(crtableLogoninfo)
Next

CRVcmr.ReportSource = crReportDocumentOpen the report and do verify database