Got this error message while trying to load a sub-report from an existing
report and passing a parameter into the sub-report. I created the report
parameter just like it did for the source report. Please help.That means you forgot to provide a Prompt for the parameter in the
subreport.
Omitting the Prompt indicates to the server that the user should not be
prompted for a value (hence: read-only).
--
My employer's lawyers require me to say:
"This posting is provided 'AS IS' with no warranties, and confers no
rights."
"John Cosmas" <vabo214@.msn.com> wrote in message
news:OKnfI3WZEHA.3228@.TK2MSFTNGP12.phx.gbl...
> Got this error message while trying to load a sub-report from an existing
> report and passing a parameter into the sub-report. I created the report
> parameter just like it did for the source report. Please help.
>
Showing posts with label message. Show all posts
Showing posts with label message. Show all posts
Friday, March 30, 2012
report parameter order
hi,
after changing the order of my report parameters (in this example test)
in the menue via the up and down arrow I get the following error
message:
an error occured during local processing. an error occured during
report processing. the value expression for the query parameter 'date'
contains an error: the expression referenced a non-existing parameter
in the report parameters collection.
anybody knows how to do this?
thanksIt sounds like you have either:
A) deleted a parameter which was there before, or more likely
B) changed the sequence required for cascading parameters, i.e. parameters
where one value depends on another one previously entered. It is probably
something to do with one of your report parameters' 'available values' or
'default values' definitions.
HTH,
Magendo_man
"florian" wrote:
> hi,
> after changing the order of my report parameters (in this example test)
> in the menue via the up and down arrow I get the following error
> message:
> an error occured during local processing. an error occured during
> report processing. the value expression for the query parameter 'date'
> contains an error: the expression referenced a non-existing parameter
> in the report parameters collection.
> anybody knows how to do this?
> thanks
>|||You're right I got this error msg. with cascading parameters. The
hierachie goes like this: A-->B-->C Originally I only included A and C
in my parameters but B was missing. So I added B but I didn't like it
to occure as the last report parameter so I wanted to change the
position and then I got the error msg. I get the same error when I
modifie the rdl file and swith the Report Parameters.
Any ideas instead of writing the whole report once again?
magendo_man schrieb:
> It sounds like you have either:
> A) deleted a parameter which was there before, or more likely
> B) changed the sequence required for cascading parameters, i.e. parameters
> where one value depends on another one previously entered. It is probably
> something to do with one of your report parameters' 'available values' or
> 'default values' definitions.
> HTH,
> Magendo_man
> "florian" wrote:
> > hi,
> >
> > after changing the order of my report parameters (in this example test)
> > in the menue via the up and down arrow I get the following error
> > message:
> >
> > an error occured during local processing. an error occured during
> > report processing. the value expression for the query parameter 'date'
> > contains an error: the expression referenced a non-existing parameter
> > in the report parameters collection.
> >
> > anybody knows how to do this?
> >
> > thanks
> >
> >|||Just add parameter B back in to Report Parameters in 2nd position.
"florian" wrote:
> You're right I got this error msg. with cascading parameters. The
> hierachie goes like this: A-->B-->C Originally I only included A and C
> in my parameters but B was missing. So I added B but I didn't like it
> to occure as the last report parameter so I wanted to change the
> position and then I got the error msg. I get the same error when I
> modifie the rdl file and swith the Report Parameters.
> Any ideas instead of writing the whole report once again?
>
> magendo_man schrieb:
> > It sounds like you have either:
> > A) deleted a parameter which was there before, or more likely
> > B) changed the sequence required for cascading parameters, i.e. parameters
> > where one value depends on another one previously entered. It is probably
> > something to do with one of your report parameters' 'available values' or
> > 'default values' definitions.
> >
> > HTH,
> > Magendo_man
> >
> > "florian" wrote:
> >
> > > hi,
> > >
> > > after changing the order of my report parameters (in this example test)
> > > in the menue via the up and down arrow I get the following error
> > > message:
> > >
> > > an error occured during local processing. an error occured during
> > > report processing. the value expression for the query parameter 'date'
> > > contains an error: the expression referenced a non-existing parameter
> > > in the report parameters collection.
> > >
> > > anybody knows how to do this?
> > >
> > > thanks
> > >
> > >
>|||do mean at the data view or where?
magendo_man schrieb:
> Just add parameter B back in to Report Parameters in 2nd position.
> "florian" wrote:
> > You're right I got this error msg. with cascading parameters. The
> > hierachie goes like this: A-->B-->C Originally I only included A and C
> > in my parameters but B was missing. So I added B but I didn't like it
> > to occure as the last report parameter so I wanted to change the
> > position and then I got the error msg. I get the same error when I
> > modifie the rdl file and swith the Report Parameters.
> >
> > Any ideas instead of writing the whole report once again?
> >
> >
> > magendo_man schrieb:
> >
> > > It sounds like you have either:
> > > A) deleted a parameter which was there before, or more likely
> > > B) changed the sequence required for cascading parameters, i.e. parameters
> > > where one value depends on another one previously entered. It is probably
> > > something to do with one of your report parameters' 'available values' or
> > > 'default values' definitions.
> > >
> > > HTH,
> > > Magendo_man
> > >
> > > "florian" wrote:
> > >
> > > > hi,
> > > >
> > > > after changing the order of my report parameters (in this example test)
> > > > in the menue via the up and down arrow I get the following error
> > > > message:
> > > >
> > > > an error occured during local processing. an error occured during
> > > > report processing. the value expression for the query parameter 'date'
> > > > contains an error: the expression referenced a non-existing parameter
> > > > in the report parameters collection.
> > > >
> > > > anybody knows how to do this?
> > > >
> > > > thanks
> > > >
> > > >
> >
> >|||In Layout view select from the menu Report> Report Parameters..
You should then be able to add back in your deleted parameter and move it in
to the correct position.
~ Magendo_man
"florian" wrote:
> do mean at the data view or where?
>
> magendo_man schrieb:
> > Just add parameter B back in to Report Parameters in 2nd position.
> >
> > "florian" wrote:
> >
> > > You're right I got this error msg. with cascading parameters. The
> > > hierachie goes like this: A-->B-->C Originally I only included A and C
> > > in my parameters but B was missing. So I added B but I didn't like it
> > > to occure as the last report parameter so I wanted to change the
> > > position and then I got the error msg. I get the same error when I
> > > modifie the rdl file and swith the Report Parameters.
> > >
> > > Any ideas instead of writing the whole report once again?
> > >
> > >
> > > magendo_man schrieb:
> > >
> > > > It sounds like you have either:
> > > > A) deleted a parameter which was there before, or more likely
> > > > B) changed the sequence required for cascading parameters, i.e. parameters
> > > > where one value depends on another one previously entered. It is probably
> > > > something to do with one of your report parameters' 'available values' or
> > > > 'default values' definitions.
> > > >
> > > > HTH,
> > > > Magendo_man
> > > >
> > > > "florian" wrote:
> > > >
> > > > > hi,
> > > > >
> > > > > after changing the order of my report parameters (in this example test)
> > > > > in the menue via the up and down arrow I get the following error
> > > > > message:
> > > > >
> > > > > an error occured during local processing. an error occured during
> > > > > report processing. the value expression for the query parameter 'date'
> > > > > contains an error: the expression referenced a non-existing parameter
> > > > > in the report parameters collection.
> > > > >
> > > > > anybody knows how to do this?
> > > > >
> > > > > thanks
> > > > >
> > > > >
> > >
> > >
>sql
after changing the order of my report parameters (in this example test)
in the menue via the up and down arrow I get the following error
message:
an error occured during local processing. an error occured during
report processing. the value expression for the query parameter 'date'
contains an error: the expression referenced a non-existing parameter
in the report parameters collection.
anybody knows how to do this?
thanksIt sounds like you have either:
A) deleted a parameter which was there before, or more likely
B) changed the sequence required for cascading parameters, i.e. parameters
where one value depends on another one previously entered. It is probably
something to do with one of your report parameters' 'available values' or
'default values' definitions.
HTH,
Magendo_man
"florian" wrote:
> hi,
> after changing the order of my report parameters (in this example test)
> in the menue via the up and down arrow I get the following error
> message:
> an error occured during local processing. an error occured during
> report processing. the value expression for the query parameter 'date'
> contains an error: the expression referenced a non-existing parameter
> in the report parameters collection.
> anybody knows how to do this?
> thanks
>|||You're right I got this error msg. with cascading parameters. The
hierachie goes like this: A-->B-->C Originally I only included A and C
in my parameters but B was missing. So I added B but I didn't like it
to occure as the last report parameter so I wanted to change the
position and then I got the error msg. I get the same error when I
modifie the rdl file and swith the Report Parameters.
Any ideas instead of writing the whole report once again?
magendo_man schrieb:
> It sounds like you have either:
> A) deleted a parameter which was there before, or more likely
> B) changed the sequence required for cascading parameters, i.e. parameters
> where one value depends on another one previously entered. It is probably
> something to do with one of your report parameters' 'available values' or
> 'default values' definitions.
> HTH,
> Magendo_man
> "florian" wrote:
> > hi,
> >
> > after changing the order of my report parameters (in this example test)
> > in the menue via the up and down arrow I get the following error
> > message:
> >
> > an error occured during local processing. an error occured during
> > report processing. the value expression for the query parameter 'date'
> > contains an error: the expression referenced a non-existing parameter
> > in the report parameters collection.
> >
> > anybody knows how to do this?
> >
> > thanks
> >
> >|||Just add parameter B back in to Report Parameters in 2nd position.
"florian" wrote:
> You're right I got this error msg. with cascading parameters. The
> hierachie goes like this: A-->B-->C Originally I only included A and C
> in my parameters but B was missing. So I added B but I didn't like it
> to occure as the last report parameter so I wanted to change the
> position and then I got the error msg. I get the same error when I
> modifie the rdl file and swith the Report Parameters.
> Any ideas instead of writing the whole report once again?
>
> magendo_man schrieb:
> > It sounds like you have either:
> > A) deleted a parameter which was there before, or more likely
> > B) changed the sequence required for cascading parameters, i.e. parameters
> > where one value depends on another one previously entered. It is probably
> > something to do with one of your report parameters' 'available values' or
> > 'default values' definitions.
> >
> > HTH,
> > Magendo_man
> >
> > "florian" wrote:
> >
> > > hi,
> > >
> > > after changing the order of my report parameters (in this example test)
> > > in the menue via the up and down arrow I get the following error
> > > message:
> > >
> > > an error occured during local processing. an error occured during
> > > report processing. the value expression for the query parameter 'date'
> > > contains an error: the expression referenced a non-existing parameter
> > > in the report parameters collection.
> > >
> > > anybody knows how to do this?
> > >
> > > thanks
> > >
> > >
>|||do mean at the data view or where?
magendo_man schrieb:
> Just add parameter B back in to Report Parameters in 2nd position.
> "florian" wrote:
> > You're right I got this error msg. with cascading parameters. The
> > hierachie goes like this: A-->B-->C Originally I only included A and C
> > in my parameters but B was missing. So I added B but I didn't like it
> > to occure as the last report parameter so I wanted to change the
> > position and then I got the error msg. I get the same error when I
> > modifie the rdl file and swith the Report Parameters.
> >
> > Any ideas instead of writing the whole report once again?
> >
> >
> > magendo_man schrieb:
> >
> > > It sounds like you have either:
> > > A) deleted a parameter which was there before, or more likely
> > > B) changed the sequence required for cascading parameters, i.e. parameters
> > > where one value depends on another one previously entered. It is probably
> > > something to do with one of your report parameters' 'available values' or
> > > 'default values' definitions.
> > >
> > > HTH,
> > > Magendo_man
> > >
> > > "florian" wrote:
> > >
> > > > hi,
> > > >
> > > > after changing the order of my report parameters (in this example test)
> > > > in the menue via the up and down arrow I get the following error
> > > > message:
> > > >
> > > > an error occured during local processing. an error occured during
> > > > report processing. the value expression for the query parameter 'date'
> > > > contains an error: the expression referenced a non-existing parameter
> > > > in the report parameters collection.
> > > >
> > > > anybody knows how to do this?
> > > >
> > > > thanks
> > > >
> > > >
> >
> >|||In Layout view select from the menu Report> Report Parameters..
You should then be able to add back in your deleted parameter and move it in
to the correct position.
~ Magendo_man
"florian" wrote:
> do mean at the data view or where?
>
> magendo_man schrieb:
> > Just add parameter B back in to Report Parameters in 2nd position.
> >
> > "florian" wrote:
> >
> > > You're right I got this error msg. with cascading parameters. The
> > > hierachie goes like this: A-->B-->C Originally I only included A and C
> > > in my parameters but B was missing. So I added B but I didn't like it
> > > to occure as the last report parameter so I wanted to change the
> > > position and then I got the error msg. I get the same error when I
> > > modifie the rdl file and swith the Report Parameters.
> > >
> > > Any ideas instead of writing the whole report once again?
> > >
> > >
> > > magendo_man schrieb:
> > >
> > > > It sounds like you have either:
> > > > A) deleted a parameter which was there before, or more likely
> > > > B) changed the sequence required for cascading parameters, i.e. parameters
> > > > where one value depends on another one previously entered. It is probably
> > > > something to do with one of your report parameters' 'available values' or
> > > > 'default values' definitions.
> > > >
> > > > HTH,
> > > > Magendo_man
> > > >
> > > > "florian" wrote:
> > > >
> > > > > hi,
> > > > >
> > > > > after changing the order of my report parameters (in this example test)
> > > > > in the menue via the up and down arrow I get the following error
> > > > > message:
> > > > >
> > > > > an error occured during local processing. an error occured during
> > > > > report processing. the value expression for the query parameter 'date'
> > > > > contains an error: the expression referenced a non-existing parameter
> > > > > in the report parameters collection.
> > > > >
> > > > > anybody knows how to do this?
> > > > >
> > > > > thanks
> > > > >
> > > > >
> > >
> > >
>sql
Wednesday, March 28, 2012
Report Paging
This is a multi-part message in MIME format.
--=_NextPart_000_00B0_01C7B32E.8ACDD040
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
How do I define the number of lines per page in Report Designer? I have = defined the report as 11" x 8.5" landscape but when I preview or print, = I am getting alternate correctly numbered pages consisting just a report = header & report footer. I'm assuming that it is related to an issue = with rows per page, but am unable to find the definition to give that a = try.
--=_NextPart_000_00B0_01C7B32E.8ACDD040
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
How do I define the = number of lines per page in Report Designer? I have defined the report as = 11=94 x 8.5=94 landscape but when I preview or print, I am getting alternate correctly = numbered pages consisting just a report header & report footer. I=92m = assuming that it is related to an issue with rows per page, but am unable to find = the definition to give that a try.
--=_NextPart_000_00B0_01C7B32E.8ACDD040--On Jun 20, 2:31 pm, "Joe" <hortoris...@.gmail.dot.com> wrote:
> How do I define the number of lines per page in Report Designer? I have defined the report as 11" x 8.5" landscape but when I preview or print, I am getting alternate correctly numbered pages consisting just a report header & report footer. I'm assuming that it is related to an issue with rows per page, but am unable to find the definition to give that a try.
What is the width of the report body? If the body is wider than page
then you will get these extra pages. It doesn't matter if there is
nothing to display, it will still think your report needs to be that
wide.|||There's a good explanation of report paging in
http://blogs.msdn.com/bwelcker/archive/2005/08/19/454043.aspx.
However, even having followed the instructions on this blog, we have
problems with report paging as well. We seem to have some reports that show
fewer pages in the report viewer than when they are printed to pdf or the
printer. We even have one report, that depending on the parameters, shows as
a single page in the viewer and many pages when printing in pdf or the
printer. Are there other people having these problems as well?
"Joe" wrote:
> How do I define the number of lines per page in Report Designer? I have defined the report as 11" x 8.5" landscape but when I preview or print, I am getting alternate correctly numbered pages consisting just a report header & report footer. I'm assuming that it is related to an issue with rows per page, but am unable to find the definition to give that a try
--=_NextPart_000_00B0_01C7B32E.8ACDD040
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
How do I define the number of lines per page in Report Designer? I have = defined the report as 11" x 8.5" landscape but when I preview or print, = I am getting alternate correctly numbered pages consisting just a report = header & report footer. I'm assuming that it is related to an issue = with rows per page, but am unable to find the definition to give that a = try.
--=_NextPart_000_00B0_01C7B32E.8ACDD040
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
How do I define the = number of lines per page in Report Designer? I have defined the report as = 11=94 x 8.5=94 landscape but when I preview or print, I am getting alternate correctly = numbered pages consisting just a report header & report footer. I=92m = assuming that it is related to an issue with rows per page, but am unable to find = the definition to give that a try.
--=_NextPart_000_00B0_01C7B32E.8ACDD040--On Jun 20, 2:31 pm, "Joe" <hortoris...@.gmail.dot.com> wrote:
> How do I define the number of lines per page in Report Designer? I have defined the report as 11" x 8.5" landscape but when I preview or print, I am getting alternate correctly numbered pages consisting just a report header & report footer. I'm assuming that it is related to an issue with rows per page, but am unable to find the definition to give that a try.
What is the width of the report body? If the body is wider than page
then you will get these extra pages. It doesn't matter if there is
nothing to display, it will still think your report needs to be that
wide.|||There's a good explanation of report paging in
http://blogs.msdn.com/bwelcker/archive/2005/08/19/454043.aspx.
However, even having followed the instructions on this blog, we have
problems with report paging as well. We seem to have some reports that show
fewer pages in the report viewer than when they are printed to pdf or the
printer. We even have one report, that depending on the parameters, shows as
a single page in the viewer and many pages when printing in pdf or the
printer. Are there other people having these problems as well?
"Joe" wrote:
> How do I define the number of lines per page in Report Designer? I have defined the report as 11" x 8.5" landscape but when I preview or print, I am getting alternate correctly numbered pages consisting just a report header & report footer. I'm assuming that it is related to an issue with rows per page, but am unable to find the definition to give that a try
Friday, March 23, 2012
Report Model on tables without primary key
I am trying to create a report model on some tables that do not have a
primary key. The wizard keeps failing with the message "Table does not have a
primary key". Is a primary key mandatory?You could define logic primary key in your dsv.
"Dan Varozza" wrote:
> I am trying to create a report model on some tables that do not have a
> primary key. The wizard keeps failing with the message "Table does not have a
> primary key". Is a primary key mandatory?|||WHen I run the DSV wizard it tells me that "no foreign keys were found. You
can create logical relationships on matching columns."
Then it gives me the choice to "Create logical relationships by matching
columns" and 3 Foreign Key Matches to choose from:
"Same as Primary key"
or
"Same name as destination table name"
or
"Destination table name + primary key name"
I have tried all 3 of the choices above and still the wizard fails with the
same error. "Table does not have a primary key".
Any ideas?
"yongli" wrote:
> You could define logic primary key in your dsv.
> "Dan Varozza" wrote:
> > I am trying to create a report model on some tables that do not have a
> > primary key. The wizard keeps failing with the message "Table does not have a
> > primary key". Is a primary key mandatory?sql
primary key. The wizard keeps failing with the message "Table does not have a
primary key". Is a primary key mandatory?You could define logic primary key in your dsv.
"Dan Varozza" wrote:
> I am trying to create a report model on some tables that do not have a
> primary key. The wizard keeps failing with the message "Table does not have a
> primary key". Is a primary key mandatory?|||WHen I run the DSV wizard it tells me that "no foreign keys were found. You
can create logical relationships on matching columns."
Then it gives me the choice to "Create logical relationships by matching
columns" and 3 Foreign Key Matches to choose from:
"Same as Primary key"
or
"Same name as destination table name"
or
"Destination table name + primary key name"
I have tried all 3 of the choices above and still the wizard fails with the
same error. "Table does not have a primary key".
Any ideas?
"yongli" wrote:
> You could define logic primary key in your dsv.
> "Dan Varozza" wrote:
> > I am trying to create a report model on some tables that do not have a
> > primary key. The wizard keeps failing with the message "Table does not have a
> > primary key". Is a primary key mandatory?sql
Monday, March 12, 2012
Report Manager in SQL Exprtess
I cannot get report manager to load in IE 7 after installing on SQL Express,
advanced edition. The error message is "The ReportServerVirtualDirectory
element is missing". When I check the reporting services configuration file,
there is no XML tag for this (Should there be?). In the reporting services
configuration manager, it shows as not being installed, but when I try to
install, it says it is. It is a little confusing, but basically on the
right-hand side it display a red "X" by report manager, but a green checkmark
on the left-hand side. Note that the report server loads fine in IE 7.On Sep 4, 2:14 pm, Craig Plank, SBS
<CraigPlank...@.discussions.microsoft.com> wrote:
> I cannot get report manager to load in IE 7 after installing on SQL Express,
> advanced edition. The error message is "The ReportServerVirtualDirectory
> element is missing". When I check the reporting services configuration file,
> there is no XML tag for this (Should there be?). In the reporting services
> configuration manager, it shows as not being installed, but when I try to
> install, it says it is. It is a little confusing, but basically on the
> right-hand side it display a red "X" by report manager, but a green checkmark
> on the left-hand side. Note that the report server loads fine in IE 7.
This article might help.
http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=1532003&SiteID=17
Regards,
Enrique Martinez
Sr. Software Consultant
advanced edition. The error message is "The ReportServerVirtualDirectory
element is missing". When I check the reporting services configuration file,
there is no XML tag for this (Should there be?). In the reporting services
configuration manager, it shows as not being installed, but when I try to
install, it says it is. It is a little confusing, but basically on the
right-hand side it display a red "X" by report manager, but a green checkmark
on the left-hand side. Note that the report server loads fine in IE 7.On Sep 4, 2:14 pm, Craig Plank, SBS
<CraigPlank...@.discussions.microsoft.com> wrote:
> I cannot get report manager to load in IE 7 after installing on SQL Express,
> advanced edition. The error message is "The ReportServerVirtualDirectory
> element is missing". When I check the reporting services configuration file,
> there is no XML tag for this (Should there be?). In the reporting services
> configuration manager, it shows as not being installed, but when I try to
> install, it says it is. It is a little confusing, but basically on the
> right-hand side it display a red "X" by report manager, but a green checkmark
> on the left-hand side. Note that the report server loads fine in IE 7.
This article might help.
http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=1532003&SiteID=17
Regards,
Enrique Martinez
Sr. Software Consultant
Report Manager error
When I try to start report manager, I get the following error message. What do I need to do?
Server Error in '/Reports' Application.
Parser Error
Description: An error occurred during the parsing of a resource required to service this request. Please review the following specific parse error details and modify your source file appropriately.
Parser Error Message: Could not load type 'Microsoft.ReportingServices.UI.GlobalApp'.
Source Error:
|
Source File: C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportManager\global.asax Line: 1
Version Information: Microsoft .NET Framework Version:1.1.4322.2300; ASP.NET Version:1.1.4322.2300
Open the IIS MMC plug in, go to the reports and report server virtual directories, right-click and select properties. Go to the ASP.Net tab. ensure the ASP.Net version is set to 2.0
-Lukasz
This posting is provided "AS IS" with no warranties, and confers no rights.
Hi - when I do this it comes back with this error message?
Failed to map the path '/Reports/App_GlobalResources/'
|||Use regmon and filemon to check if there are any "access denied" errors on ASPNET user. Grant access if you see any error.|||You can use the aspnet_regiis.exe tool with the "-ga" parameter to grant access to the Web Service account listed in the report server configuration tool or to the application pool idenity assigned to the report manager/report server virtual directory.
-Lukasz
|||This was the solution to my problem. If you don't have the ASP.Net tab like me, go to %SYSTEMROOT%\Microsoft.NET\Framework\<Version> and use aspnet_regiis.exe -s <Path to your Reports-VDir>. If everything is default: aspnet_regiis.exe -s W3SVC/1/ROOT/Reports will do it.
Report Manager error
When I try to start report manager, I get the following error message. What do I need to do?
Server Error in '/Reports' Application.
Parser Error
Description: An error occurred during the parsing of a resource required to service this request. Please review the following specific parse error details and modify your source file appropriately.
Parser Error Message: Could not load type 'Microsoft.ReportingServices.UI.GlobalApp'.
Source Error:
|
Source File: C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportManager\global.asax Line: 1
Version Information: Microsoft .NET Framework Version:1.1.4322.2300; ASP.NET Version:1.1.4322.2300
Open the IIS MMC plug in, go to the reports and report server virtual directories, right-click and select properties. Go to the ASP.Net tab. ensure the ASP.Net version is set to 2.0
-Lukasz
This posting is provided "AS IS" with no warranties, and confers no rights.
Hi - when I do this it comes back with this error message?
Failed to map the path '/Reports/App_GlobalResources/'
|||Use regmon and filemon to check if there are any "access denied" errors on ASPNET user. Grant access if you see any error.|||You can use the aspnet_regiis.exe tool with the "-ga" parameter to grant access to the Web Service account listed in the report server configuration tool or to the application pool idenity assigned to the report manager/report server virtual directory.
-Lukasz
|||This was the solution to my problem. If you don't have the ASP.Net tab like me, go to %SYSTEMROOT%\Microsoft.NET\Framework\<Version> and use aspnet_regiis.exe -s <Path to your Reports-VDir>. If everything is default: aspnet_regiis.exe -s W3SVC/1/ROOT/Reports will do it.
Report Manager error
When I try to start report manager, I get the following error message. What do I need to do?
Server Error in '/Reports' Application.
Parser Error
Description: An error occurred during the parsing of a resource required to service this request. Please review the following specific parse error details and modify your source file appropriately.
Parser Error Message: Could not load type 'Microsoft.ReportingServices.UI.GlobalApp'.
Source Error:
|
Source File: C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportManager\global.asax Line: 1
Version Information: Microsoft .NET Framework Version:1.1.4322.2300; ASP.NET Version:1.1.4322.2300
Open the IIS MMC plug in, go to the reports and report server virtual directories, right-click and select properties. Go to the ASP.Net tab. ensure the ASP.Net version is set to 2.0
-Lukasz
This posting is provided "AS IS" with no warranties, and confers no rights.
Hi - when I do this it comes back with this error message?
Failed to map the path '/Reports/App_GlobalResources/'
|||Use regmon and filemon to check if there are any "access denied" errors on ASPNET user. Grant access if you see any error.|||You can use the aspnet_regiis.exe tool with the "-ga" parameter to grant access to the Web Service account listed in the report server configuration tool or to the application pool idenity assigned to the report manager/report server virtual directory.
-Lukasz
|||This was the solution to my problem. If you don't have the ASP.Net tab like me, go to %SYSTEMROOT%\Microsoft.NET\Framework\<Version> and use aspnet_regiis.exe -s <Path to your Reports-VDir>. If everything is default: aspnet_regiis.exe -s W3SVC/1/ROOT/Reports will do it.
Wednesday, March 7, 2012
'Report Is Being Generated' Message and Graphic not Displaying
Hello,
I am using ReportViewer in a Web Page with a Server Report and
Asyncrendering is turned on. The report displays correctly; however, the
'Report Is Being Generated' message and graphic do not display when the
report is loading.
It works fine in Report Manager. It is a big problem because the user can
not tell when a report is loading and they keep pressing the 'View Report'
button.
Any suggestions?
Thanks.Hello,
Have you tried this on other develop machine to develop a new report for
test?
Have you use the impersonate in your ASP.NET web application?
If so, what's the permission you have on the report server?
Also, please add your report server to the trust site in the IE and try to
set the security level to low to have a try.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||> Have you tried this on other develop machine to develop a new report for
> test?
No.
> Have you use the impersonate in your ASP.NET web application?
No.
>Also, please add your report server to the trust site in the IE and try to
> set the security level to low to have a try.
I tried this and it didn't work
What do you suggest based on these answers?
Thank
"Wei Lu [MSFT]" wrote:
> Hello,
> Have you tried this on other develop machine to develop a new report for
> test?
> Have you use the impersonate in your ASP.NET web application?
> If so, what's the permission you have on the report server?
> Also, please add your report server to the trust site in the IE and try to
> set the security level to low to have a try.
> Sincerely,
> Wei Lu
> Microsoft Online Community Support
> ==================================================> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ==================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
>|||Hello,
I suggest you to check the develop this report on another machine to check
whether this issue appeared or not.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Hello,
Did you use any User Control to hold the ReportViewer? If you put your
ReportViewer to a single aspx page, does this issue appeared?
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Hello
I find some user got the similar issue as you but I did not find any
solution since I could not reproduce this issue on my side.
Could you try to generate a simple sample which could reproduce your issue
and send it to me?
To reach me, please remove the ONLINE in my email address.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi ,
How is everything going? Please feel free to let me know if you need any
assistance.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.
I am using ReportViewer in a Web Page with a Server Report and
Asyncrendering is turned on. The report displays correctly; however, the
'Report Is Being Generated' message and graphic do not display when the
report is loading.
It works fine in Report Manager. It is a big problem because the user can
not tell when a report is loading and they keep pressing the 'View Report'
button.
Any suggestions?
Thanks.Hello,
Have you tried this on other develop machine to develop a new report for
test?
Have you use the impersonate in your ASP.NET web application?
If so, what's the permission you have on the report server?
Also, please add your report server to the trust site in the IE and try to
set the security level to low to have a try.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||> Have you tried this on other develop machine to develop a new report for
> test?
No.
> Have you use the impersonate in your ASP.NET web application?
No.
>Also, please add your report server to the trust site in the IE and try to
> set the security level to low to have a try.
I tried this and it didn't work
What do you suggest based on these answers?
Thank
"Wei Lu [MSFT]" wrote:
> Hello,
> Have you tried this on other develop machine to develop a new report for
> test?
> Have you use the impersonate in your ASP.NET web application?
> If so, what's the permission you have on the report server?
> Also, please add your report server to the trust site in the IE and try to
> set the security level to low to have a try.
> Sincerely,
> Wei Lu
> Microsoft Online Community Support
> ==================================================> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ==================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
>|||Hello,
I suggest you to check the develop this report on another machine to check
whether this issue appeared or not.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Hello,
Did you use any User Control to hold the ReportViewer? If you put your
ReportViewer to a single aspx page, does this issue appeared?
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Hello
I find some user got the similar issue as you but I did not find any
solution since I could not reproduce this issue on my side.
Could you try to generate a simple sample which could reproduce your issue
and send it to me?
To reach me, please remove the ONLINE in my email address.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi ,
How is everything going? Please feel free to let me know if you need any
assistance.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to:
Posts (Atom)