Giving Statements "Internal Server Error"

Question

0

Giving Statements "Internal Server Error"

Dave Brown posted 8 Years Ago

I have pointed the statement generator to our Rock URL & added a custom logo. When I attempt to navigate "step 1," this is the result...

0
- Dave Brown replied 8 Years Ago
ADDITIONAL INFORMATION ("Edit Question" button does not actually allow me to edit the question):

I asked our IT consultant to look at this issue as well. Here is the full request provided to him:

"I have the following scenario: 1. Rock contribution statements are generated through an application that is downloaded from Rock's "Power Tools" (ADMIN TOOLS | POWER TOOLS). 2. Prior to "Go Live" in September, I "pointed" the software to the sandbox [ http://rmsdev.lakeside.local/ ] and successfully generated statements from that source. Today, I can still successfully pull statements from the sandbox. 3. Pointing the software to the current URLs [ http://rockadmin.lakesidechristian.com/ OR https://rockadmin.lakesidechristian.com/ ] results in a software response of "INTERNAL SERVER ERROR."

He provided the following reply:

"[I] was able to reproduce, but couldn't figure out any way to get the statement builder into a debug mode to see any detailed error messages. The fact that it's allowing login, but then blows up when querying the list seems very odd. That means it can talk to the server to authenticate, but not to run that command. Make sure you include that information in your bug report. If you have found any way to put it into debug mode pass it along to me and maybe I can be of further help, but I don't see anything wrong with the webserver configuration."

Looking forward to this forum's expertise as the reporting deadline is looming.
Edit Answer

ADDITIONAL INFORMATION ("Edit Question" button does not actually allow me to edit the question): I asked our IT consultant to look at this issue as well.  Here is the full request provided to him: <pre> "I have the following scenario: 1. Rock contribution statements are generated through an application that is downloaded from Rock's "Power Tools" (ADMIN TOOLS | POWER TOOLS). 2. Prior to "Go Live" in September, I "pointed" the software to the sandbox [ http://rmsdev.lakeside.local/ ] and successfully generated statements from that source. Today, I can still successfully pull statements from the sandbox. 3. Pointing the software to the current URLs [ http://rockadmin.lakesidechristian.com/ OR https://rockadmin.lakesidechristian.com/ ] results in a software response of "INTERNAL SERVER ERROR."</pre> He provided the following reply: <pre> "[I] was able to reproduce, but couldn't figure out any way to get the statement builder into a debug mode to see any detailed error messages. The fact that it's allowing login, but then blows up when querying the list seems very odd. That means it can talk to the server to authenticate, but not to run that command. Make sure you include that information in your bug report. If you have found any way to put it into debug mode pass it along to me and maybe I can be of further help, but I don't see anything wrong with the webserver configuration."</pre> Looking forward to this forum's expertise as the reporting deadline is looming.
ADDITIONAL INFORMATION ("Edit Question" button does not actually allow me to edit the question): I asked our IT consultant to look at this issue as well.  Here is the full request provided to him: <pre> "I have the following scenario: 1. Rock contribution statements are generated through an application that is downloaded from Rock's "Power Tools" (ADMIN TOOLS | POWER TOOLS). 2. Prior to "Go Live" in September, I "pointed" the software to the sandbox [ http://rmsdev.lakeside.local/ ] and successfully generated statements from that source. Today, I can still successfully pull statements from the sandbox. 3. Pointing the software to the current URLs [ http://rockadmin.lakesidechristian.com/ OR https://rockadmin.lakesidechristian.com/ ] results in a software response of "INTERNAL SERVER ERROR."</pre> He provided the following reply: <pre> "[I] was able to reproduce, but couldn't figure out any way to get the statement builder into a debug mode to see any detailed error messages. The fact that it's allowing login, but then blows up when querying the list seems very odd. That means it can talk to the server to authenticate, but not to run that command. Make sure you include that information in your bug report. If you have found any way to put it into debug mode pass it along to me and maybe I can be of further help, but I don't see anything wrong with the webserver configuration."</pre> Looking forward to this forum's expertise as the reporting deadline is looming.
ADDITIONAL INFORMATION ("Edit Question" button does not actually allow me to edit the question): I asked our IT consultant to look at this issue as well.  Here is the full request provided to him: <pre> "I have the following scenario: 1. Rock contribution statements are generated through an application that is downloaded from Rock's "Power Tools" (ADMIN TOOLS | POWER TOOLS). 2. Prior to "Go Live" in September, I "pointed" the software to the sandbox [ http://rmsdev.lakeside.local/ ] and successfully generated statements from that source. Today, I can still successfully pull statements from the sandbox. 3. Pointing the software to the current URLs [ http://rockadmin.lakesidechristian.com/ OR https://rockadmin.lakesidechristian.com/ ] results in a software response of "INTERNAL SERVER ERROR."</pre> He provided the following reply: <pre> "[I] was able to reproduce, but couldn't figure out any way to get the statement builder into a debug mode to see any detailed error messages. The fact that it's allowing login, but then blows up when querying the list seems very odd. That means it can talk to the server to authenticate, but not to run that command. Make sure you include that information in your bug report. If you have found any way to put it into debug mode pass it along to me and maybe I can be of further help, but I don't see anything wrong with the webserver configuration."</pre> Looking forward to this forum's expertise as the reporting deadline is looming.
Save Cancel
0
- David Leigh replied 8 Years Ago
What version of Rock are you running in the sandbox and in the live system - are they the same?
You can check the version by clicking the info icon on the Admin toolbar.

Also, are you running the same instance of the statement generator (ie. the same .exe) against both Rock instances?
Edit Answer

What version of Rock are you running in the sandbox and in the live system - are they the same? You can check the version by clicking the info icon on the Admin toolbar. Also, are you running the same instance of the statement generator (ie. the same .exe) against both Rock instances?  
What version of Rock are you running in the sandbox and in the live system - are they the same? You can check the version by clicking the info icon on the Admin toolbar. Also, are you running the same instance of the statement generator (ie. the same .exe) against both Rock instances?  
What version of Rock are you running in the sandbox and in the live system - are they the same? You can check the version by clicking the info icon on the Admin toolbar. Also, are you running the same instance of the statement generator (ie. the same .exe) against both Rock instances?  
Save Cancel
0
- Dave Brown replied 8 Years Ago
Sandbox: Rock McKinley 3.2

Production: Rock McKinley 3.4

and yes, I'm running the same executable file for both instances.
Edit Answer

Sandbox: Rock McKinley 3.2 Production: Rock McKinley 3.4 and yes, I'm running the same executable file for both instances.
Sandbox: Rock McKinley 3.2 Production: Rock McKinley 3.4 and yes, I'm running the same executable file for both instances.
Sandbox: Rock McKinley 3.2 Production: Rock McKinley 3.4 and yes, I'm running the same executable file for both instances.
Save Cancel
0
- David Leigh replied 8 Years Ago
Ok, that might be the cause of the problem.

Try downloading the Statement Generator again from your Rock production site (v3.4) and use that version instead.
The Statement Generator has had some updates since v3.2, so you need to use the version that is compatible with 3.4.
Edit Answer

Ok, that might be the cause of the problem. Try downloading the Statement Generator again from your Rock production site (v3.4) and use that version instead. The Statement Generator has had some updates since v3.2, so you need to use the version that is compatible with 3.4.
Ok, that might be the cause of the problem. Try downloading the Statement Generator again from your Rock production site (v3.4) and use that version instead. The Statement Generator has had some updates since v3.2, so you need to use the version that is compatible with 3.4.
Ok, that might be the cause of the problem. Try downloading the Statement Generator again from your Rock production site (v3.4) and use that version instead. The Statement Generator has had some updates since v3.2, so you need to use the version that is compatible with 3.4.
Save Cancel
0
- Dave Brown replied 8 Years Ago
Nope, I get the exact same error after deleting the legacy Statement Generator and installing from our current production site (I repeated the delete-and-install twice to be certain).
Edit Answer

Nope, I get the exact same error after deleting the legacy Statement Generator and installing from our current production site (I repeated the delete-and-install twice to be certain).
Nope, I get the exact same error after deleting the legacy Statement Generator and installing from our current production site (I repeated the delete-and-install twice to be certain).
Nope, I get the exact same error after deleting the legacy Statement Generator and installing from our current production site (I repeated the delete-and-install twice to be certain).
Save Cancel
0
- Dave Brown replied 8 Years Ago
Bump...URGENT!!!!
Edit Answer

Bump...URGENT!!!!
Bump...URGENT!!!!
Bump...URGENT!!!!
Save Cancel
0
- Jon Edmiston replied 8 Years Ago
Couple of things to look at:

Do you see anything in your server exception log ('Admin Tools > System Settings > Exception List').

You could try to update to v4 (it's shipping next week). Might try it on your sandbox first. To do so you'd need to follow these instructions: http://www.rockrms.com/page/473?Item=91

Keep me posted. I'll follow this Q&A over the weekend.
Edit Answer

Couple of things to look at: <ol> <li>Do you see anything in your server exception log ('Admin Tools > System Settings > Exception List').</li> <li>You could try to update to v4 (it's shipping next week). Might try it on your sandbox first. To do so you'd need to follow these instructions: http://www.rockrms.com/page/473?Item=91</li> </ol> Keep me posted. I'll follow this Q&A over the weekend.
Couple of things to look at: <ol> <li>Do you see anything in your server exception log ('Admin Tools > System Settings > Exception List').</li> <li>You could try to update to v4 (it's shipping next week). Might try it on your sandbox first. To do so you'd need to follow these instructions: http://www.rockrms.com/page/473?Item=91</li> </ol> Keep me posted. I'll follow this Q&A over the weekend.
Couple of things to look at: <ol> <li>Do you see anything in your server exception log ('Admin Tools > System Settings > Exception List').</li> <li>You could try to update to v4 (it's shipping next week). Might try it on your sandbox first. To do so you'd need to follow these instructions: http://www.rockrms.com/page/473?Item=91</li> </ol> Keep me posted. I'll follow this Q&A over the weekend.
Save Cancel
Jon Edmiston

8 years ago

You might also triple check this is the version of the app you're using for 3.x http://storage.rockrms.com/externalapplications/sparkdevnetwork/statementgenerator/1.3.0/statementgenerator.exe
0
- Dave Brown replied 8 Years Ago
Here is the exception:

Newtonsoft.Json.JsonSerializationException

Self referencing loop detected with type 'Rock.Model.FinancialAccount'. Path '[4].ChildAccounts'.

We show the "Everything is shipshape" [McKinley 3.4] under Home | General Settings | Rock Update
Edit Answer

Here is the exception: <div>Newtonsoft.Json.JsonSerializationException</div> <div> <table class="grid-table table table-bordered table-striped table-hover" id="ctl00_main_ctl23_ctl01_ctl06_gExceptionOccurrences" style="box-sizing: border-box; border-collapse: collapse; border-spacing: 0px; width: 1304.44px; max-width: 100%; margin-bottom: 0px; color: rgb(106, 106, 106); font-family: OpenSans, 'Helvetica Neue', Helvetica, Arial, sans-serif; font-size: 14px; line-height: 22.2222px;"> <tbody style="box-sizing: border-box;"> <tr align="left" data-original-title="" data-row-index="0" datakey="2665" style="box-sizing: border-box;" title=""> <td class="grid-select-cell" data-priority="1" style="box-sizing: border-box; padding: 12px; cursor: pointer; line-height: 1.42857; vertical-align: top; background-color: rgb(249, 249, 249);">Self referencing loop detected with type 'Rock.Model.FinancialAccount'. Path '[4].ChildAccounts'.</td> </tr> </tbody> </table> We show the "Everything is shipshape" [McKinley 3.4] under <a href="https://rockadmin.lakesidechristian.com/page/12" style="line-height: 1.6em; box-sizing: border-box; color: rgb(49, 96, 120); text-decoration: none; outline: 0px; background: transparent;">Home</a> | <a href="https://rockadmin.lakesidechristian.com/page/77" style="line-height: 1.6em; box-sizing: border-box; color: rgb(71, 139, 174); text-decoration: none; background: transparent;">General Settings</a> | Rock Update </div>
Here is the exception: <div>Newtonsoft.Json.JsonSerializationException</div> <div> <table class="grid-table table table-bordered table-striped table-hover" id="ctl00_main_ctl23_ctl01_ctl06_gExceptionOccurrences" style="box-sizing: border-box; border-collapse: collapse; border-spacing: 0px; width: 1304.44px; max-width: 100%; margin-bottom: 0px; color: rgb(106, 106, 106); font-family: OpenSans, 'Helvetica Neue', Helvetica, Arial, sans-serif; font-size: 14px; line-height: 22.2222px;"> <tbody style="box-sizing: border-box;"> <tr align="left" data-original-title="" data-row-index="0" datakey="2665" style="box-sizing: border-box;" title=""> <td class="grid-select-cell" data-priority="1" style="box-sizing: border-box; padding: 12px; cursor: pointer; line-height: 1.42857; vertical-align: top; background-color: rgb(249, 249, 249);">Self referencing loop detected with type 'Rock.Model.FinancialAccount'. Path '[4].ChildAccounts'.</td> </tr> </tbody> </table> We show the "Everything is shipshape" [McKinley 3.4] under <a href="https://rockadmin.lakesidechristian.com/page/12" style="line-height: 1.6em; box-sizing: border-box; color: rgb(49, 96, 120); text-decoration: none; outline: 0px; background: transparent;">Home</a> | <a href="https://rockadmin.lakesidechristian.com/page/77" style="line-height: 1.6em; box-sizing: border-box; color: rgb(71, 139, 174); text-decoration: none; background: transparent;">General Settings</a> | Rock Update </div>
Here is the exception: <div>Newtonsoft.Json.JsonSerializationException</div> <div> <table class="grid-table table table-bordered table-striped table-hover" id="ctl00_main_ctl23_ctl01_ctl06_gExceptionOccurrences" style="box-sizing: border-box; border-collapse: collapse; border-spacing: 0px; width: 1304.44px; max-width: 100%; margin-bottom: 0px; color: rgb(106, 106, 106); font-family: OpenSans, 'Helvetica Neue', Helvetica, Arial, sans-serif; font-size: 14px; line-height: 22.2222px;"> <tbody style="box-sizing: border-box;"> <tr align="left" data-original-title="" data-row-index="0" datakey="2665" style="box-sizing: border-box;" title=""> <td class="grid-select-cell" data-priority="1" style="box-sizing: border-box; padding: 12px; cursor: pointer; line-height: 1.42857; vertical-align: top; background-color: rgb(249, 249, 249);">Self referencing loop detected with type 'Rock.Model.FinancialAccount'. Path '[4].ChildAccounts'.</td> </tr> </tbody> </table> We show the "Everything is shipshape" [McKinley 3.4] under <a href="https://rockadmin.lakesidechristian.com/page/12" style="line-height: 1.6em; box-sizing: border-box; color: rgb(49, 96, 120); text-decoration: none; outline: 0px; background: transparent;">Home</a> | <a href="https://rockadmin.lakesidechristian.com/page/77" style="line-height: 1.6em; box-sizing: border-box; color: rgb(71, 139, 174); text-decoration: none; background: transparent;">General Settings</a> | Rock Update </div>
Save Cancel
Jon Edmiston

8 years ago

Ah OK, can you send me the results of this query (you can run it under 'Admin Tools > Power Tools > SQL Command'):

SELECT
*
FROM
[FinancialAccount]

If you could export that to Excel and email it to me jon(at)sparkdevnetwork.org I can send you a SQL fix. Looks like you might have an endless parent/child loop in your account structure.

Jon Edmiston · Accepted Answer · 2016-01-19T15:04-07:00

0

Jon Edmiston replied 8 Years Ago

Looks like the 'Memorial' account has its parent account set to itself. This is causing a loop in the SQL. You can try changing it in the UI or use this SQL:

UPDATE [FinancialAccount]

    SET [ParentAccountId] = NULL

    WHERE [Id] = 5

If you do this in the 'SQL Command' tool be sure to flip the 'Selection Query' to 'No'

Question

0

Giving Statements "Internal Server Error"

0

0

0

0

0

0

0

0

0