A weblogic application which is working fine, But on redeploying the .EAR file an error arises mentioning that .EAR file are already existing. On viewing weblogic console menu deployed, It shows no deployed .EAR.
Missing EAR File from Console Menu
This is peculiar, according to you, the application is working fine if that's the case then there should be something deployed on the server, but from the pic, I can't see anything.
This could probably because of the customize table option, it could be possible that you wouldn't have selected any of the available options.
If this problem arises after redeploying, then there is something wrong with the redeployed .ear. If by redeploying, you have just updated the .ear then it's mostly a problem with your .ear, if you have deleted and re-installed the .ear then you should probably check your config.xml file before and after the redeploy. And do check for your server logs when you are redeploying the .ear, that in itself should give a great deal of info.
Please do update your question with the server logs so that it would be easy for me (or others) to debug and help you out, and give an appropriate answer.
Related
I'm working on an Angular front end in Visual Studio Code for an app with a C# windows service back end. After spending a few days on the back end without touching the front end, I found that Visual Studio Code would no longer automatically recompile my typescript code every time I saved. Instead, I would have to ctrl+c out of the process and run "npm start" again.
I ensured that compileOnSave was set to true in my tsconfig.json. In doing so, I notice a warning:
Problems loading reference 'http://json.schemastore.org/tsconfig': Unable to load schema from 'http://json.schemastore.org/tsconfig': Unable to to connect to http://json.schemastore.org/tsconfig. Error: getaddrinfo ENOTFOUND json.schemastore.org json.schemastore.org:80
I noticed a similar warning for packages.json. I'm able to load the schema on the links on Google Chrome.
What could be a possible fix? Could I download the schema and load it in Visual Studio Code manually?
For me it wasn't the proxy blocking, but trusted domain list in VSCode.
Go to "Manage trusted domains" on Command Palette and add required url. Here we can add "http://json.schemastore.org"
This is whitelist for VSCode, as a security feature, stopping it running code from anywhere from internet.
Update:
Seems a network issue for me. When I set Http: proxy correctly it disappeared and json schema works well.
Go to "Settings" > "JSON" > "Schema Download" and disabled it.
That's worked for me.
The solution, as pointed out by #Matt Bierner in the comment above, is to set the "$schema" key to direct to a local schema file (which can be downloaded from the address in the error).
The problem seems to be caused by a web proxy. Why it showed up now is still unknown.
just follow these simple steps
click on the Settings icon at the bottom left of your vscode
search for JSON
you should see the schema download, it should be enabled
just turn it off
This worked for me.
I am configuring my Production Version DNN on other machine, but it is always redirecting to the installation wizard page.
I have googled over it and tried below mentioned solutions.
re-checked database connection
re-checked database is not corrupt.
tried to change below settings to false. by doing so, its redirecting to Install/UnderConstruction.htm page.
Can anybody help me to find solution for this issue?
If you navigate to /install/install.aspx what displays on that page?
I would be willing to bet money that it says the database connection fails, there is something you are missing in your DB setup, or connection string, that isn't working properly.
I have a VM that I set up to do development on two sites hosted on Acquia with the same codebase. I'm using version Drupal 7.26. I have it where I can access both sites from the host computer, but when I try to log in using /user/login on either site, I get nothing. The POST returns a 404 containing the log in page again.
I've tried settings $cookie_domain = '.my-site.dev' as well as $cookie = 'www.mysite.dev'. Neither has any effect. I also tried adding a bunch of random charactersto the file to make sure I was editing the correct file; with the random characters, pages didn't load at all. (See https://www.drupal.org/node/611920#comment-3110010.)
I also tried doing repair table sessions. I forgot which site I saw that recommendation from. I also tried delete from sessions just for kicks. Neither worked.
Any ideas? Thanks!
edit: Per https://www.drupal.org/node/261411#comment-3182566, I tried to go to www.mysite.dev/?q=user/login. This did not give me a 404, but I had tried (unsuccessfully, it seems) to reset my password through the database. I'm at least getting an error about a bad username/password combination rather than nothing at all. Still, I would think /user/login should have worked, too.
edit 2: The production site uses CAS, but logging in through /user/login still works.
I'm running into this problem and its driving me crazy.
Also, we are not allowed to update the version of IIS.
The content on the server (asmx files holding WCF webmethods called via SOAP) exists and I can freely browse in inetmgr to the virtual directory that contains this data. The files all exist all on the file system and the virtual directories all point to the correct spot and have the correct ACLS, but when I go to their URLs all I get is a 404 message.
I have reset IIS, I have rebooted the server, and I have done everything I can think of.
The IIS logs simple return "404 - -" as the entire line contents, with no other data in the line.
The event logs show nothing, and ASPNET is not dying or anything like that.
With no event logs, and minimal logs in IIS , I have no idea what to do and was hoping that others had run into this before.
In IIS logs there should some codes along side the 404 error which will help find the issue.
Check IIS has the correct version of .Net installed using aspnet_regiis command line tool. Also check that ASMX extensions are mapped to the .Net ISAPI filter as they are with ASPX pages.
I hosted one DotNetNUke Application to my production server, and locally it works perfectly. But, when browsing it redirects to the error page.
How do I set the default.aspx as my application default page? I am getting the error as below:
DotNetNuke Error
--------------------------------------------------------------------------------
Windows Vista
Return to Site
Can anyone can help me, please? Will be appreciated.
UPDATE:
Hi, I changed the Path in the PortalAlias table to the server url and default.aspx as the starting page, but it displays the error.aspx as default page.
Please help me resolve this problem..
So, the application works perfectly locally, but not when you put it on the server. Is that correct?
Make sure that your portal alias is valid. If the site is hosted at
http://www.mysite.com
then www.mysite.com needs to be listed in the PortalAlias table
If you open that table in SQL Mgmt Studio, you'll probably see an entry attaching the portal to your local DotNetNuke folder (ie. localhost). Just add a new entry that points to the same PortalID, but with the correct URL for your production server.
Assuming your DNN installation is at "mysite.com", if you navigate to
http://www.mysite.com/default.aspx
do you still get the error page? If so is any error listed?
I was able to fix the issue (for me) by taking the web.config file from a working site with the same version of DotNetNuke and modifying it to have to correct machine key and connection strings. This is my last resort something is really strange procedure.