My JDeveloper IDE hangs every time I go to Application Module > Data Model tab. I have tried re-installing. We’re using SVN Subversion for Server. We’re not able to process further because of this issue.
It was working until I did commit on Subversion, after that I'm facing this issue. My whole team is having this issue. Any help?
Few suggestions:
Try to revert your SVN changes that caused the problem. Use Tortoise SVN for reverting changes, not Jdeveloper SVN client.
Try not to use Jdeveloper SVN client. You can use TortoiseSVN instead, as separate tool.
Additionally, I would try to disable all Jdeveloper Audit Rules. Go to: Preferences -> Audit -> Profiles -> Code Assist Rules", then uncheck "Application Development Framework". Restart Jdeveloper and see if you have problem anymore. If this works, try to enable each extension one by one and see if you can nail the one causing the problems.
Related
While working with some projects checked out from Git, we get errors with modifying the project settings in MyEclipse. I am trying to modify the deployment values in my workspace and it is not letting me (screenshot below).
There isn't a lot of information to go on, here (e.g. what is the version of MyEclipse, what type of project is this, what properties page are you switching from, the OS and version, whether this has worked before, the error log - but please don't paste that in here - and so on).
However, here are some actions that might help resolve it:
Firstly, try a fresh empty workspace then import the project from the old workspace, or better still import again from Git. This would help clean up possibly corrupted settings in the workspace.
Another thing to try is to launch MyEclipse with the -clean option (just add that option to the top of your myeclipse.ini file, found in the installation folder).
#Howlger is right, though, this is a commercial product and we may be better able to help if you raised the issue in the MyEclipse support forums.
I am hosting a project in visualstudio.com and what I have is only a VS studio 2012 installed. My friend has checked out and locked a file and then re-installed his windows, also creating a different name for his computer and thus he cannot check it in. Is it possible to remove that lock in any way? I am the one who created the project, so I should have all admin rights. It's just I do not know how to do it. I tried using
tf lock /lock:none /workspace:FRIEND-PC;friend#email.com filepath/filename.css /collection:https://***.visualstudio.com
however it seems to be searching in my computer which is not what I want at all. Nothing better I was able to find though :(
I had this trouble too. I couldn't get the commands to work without errors. What did work for me was much simpler.
From within Visual Studio 2012(and 2013):
File -> Source Control -> Advanced -> Workspaces...
In the dialog that came up, I checked "Show remote workspaces" and the locked workspace came up in the window. I then selected it and clicked "Remove".
try
tf workspace /delete FRIEND-PC;friend#email.com
Deleteing the old workspace will remove any pending changes or locks.
Here's what I did to remove the lock
tf undo /workspace:USER;Domain\User xyz.cs
I was able to remove the lock this way:
C:\Users\****\Documents\Visual Studio 2012\Projects>
tf undo /workspace:FRIEND-PC;friend#email.com
/collection:https://xxxx.visualstudio.com/DefaultCollection
$/xxxx/ProjectFolder/ProjectName/filepath/filename.css
I have somehow got into a strange situation with my CRM system.
A plugin I have developed is not getting updated correctly when the solution is imported. When I choose to maintain the customisations the plugin updates dont get applied, but when I choose to overwrite customisations the steps get doubled up and so the plugin gets fired twice.
Has this happened to anyone else? How do I stop this from happening?
Thanks
I've had a similar situation where I had plugins registered twice after importing.
I believe the way I solved this was:
Use the plugin registration tool to remove the plugin from the server you are deploying to.
Reimport the solution.
I can't see you doing any major damage here, but I would suggest backing up the server first because I'm not 100% on this one.
Are you assigning a strong name to the assembly? I've seen this kind of thing happen in CRM 4.0. If you don't assign a strong name with a key, CRM doesn't seem to see that it is the same assembly.
If you deploy the plugins using the plugin registration tool, solution deployment will duplicate all of the steps as it does not recognise the deployed plugin steps as their ID is changed.
If plugin assembly is deployed without the steps, you've forgotten to add the steps into the "Sdk Message Processing Steps" section of the solution.
#JamesWood approach will always work but is very heavy handed for a production environment, an IIS Reset and restart of the MSCRM services (in services.msc) usually clears any cached plugin assembly, while a redeployment should only be needed/used in dire situations.
I have downloaded sample XPages database http://www.jmackey.net/groupwareinc/johnblog/johnblog.nsf/d6plinks/SurveyToolSample
and deployed it to server. I can open it without problem with my Lotus Notes 8.5.3, but my colleague cannot open it on his Lotus Notes 8.5.2 Standard Configuration.
He gets the following error:
**This Page Cannot Be Displayed**
Internal system error when processing the request for the page ( http://127.0.0.1/xsp/JHGNES!!Major %5CSurvey.nsf/HomePage.xsp?OpenXPage&xspRunningContext=Notes ).
Please retry this request.
Enforced by host JHGMELWEB01
If this condition persists, please contact your corporate network administrator and provide the code shown below.
Notification codes: (1, INTERNAL_ERROR, http://127.0.0.1/xsp/JHGNES!!Major %5CSurvey.nsf/HomePage.xsp?OpenXPage&xspRunningContext=Notes)
I have Recompiled all lotusScript in the database using my 8.5.3 client.
Any ideas what can be the problem?
Recompiling all Lotusscript does not re-compile XPages.
Try doing a clean of the project by opening the database in Domino Designer and then use Project - Clean in the menu. Clean removes all built code and then re-builds the code.
In your 853 Designer, try recompiling the app to support 852 as the minimum release?
Launch the Application Properties in Designer, go to the XPages tab, then under 'Minimum Supported Release' select to compile this application to run on 'Release 8.5.2'.
For the vast majority of cases, apps built or compiles on current releases will work fine on previous releases without needing to do this step. Though in some cases, changes in the new release, like a new property for example, may cause failures in previous releases. This is what I'm guessing what is happening in your case.
Thanks for your quick responses. I have done more testing after I tried suggested solutions and it seems like the problem is not in the database itself but in this colleague's PC configuration, as it works on 5 other PCs running 8.5.2 and 8.5.2FP2.
Actually when you change "Minimum supported Release" on the xpages tab of app properties it prompts you to rebuild all the code.
The problem was in the location settings of that particular machine. After we removed contents of "Proxy configuration" it worked like a charm.
On our Trac system, two things suddenly stopped working. The first thing is the update of the "Browse Source". The second thing is the auto-fixing feature. The only solution for the first issue is to manually run the post-commit hook of the SVN repository. But than we still have the problem, that Trac doesn't close ticket anymore depending on the SVN commit message. That was working before without any issues. Ah and a third thing is that PNG images are no longer shown in the HTML preview. The user has to download the file to see it.
Is there any known bug or issue for our described problem. Or how can I update the Trac system without loosing all the information within the Trac projects (I have set up a multi project Trac system).
If all else fails, reboot the server :)
Can you give us some more info about your server and Trac setup? For example, OS and version, Trac version, plugins used, etc.
It's odd for things to suddenly quit working. If you are running a Linux system, it's possible that your server installed some updates that your system isn't fully compatible with (for example, upgrading Trac can cause some plugins to quit working properly). Check your server's logs to see if anything was updated or reconfigured around the time Trac quit working.
Also, try setting Trac's log priority to 'DEBUG' and see if the Trac logfile contains any useful error details.
The solution was the following: file permissions!
To solve the issue we used the sudo in the post-commit hooks of SVN like the following:
sudo /usr/local/bin/trac-admin /var/trac/reponame/ changeset added "reponame" $REV
And we had to allow the SVN user to run the trac-admin command using visudo:
www-data,svn ALL=(ALL) NOPASSWD: /usr/local/bin/trac-admin