Important Update: Archer Community Scheduled Maintenance on November 23–24 - New Community Launching Soon! Learn More..
2020-03-11 04:49 AM
Hi,
We recently upgraded our Archer environment from 6.3 to 6.6 p6 and after upgrade one of our custom code is not working as expected. Basically when we are clicking the code, its taking to the home page of Archer instead of selecting relevant controls which the code is supposed to do.
I know RSA had changed the way certain protocols work after 6.3 like you can no longer find record id in the URL.
Any advise on this would be greatly appreciated.
Thanks
2020-03-13 01:34 AM
Thanks David,
The link didn't work unfortunately.
Thanks
Rohit
2020-03-13 07:46 AM
When you say that the wfrmLogin.aspx is on the same IIS/Webserver. Is the file actually in Archer's folder or a completely different site in IIS?
In 6.4 URL Routing Changes were made and you might be running into that if the page is located in the same folder as Archer. https://community.rsa.com/community/products/archer-grc/archer-customer-partner-community/blog/2018/04/25/rsa-archer-64-url-routing-changes
Advisory Consultant
2020-03-13 08:26 AM
Hi David,
The RSA Archer folder is in E:\APPS\RSA_Archer
While the custom app is in E:\APPS\CustomCode folder.
Do you think this should not be the case?
Also, during installation, we chose website as default website and destination directory as custom_app in IIS application and not websites' default application?
We are really stuck and any help here would be highly appreciated.
Thanks so much, best regards
2020-03-13 09:03 AM
Are these two different directories configured as different applications in IIS with different application pools?
The RSA Archer folder is in E:\APPS\RSA_Archer
While the custom app is in E:\APPS\CustomCode folder.
Also, during installation, we chose website as default website and destination directory as custom_app in IIS application and not websites' default application?
I'm not understanding what you're asking.
When installing Archer, you can select the default IIS application or select a different IIS application to install Archer in.
Ideally, your web application should be installed in a different IIS application from Archer's with a different application pool.
Advisory Consultant
2020-03-14 04:40 AM
Ok,
We are also getting below error in cutom_app directory in website -
Version:1.0 StartHTML:000000204 EndHTML:000001746 StartFragment:000001591 EndFragment:000001661 StartSelection:000001591 EndSelection:000001661 SourceURL:https://localhost/custom_app/Default.aspxParser Error
<AT:ArcherRadScriptManager ID="scriptManager" runat="server" /> |
2020-03-17 08:50 AM
Rohit, might be the time to open a ticket with support on this.
Advisory Consultant
2020-03-17 12:01 PM
Yes we did that already long back, but you know RSA support does not provide support on custom code
2020-03-17 01:56 PM
Correct, if this is a home-grown application or custom object, support won't support it.
If this in relationship to Archer not working properly (sans your custom code), you need support to help resolve the issue.
Advisory Consultant
2020-03-31 11:17 AM
Hi David,
As per the post, the URL to any record can be fetched from the Email icon. Below is the URL fetched:
https://URL//default.aspx?requestUrl=..%2fGenericContent%2fRecord.aspx%3fid%3dxxxxx%26moduleId%3dxxx
But our custom code needs to navigate a Logon page that is placed in the same folder as Generic Content(folder in the above URL containing record.aspx)
And we have tried all of the below URL formations but all of them give an Unexpected error.
2020-04-02 10:06 AM
HI David Petty,
Hope you are doing good. Just wanted to check if you got sometime to look on the question above.