WebLogic 11G: Deleted WARs Still Being Listed - weblogic11g

WebLogic 11G
Windows XP
Hi,
I'm running WebLogic 11g. I put two WARs into the autodeploy directory. Everything was fine. A few months later I no longer needed them so I deleted them from the autodeploy directory.
When I log into the WebLogic 11g Admin site, those WARs are still listed as being there under "deployments". If I try to delete those listing through the admin site I get told that since they were autodeployed they have to be manually deleted from the directory. Which I did, in addition to restarting WebLogic 11g and I even tried stopping the services first. No dice.
How can I fix this?
Thanks much in advance
Steve

After you shutdown your WLS server, open the domain config.xml in the text editor and search for all the tag. Very likely you will see section regarding those war files that you deleted. Remove these sections. Then start your WLS again.

Related

pgAdmin 4 opens but clicking on server won't show anything (not even error)

I am on MacBook Pro (late 2015). I have a fresh install on macOS Catalina 10.15.2.
I have PostgreSQL 12 which is running with no issues.
Running which psql gives me the correct path: /Applications/Postgres.app/Contents/Versions/latest/bin/psql
I can run psql commands with no issues (create user for example).
I have installed pgAdmin 4 (version 4.16). The installation went well with no issues. pgAdmin 4 will open with no issues BUT clicking the server section instead of opening all the users, groups and databases seem to freeze the process (in other words it won't show any).
I have tried to reinstall, restart numerous times. I have downgraded to 4.12 thinking there might be an issue having the latest version. I am getting, however, the same result. I have tried to Google out but haven't seen anyone experiencing a similar issue. Thank you for all your help with this.
Weirdly I managed to resolve this by chance. Out of desperation, I clicked on Object => Create => Server Group and I have named it Postgres. Clicking again on the Servers in the sidebar opened all the usual databases, Login/Group Roles. If anyone knows why I had to do this and how come it did not work as usual I will be grateful.

Filezilla/Wildfly server deployment error (Possible database dependencies)

This is my first time on here. I am having an issue deploying a java application I made on myEclipse. I am using Filezilla to host my Wildfly 9.0.2 test server. I exported my project to a .war file and upon dragging it into the test server I am met with a deployment.failed. Upon viewing the file in Notepad it declares "Services with missing/unavailable dependencies". one such error can be seen below:
[ "jboss.naming.context.java.module.myproject.myproject.env.common.jdbc.database_connection is missing [jboss.naming.context.java.database.connection] "
There are five of these similar errors and all point to a diffferent database connection of some type that I am not using within my project. I understand the issue but I do not know where these dependencies are declared and how I can go about removing them.
Any help will be greatly appreciated.
Kind Regards,
Paul
Creating the WAR file will use the project's deployment assembly (assuming you're using MyEclipse 2013 or later). Right click on the project and select Properties. Then go to the MyEclipse/Deployment Assembly page. This will have all of the files that are added to the deployment (or to the WAR file).
However, the message seems to suggest that a project is using a database connection which can't be found when running on the server. A first thought was that you're using the inbuilt Derby database but don't have that running when you run on Wildfly.But you say that you're not using a database. Also, I'm not familiar with how Filezilla can host a J2EE server - I thought Filezilla was an FTP client and server solution. Perhaps you could give more details, if this answer doesn't help.

Value cannot be null, Parameter name: viewInfo

After installing SP2 to an existing SQL Server 2008 R2 I lost access to all my databases and started facing the error in the screenshot.
Any ideas?
Check the environment value for Temp and TMP.
C:\Users\buck>set t
TEMP=C:\Users\buck\AppData\Local\Temp\2
TMP=C:\Users\buck\AppData\Local\Temp\2
Make sure the directory listed exist and your id has appropriate permission to write to that directory. Alternatively, through the control panel (Control Panel-> System and Security-> System -> Advanced system settings), you can change the default directories that are assigned to TEMP and TMP.
When I've seen this issue, it is usually because the Drive that SSMS is installed on has run out of free space. Deleting some old Log files clears the issue up.
Doing that quick check might be worthwhile before going forward with a re-install.
I got this error on our remote shared server. Turned out that our C drive did not have any space left.
I got it working by asking my colleague to close his SQL Server Management Studio session and it cleared up 7 GB right away! I could login then! Woot woot!
Right click on the SSMS icon and click 'run as administrator'. At the SSMS console verify that the error is gone by clicking on the 'Databases' tree node. The error should now be permanently fixed and you do not need to run SSMS as admin anymore. Next time just start SSMS normally and it should work fine.
Changing the temp variables did not resolve. Drive with SMMS installed has 34% free space.
However, using Run > %temp% > it would error out as "C:\%username%\appdata\local\temp\4 was missing" (this is not listed in my TEMP/TMP variables).
Quick solution was to add sub folder for "4" in c:\%username%\appdata\local\temp\ and now able to open SMMS without issue.
When running into this I found it was related to the environment temp folder (TMP Temp).
I had tried adding the "2" folder to this location with no success.
C:\Users\USER\AppData\Local\Temp\2
Try typing %temp% in file explorer and see if it takes you to a valid location. I found that I received an error because it was trying to go to a "4" location.
C:\Users\USER\AppData\Local\Temp\4
I created a folder named "4" in the Temp folder, reran SSMS, and it started working again.
A quick google suggest that apparently it is a bit common issue. It looks like that it is not an issue of SQL Server itself but actually .NET issue And most common (and quick) solution I found is to reinstall SSMS.
I've found that if you are upgrading an iseries odbc driver on a sql cluster. Lots of times you will run into this issue exactly. Renaming the machine.config in both the 32 bit and 64 bit folders does the trick. we currently upgraded from version 12 or 6.1 to 7.1 or 13 as the version 12 was causing a bug check on one of our SQL instances. Upgraded, and the issues all went away.
Cheers,
According to the following link:
https://connect.microsoft.com/SQLServer/feedback/details/573771/value-cannot-be-null
I just checked that my user is local admin, then i logged off and logged back in.
After that step i haven't received this error again.
I was receiving this exact error and thought I'd have a go at running the repair.
Well the repair didn't resolve the issue however it did tell me that it was unable to access machine.config in C:\Windows\Microsoft.NET\Framework\v2.0.50727\CONFIG - found it didn't exist! There was another file machine.config.default
So had a stab at copying, renaming to .config and viola resolved it and everything working like a champion.
I got the same error in SSMS and I found this link and followed the steps as it mentioned.
The problem appeared to be when accessing the contents of a settings file. The file had invalid entries. This file is CurrentSettings-. The fix for this is as shown below:
On the server Go to start menu–>Your profile–>Documents–>SQL Server Management Studio–>Settings (this is the location of the file specified above)
Delete all files from this folder
Restart sqlserver services
Launch the SSMS and this error is gone. You will be able to expand all the folders and perform regular SSMS activities without this error.
Once I performed these steps and restarted my PC this error was gone and SSMS worked fine.
I just faced this issue and resolved it immediately in 5 mins. Just go to Control Panel and Run Troubleshooting tool on Programs.
**PATH** Control Panel\All Control Panel Items\Troubleshooting\Programs
It will give you the list of installed programs which may have any issue. Scroll down that list and find 'SQL Server Management Studio' and run troubleshooting process on that. It will hopefully fix you issue.
I gets this messages many times and every time it is resolved by different solutions below few of it.
Solution: Clear cache from temp folder, Press windows + R => type "%temp%" => Delete all the files from temp folder... And try weather it works and opens ssms successfully
Solution: create folder named "2" in this above mentioned temp folder location... And try weather it works and opens ssms successfully.
Solution:create folder named "4" in this above mentioned temp folder location... And try weather it works and opens ssms successfully.
Solution: It may cause because of low disk space in drive ssms is installed... so free some space...And try weather it works and opens ssms successfully.
Solution: Format is the last solution...

Oracle Database Mobile Server first steps

I download jdeveloper studio edition and install it in C:\Oracle\Middleware
then I install weblogic instance using C:\Oracle\Middleware\wlserver_10.3\common\bin\config.exe
to C:\myproject\domains\myweblogic
Then download DMS_11.1.0.0.0_WINDOWS.zip and install it to C:\Oracle\Middleware\Mobile.
thereafter cant start
C:\Oracle\Middleware\Mobile\Mobile\Server\bin\runmobileserver.bat
unless i change the variable to this batch file
set DOMAIN_DIR=C:\myproject\domains\myweblogic
what do I do next to see that it works?
is there a simple example that creates a sigle table and synchronized between server and mobile clients?
very difficult to find information on this technology. interfere very popular tags (Oracle, Database).
If you install Database Mobile Server directly in the WebLogic directory, you will not need to edit the batch file. For instance, I believe the default install directory is:
C:\Oracle\Middleware\wlserver_10.3
So if you used the default install directory, you would install Database Mobile Server there, with no added 'Mobile' or other directory. If you chose to install WebLogic elsewhere, then replace the above with that directory.
There is another small issue to be aware of.
The installer will give you warning about installing in a non-empty
directory. You should click through the warning. This is a known issue
documented in the Release Notes.
Regarding your other question about a demo, there is a Java demo found in
<MOBILE_HOME>\Mobile\Server\demos\consolidator_api
You will need to download a client and perform a sync, which is documented here:
http://download.oracle.com/docs/cd/E22663_01/doc.11100/e22681/instsqlite.htm#BABGAACI
I hope that helps, good luck with your project. Let me know if you have further questions.
Eric Jensen, Oracle PM

Reinstall xampp

Im using a mac. Xampp stopped working after the latest update 10.6.8 and I think it may be a direct result of the update. Anyway, Id like to reinstall xampp however i didnt backup my database and i cant get into localhost/phpmyadmin to import it. Is there anyway I can backup my database another way and reinstall xampp? or is there another problem as to why the pages dont load.
I get this error when i go to localhost/phpmyadmin: The requested URL /phpmyadmin was not found on this server.
When you use XAMPP, it automatically freezes all the other database. If you are using mysql, you can backup them either using
1.mysqladmin tool (http://dev.mysql.com/downloads/gui-tools/5.0.html)
directly login as the admin and select the databases that you need and backup.
or
2.using command line (manual backup):
goto mysql/bin and then follow this tutorial: http://linux.byexamples.com/archivesc/90/backup-and-restore-mysql-database/
When you uninstall xampp, the databases (in var/mysql) and the htdocs folders are not normally deleted by the uninstall wizard. When you reinstall xampp, those existing folders will be used. It's also a good idea to back up those folders directly to reduce the risk of loss.

Resources