I have created one application in oracle application online, and i have not worked for 3months in it but i have worked before a lot and not even have a backup file of that application.
i got an email that "Your workspace is about to be purged!" and when i trying to login its saying "Workspace aaa will not be purged. Thank you."
But i cannot see the workspace again, please anyone help to recover the workspace in oracle application express
This is a routine email that apex.oracle.com sends to purge workspaces - to remove dormant workspaces.
Workspace will not be purged
this means that your workspace is still there.
you can go to apex.oracle.com and log in using your credentials
Related
I had a database that I was using for two applications, when I deleted one that I no longer used, it deleted the database together, is there a way to recover?
Was your second app using manually added credentials to access the database, or did you use Heroku's "Attach Database" option to link to it?
When deleting an app on Heroku, all associated resources that were created within that app will also be deleted. If Heroku was made aware another app was attached to it (via "Attach Database") then it ought to have shown a warning.
Either way, if the database no longer shows in your data dashboard then it has been removed. Contact Heroku support to see if they keep deleted databases a short time before permanent deletion...
In future, it's worth occasionally using Heroku's "Create Manual Backup" option for databases (you can find it in the "Durability" tab for each database) and downloading a copy to keep safe. (And definitely do a backup again before deleting anything, I always find that a nerve wracking time! ;)
We use CRM 2016 SP1. We deployed our latest changes from Dev to QA, staging and production by means of importing a managed solution file. As part of the solution file there is a custom Action workflow (Category = Action) with the publisher prefix set to our company name.
The workflow has been activated and working well in QA and staging but when trying to activate it on production CRM comes up with the error "Unexpected Error". Downloaded error details show the same message.
Upon investigating the workflow in production we realised that its publisher prefix had been changed to "new_". To be more specific, the Process Name property starts with the correct prefix name but the Unique Name property starts with "new_".
We had not made any changes to the workflow in Dev and it was working fine in production prior to the deployment.
So far my research on the Internet on how/why this change has come about and how to fix it has been in vain. So any help is greatly appreciated.
Regards
This is identified as an issue in 2016 SP1.
Check Link Here
The solution is to Recreate the Process with correct Prefix and delete the one which start with new_ that to before final deployment/packaging/release.
It is observed that even both processes has different prefix they are identified as same process.
Please see this link for the solution
https://community.dynamics.com/crm/f/117/p/243572/680715#680715
I created an simple skeletal web application. I created only a simple blank JSF page. Right click and run. Then I got the following message in the Log console.
The Server Instance cannot be started because the Integrated Weblogic domain was not built successfully.
Can anybody suggest me why I am getting this error?
Your question does not provide detailed information.
The best way would be to go to weblogic domain options from start menu and create a new domain.
Then link that domain in jdeveloper and use the same. Delete the integrated domain i.e. base_domain folder.
There were 2 ways this problem can be fixed:
Try starting and fixing any issues with the Integrated weblogic domain. Till that is not starting successfully, JDeveloper cannot do anything on that. For me one time startup of the current domain outside of the Jdeveloper solved the issue. After that it was working fine from JDeveloper too.
Another option is as stated by vijayinani above to create a new domain and link it. But, beware your integrated base_domain is not having anything which you need to preserve if you plan to delete that.
My team uses Web Deploy in order to deploy updates to our website on to our production server. The last few days I've been doing some housekeeping and have changed my password (which I made sure to update in my Web Deploy configuration) and moved the solution for our website to a different location in TFS. I'm not sure which (if either) of these has caused the issue, but I am now no longer able to publish our website using Web Deploy.
I can preview the publish fine, but I can't actually publish it.
The Output in Visual Studio shows this:
Start Web Deploy Publish the Application/package to https://[REDACTED]:8172/msdeploy.axd?site=[REDACTED] ...
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v12.0\Web\Microsoft.Web.Publishing.targets(4270,5): Error ERROR_COULD_NOT_CONNECT_TO_REMOTESVC: Web deployment task failed. (Could not connect to the remote computer ("[REDACTED]") using the specified process ("Web Management Service") because the server did not respond. Make sure that the process ("Web Management Service") is started on the remote computer. Learn more at: http://go.microsoft.com/fwlink/?LinkId=221672#ERROR_COULD_NOT_CONNECT_TO_REMOTESVC.)
Publish failed to deploy.
(Note that I've removed some identifying information from this log, which has been replaced with '[REDACTED]')
I found a page describing this issue here: http://www.iis.net/learn/publish/troubleshooting-web-deploy/troubleshooting-web-deploy-problems-with-visual-studio
It says to check in the WMSvc log to find the status and substatus codes for further troubleshooting.
Here I've colour coded lines relating to the preview in green and lines relating to the actual publish in red. As you can see, the requests returned with a 200 (OK) status, meaning the server is not aware of any error occuring. However Visual Studio reports a failure and my production website has not been updated.
The fact that log entries are generated tells me that Web Deploy is properly installed and the handler is setup correctly.
It seems the deploy always fails after ~30 seconds. This could be coincidence, but I'm wondering if there's a timeout at play.
Could anyone suggest further troubleshooting steps?
EDIT: This issue occurs when I try to publish to ANY server, so it's definitely a client issue and not a server issue.
EDIT2: I have two branches of my project, Main and Dev. I just discovered that I can still publish from Dev, just not from Main. They both have identical settings. Very weird.
This can be caused by few reasons. I've written this blogpost earlier about the issues.
When we install the Web Deploy tool, it creates local users "WDeployConfigWriter" and "WDeployAdmin". In your case, you've explicitly changed the password to reset these local users passwords I think, or, the passwords of those in charge. To reset these local users passwords, you can do following:
"Control Panel -> User Accounts -> Give other users access to this
computer -> Advanced -> Advanced -> Users"
Reset WDeployConfigWriter's password
Reset WDeployAdmin's password
"IIS -> Server Node -> Management Service Delegation"
Right click on each
rule with users "WDeployAdmin" and "WDeployConfigWriter"
Click Edit
Click on "Set..." button in "Run As" group
Enter the name of the account you are going to update the password of
Enter password on two areas
If the operation is still erroneous see Event Logs on Windows, they are the real deals here. Check this link.
Recently I have installed and configured the Oracle BPM Suit and able to access Oracle Business Process Composer using the link as mentioned below
http://localhost:7001/bpm/composer/
But sometimes it take too long time to enter me to the dashboard and shows "Authentication Service Error, please contact the Administrator".
I have done the windows environment setup.
I have checked my credentials and sometimes it allows me to enter but sometimes this annoying message comes to me. I don't know what's wrong with the authentication service. I'll be grateful for any help/recommendation.
I went through the same problem, here are some suggestions:
Remove DOMAIN and create another, remembering that everything will be lost;
Create another user WebLogic;
If you want to solve the problem look for logs on WebLogic or in the DOMAIN directory, to understand the problem;
Recently consultants ORACLE were here on business and found that the 12c version is not stable. Look for patches on the Oracle website.