nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Incorporating New SQL Server 2005 Try and Catch statements into Live and WebReports

Kristy_Shen

Hi:I currently have a livereport that calls a stored procedure. I've put in Try and Catch statements in the sp because we've just recently migrated from sql server 2000 to 2005. I created some data that would cause a primary key voilation error when the sp is execute. The try an catch will output the appropriate error messages for this.When I run the stored proc that has the try and catch statements directly in SQL server mgmt studio, the error gets printed out correctly. When I run it in the livereport, it is also fine. However, when I run the webreport that has the livereport set as its datasource, I get "invalid tag" errors all over my page. Can someone please help me with this? How can I get the webreport to output the error correctly when try and catch is used? Do I have to use special tags?

Find more posts tagged with

Comments

Bhupinder_Singh

Message from Bhupinder Singh <bsingh@opentext.com> via eLink

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">eLink

Can you provide a screen shot of the LiveReport error as well as a screen shot of the WebReport output? A colleague of mine might be able to suggest some kind of workaround once we have those.

- Bhupinder----------------------------------------------
Bhupinder Singh, B.Math, B.Ed.
Senior Systems Analyst, Information Technology
Open Text, Waterloo, Ontario, Canada
----------------------------------------------

From: eLink Discussion: Livelink LiveReports Discussion [mailto:livereportsdiscussion@elinkkc.opentext.com]
Sent: Thursday, August 21, 2008 2:41 PM
To: eLink Recipient
Subject: Incorporating New SQL Server 2005 Try and Catch statements into Live and WebReports

Incorporating New SQL Server 2005 Try and Catch statements into Live and WebReports

Posted by kristyshen (Shen, Kristy) on 08/21/2008 02:36 PM

Hi:

I currently have a livereport that calls a stored procedure. I've put in Try and Catch statements in the sp because we've just recently migrated from sql server 2000 to 2005.

I created some data that would cause a primary key voilation error when the sp is execute. The try an catch will output the appropriate error messages for this.

When I run the stored proc that has the try and catch statements directly in SQL server mgmt studio, the error gets printed out correctly. When I run it in the livereport, it is also fine.

However, when I run the webreport that has the livereport set as its datasource, I get "invalid tag" errors all over my page.

Can someone please help me with this? How can I get the webreport to output the error correctly when try and catch is used? Do I have to use special tags?

Kristy_Shen

Hi Bhupinder:Thanks for your help! I've attached the requested data.

Bhupinder_Singh

Message from Bhupinder Singh <bsingh@opentext.com> via eLink

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">eLink

Based on your description of the problem and the screenshots, my colleague indicates:

"It appears that when there is an error in the SP procedure, rather than throwing a normal LR error, it is returning a completely different table than the one the WebReport was originally designed for. The WebReport sees valid data so it goes ahead as usual. [It's] kind of like the WebReport was designed for one specific table but under certain situations, the table can be completely different. <?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" />

I would suggest a couple of things:

a) Ideally the SP shouldn’t generate this error table, and or could use an existing column in the normal table to specify an error. Ideally there should be a way to [allow] the SP to throw a normal error.

b) Depending on what the intended output is, you could use either:

a. INCLUDEIF logic (to block [any] rows that don’t have valid data in one of the normal columns)

b. _IF/ENDIF to select different code depending on which table is being used

c. DECODE sub-tag for each column tag so that if Invalid tag is being returned, you can convert it to some default value

In a/b/c you should also use the [LL_WEBREPORT_SUPPRESSERRORLOG /] to prevent the error messages at the bottom. This is fairly normal for reports that are deployed on production systems."

- Bhupinder

----------------------------------------------
Bhupinder Singh, B.Math, B.Ed.
Senior Systems Analyst, Information Technology
Open Text, Waterloo, Ontario, Canada
----------------------------------------------

From: eLink Discussion: Livelink LiveReports Discussion [mailto:livereportsdiscussion@elinkkc.opentext.com]
Sent: Tuesday, August 26, 2008 10:37 AM
To: eLink Recipient
Subject: RE Incorporating New SQL Server 2005 Try and Catch statements into Live and WebReports

RE Incorporating New SQL Server 2005 Try and Catch statements into Live and WebReports		Posted by kristyshen (Shen, Kristy) on 08/26/2008 10:35 AM
In reply to: RE Incorporating New SQL Server 2005 Try and Catch statements into Live and WebReports		Posted by bsingh (Singh, Bhupinder) on 08/25/2008 11:04 AM

Hi Bhupinder:

Thanks for your help! I've attached the requested data.

Kristy_Shen

Hi Bhupinder:Thanks for you response. It's not that there's an error in the sp, it's the fact that I've added try and catch statements. So the error is generated because I deliberately choose a scenario where there is a primary key voilation and I had the catch statement catch this error and print on the information that is shown in the livereport. I was hoping that I could use a tag in the webreport to handle this case and print out the same output as the livereport. For point b) _IF/ENDIF to select different code depending on which table is being usedI'm not sure I understand what you mean by this. The webreport tags I'm currently using just gets the data from that specific column from the result set. However, if the error occurs, that column doesn't exist. So how do I detect that the column doesn't exist because the error info is being printed?

Greg_Petti

Message from Greg Petti <gpetti@opentext.com> via eLink

eLink

Hi,

You could just use something like this:

[LL_WEBREPORT_IF "[LL_REPTAG=SBU/]" == "* Invalid Tag Error *" /]

[LL_WEBREPORT_ELSE /]

[LL_WEBREPORT_ENDIF /]

From: eLink Discussion:Livelink LiveReports Discussion[mailto:livereportsdiscussion@elinkkc.opentext.com]
Sent: August 26, 2008 12:03 PM
To: eLink Recipient
Subject: RE Incorporating New SQL Server 2005 Try and Catch statementsinto Live and WebReports

RE Incorporating New SQL Server 2005 Try and Catch statements into Live and WebReports		Posted by kristyshen (Shen, Kristy) on 08/26/2008 02:00 PM
In reply to: RE RE Incorporating New SQL Server 2005 Try and Catch statements into Live and WebReports		Posted by bsingh (Singh, Bhupinder) on 08/26/2008 01:15 PM

Hi Bhupinder:

Thanks for you response. It's not that there's an error in the sp, it's the fact that I've added try and catch statements. So the error is generated because I deliberately choose a scenario where there is a primary key voilation and I had the catch statement catch this error and print on the information that is shown in the livereport.

I was hoping that I could use a tag in the webreport to handle this case and print out the same output as the livereport.

For point b) _IF/ENDIF to select different code depending on which table is being used

I'm not sure I understand what you mean by this. The webreport tags I'm currently using just gets the data from that specific column from the result set. However, if the error occurs, that column doesn't exist. So how do I detect that the column doesn't exist because the error info is being printed?

[To reply to this thread, use your normal E-mail reply function.]
Topic:	Incorporating New SQL Server 2005 Try and Catch statements into Live and WebReports
Discussion:	Livelink LiveReports Discussion
Livelink Server:	knowledge-wlweb01

To Unsubscribe from this Discussion, send an e-mail to unsubscribe.livereportsdiscussion@elinkkc.opentext.com.

Kristy_Shen

Hi Greg:Thanks for your suggestion! I will try it out. Kristy