Can someone explain why this error occurs every time I have to log back in after a customization is published?
If I delete the Acumatica instance and re-create it, linking to the existing database - it then works fine. If it times out and I have to log in again, I get this error:
Description: An error occurred during the compilation of a resource required to service this request. Please review the following specific error details and modify your source code appropriately.
Compiler Error Message: CS0117: 'PX.Data.PXLogin' does not contain a definition for 'EulaRequired'
Source Error:
Line 633: username :
Line 634: string.Format("{0}#{1}", username, company);
Line 635: if (username == "admin" && PXLogin.EulaRequired(fullname))
Line 636: {
Line 637: PXContext.Session.SetString("EulaRequired", fullname);
In your customization, are you including any of the PX*.dll libraries? If so you might be replacing the correct version needed for your site. Make sure the only dll file ins your customization are those that you created.
I'm not sure what was causing this, but I've deleted the instance of Acumatica, removed all my class library references in the customization project and started over. This seems to have solved the problem.
Related
we have custom method in claimapi which will create activity and also add the document in claim. When we trigger that method we are getting below error message.
Error message :java.lang.IllegalArgumentException: Cannot re-add Activity:-505001 since it has already been removed. You must use bundle rollback to undo a remove.
Not sure what is causing the issue.
In ClaimAPI method. Ensure you already have a current bundle. If it’s not available, then create a new bundle and create a new Activity.eti record and add it in the new bundle , then provide all mandatory column information. You should be able to do it.
I have followed [this][1] link to add swagger to my existing project. I encountered the following error while setting up swagger. Any leads will be highly appreciated.
:xxx\node_modules\swagger-node-express\Common\node\
swagger.js:84
self.appHandler.get(self.resourcePath.replace(self.formatString, self.jsonSuff
ix), resourceListing);
^TypeError: Cannot read property 'get' of null
[1]: https://github.com/shawngong/Swagger-Node-Express-For-Existing-APIs
This error is popping out because of -
var applicationUrl = 'http://localhost:9000'; //application runs properly on this url
swagger.configure(applicationUrl, '1.0.0');//error here
Looking at the line of code in question node-swagger-express it seems as if you need to call :
swagger.setAppHandler(app);
Before the configure call.
I specifically see the maintainer of the project you are using (https://github.com/shawngong/Swagger-Node-Express-For-Existing-APIs) has a commit message related to setAppHandler in his last commit. Perhaps there is now an issue related to it.
I have an Orchard site with a SQL DB, when I try to access the site the following error happen:
Server Error in '/' Application.
None of the constructors found with 'Orchard.Environment.AutofacUtil.DynamicProxy2.ConstructorFinderWrapper' on type 'BodyLogic.Physicians.Services.PhysicianService' can be invoked with the available services and parameters: Cannot resolve parameter 'BodyLogic.LegacyDb.Services.Repositories.Physicians.IPhysicianRepository physicianRepository' of constructor 'Void .ctor(BodyLogic.LegacyDb.Services.Repositories.Physicians.IPhysicianRepository, BodyLogic.LegacyDb.Services.DtoConverters.IDtoConverter)'.
When I delete the "default" folder from App_Data/Sites/... and install a new Orchard everything runs perfectly, no exception and the modules are ok, but when I change the connection string to point to SQL Server again, the same exception happens again.
Any assistance in this matter will be highly appreciated,
Regards and thanks,
Alex.
It's not SQL Server that's causing the error, but corrupted data. There is a feature that should be enabled but is not. I bet it's this one: BodyLogic.LegacyDb.
You probably added a dependency to an already enabled feature, am I right? If so then what you see is the default behavior - Orchard won't auto enable the newly added dependency. You need to do that manually.
Feature enable/disable state is stored in the db table Settings_ShellFeatureStateRecord. To fix the error:
open it,
find a record with Name equal to BodyLogic.LegacyDb and
set both InstallState and EnableState values to Up
After you've done that
clear your App_Data/cache.dat,
restart the app pool and you're set.
I have an app that has working WSAPI queries to populate a cardboard and grid (works on rally1.rallydev.com), and it was even working 2 weeks ago in the rally sandbox (sandbox.rallydev.com). Now, when I run the app in the sandbox environment, I get network errors saying the get requests from sandbox.rallydev.com failed:
Failed to load resource
https://sandbox.rallydev.com/slm/webservice/v2.0/PortfolioItem...
but when I click on the link that failed, it shows the data I requested!
{"QueryResult": { "_rallyAPIMajor": "2", ...
Any ideas what is going on here?
This error:
Uncaught Ext.JSON.decode(): You're trying to decode an invalid JSON String:Failed to load resource
may come up if you have
parentRepos:"{{{parents}}}"
in
Rally.launchApp('{{className}}', {
name:"{{name}}",
parentRepos:"{{{parents}}}"
});
in App.html
Please comment it out
Note: commenting out or deleting this line must be done in App.html under templates folder. It does not help if it is done in App.html deploy folder because the line gets regenerated from the template(assuming you are using 'grunt deploy' command).
I have a web part and the dll is deployed to the bin of the web application.I have created a custom cas policy and deployed( wss_custom). Just for the sake of testing i have given Unrestricted access to whatever IPermission i knew (around 10). Most of the IPermissions i got is from the PermCalc.exe. Yet i get the following error generated by the web part:
System.Security.Policy.PolicyException
The problem is that i am not able to determine as to what permission is required to be given in the custom cas file.
Appreciate your suggestions.
Thanks
My general advice to find which CAS permissions you need are:
Give your dll SecurityPermission(ControlEvidence = true, ControlPolicy = true) (and of cause also Execution = true and what else you might need)
Catch the Exception and output Exception.ToString() not only Exception.Message
Then you should get a precise listing of the first Permission that failed, add that and try again.
Try to enable logging of .net assembly loader and see what happens with "fuslogvw.exe" tool (see http://msdn.microsoft.com/en-us/library/e74a18c4(VS.80).aspx for more details)