RIA startup issue - xpa 4.8


Tom Worthen
 

We are running xpa 4.7 in our production environment and are working on moving to xpa 4.8. We have RIA for some Back Office/in-house processing. I have installed xpa 4.8 a long side xpa 4.7 on a dev server. I changed the IIS setting to use xpa 4.8 instead of xpa 4.7. The application starts in the broker and when I execute the link from a browser to load the RIA client the calls show up in the broker as well. Initially when I ran it I got a message “Data at the root level is invalid, Line 1, position 1.” I found in this group a message from 2019, #190826, that mentioned clearing the cache from %userprofile%\AppData\Local\Apps\2.0 and %userprofile%\AppData\Local\temp where the folder name starts with mgria. I cleared both of those and now when I do the install and it attempts to run the application I am getting this message:  

 

I have recreated the ecf and deployed it. That includes copying the folder over to the web server. It does not change this message.

 

Any ideas would be appreciated.

 

Thanks,

Tom

 


Tim Downie
 

Does the toolkit run RIA programs on the server you have this installation?


From: main@magicu-l.groups.io <main@magicu-l.groups.io> on behalf of Tom Worthen <tworthen@...>
Sent: Wednesday, 5 October 2022 2:17 AM
To: main@magicu-l.groups.io <main@magicu-l.groups.io>
Subject: [magicu-l] RIA startup issue - xpa 4.8
 

We are running xpa 4.7 in our production environment and are working on moving to xpa 4.8. We have RIA for some Back Office/in-house processing. I have installed xpa 4.8 a long side xpa 4.7 on a dev server. I changed the IIS setting to use xpa 4.8 instead of xpa 4.7. The application starts in the broker and when I execute the link from a browser to load the RIA client the calls show up in the broker as well. Initially when I ran it I got a message “Data at the root level is invalid, Line 1, position 1.” I found in this group a message from 2019, #190826, that mentioned clearing the cache from %userprofile%\AppData\Local\Apps\2.0 and %userprofile%\AppData\Local\temp where the folder name starts with mgria. I cleared both of those and now when I do the install and it attempts to run the application I am getting this message:  

 

I have recreated the ecf and deployed it. That includes copying the folder over to the web server. It does not change this message.

 

Any ideas would be appreciated.

 

Thanks,

Tom

 


Tom Worthen
 

We don’t typically run the studio on the RIA server but since you asked, I set it up and ran it. Yes, the programs run on the server.

 

Still get the same error if I try to start RIA.

 

From: main@magicu-l.groups.io [mailto:main@magicu-l.groups.io] On Behalf Of Tim Downie
Sent: Tuesday, October 04, 2022 7:21 PM
To: main@magicu-l.groups.io
Subject: Re: [magicu-l] RIA startup issue - xpa 4.8

 

Does the toolkit run RIA programs on the server you have this installation?

 


From: main@magicu-l.groups.io <main@magicu-l.groups.io> on behalf of Tom Worthen <tworthen@...>
Sent: Wednesday, 5 October 2022 2:17 AM
To: main@magicu-l.groups.io <main@magicu-l.groups.io>
Subject: [magicu-l] RIA startup issue - xpa 4.8

 

We are running xpa 4.7 in our production environment and are working on moving to xpa 4.8. We have RIA for some Back Office/in-house processing. I have installed xpa 4.8 a long side xpa 4.7 on a dev server. I changed the IIS setting to use xpa 4.8 instead of xpa 4.7. The application starts in the broker and when I execute the link from a browser to load the RIA client the calls show up in the broker as well. Initially when I ran it I got a message “Data at the root level is invalid, Line 1, position 1.” I found in this group a message from 2019, #190826, that mentioned clearing the cache from %userprofile%\AppData\Local\Apps\2.0 and %userprofile%\AppData\Local\temp where the folder name starts with mgria. I cleared both of those and now when I do the install and it attempts to run the application I am getting this message:  

 

I have recreated the ecf and deployed it. That includes copying the folder over to the web server. It does not change this message.

 

Any ideas would be appreciated.

 

Thanks,

Tom