This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Flexera Community
- :
- AdminStudio
- :
- AdminStudio Forum
- :
- ASPX error in Reports in latest version 12.0.0.0. Still.
Subscribe
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Sep 23, 2013
01:12 PM
ASPX error in Reports in latest version 12.0.0.0. Still.
I deployed a new Windows 2012 server to run AES/WorkflowManager. It's all fresh, not an upgrade over existing code.
When users go to http:///ReportCenter/PackageReport.aspx they get an ASPX error: "Control 'ScriptManager1' of type 'ScriptManager' must be placed inside a form tag with runat=server"
This code: " " must be INSIDE the form tag, not preceding it. I have had to fix this same error on previous versions too.
Flexera please fix your code. Customers should not have to QA and fix your products.
When users go to http://
This code: "
Flexera please fix your code. Customers should not have to QA and fix your products.
This thread has been automatically locked due to inactivity.
To continue the discussion, please start a new thread.
1 Reply
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Sep 23, 2013
09:07 PM
Hi,
The following kb addresses this issue --> http://kb.flexerasoftware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=Q211340&sliceId=1&docTypeID=DT_ERRDOC_1_1&dialogID=158185083&stateId=0%200%20158183210.
This issue is also being tracked under a Work-Order by the Engineering team and will be addressed soon.
Thanks!
The following kb addresses this issue --> http://kb.flexerasoftware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=Q211340&sliceId=1&docTypeID=DT_ERRDOC_1_1&dialogID=158185083&stateId=0%200%20158183210.
This issue is also being tracked under a Work-Order by the Engineering team and will be addressed soon.
Thanks!
