I have an application with the web browser launch properties set to open designated XPage (home.xsp).
It works fine on our test server but not on the new DMZ server where I get a 404 error (HTTP Web Server: Item Not Found Exception)
I've looked on Stack Overflow but haven't found anything to point me in the right direction. Would someone let me know how I can resolve this?
Thanks,
Dan
I would try some things
clean the project
manually build the project
check the data\Technical support folder and the data\Domino\workspace\logs folder on the server for clues
Related
I am trying to follow the quick start sample on my local Windows 10 with IIS. When I browse
"http://localhost:5000/.well-known/openid-configuration" however, I got "This site can't be reached" error with Chome. When I tried the same with IE, it still failed but with some more detail: "The device or resource (localhost) is not set up to accept connections on port '5000'.". All I did was following the doc of the quick start. Is there something I missed, such as configuring IIS is some way?
Choose Kestrel as the startup project and then you will see the handy log in a console window. That will help you debug your connectivity issues. In the log you will see what port Kestrel is listening on.
Just choose the name of your project here instead of IIS Express:
I am trying to publish sharepoint2016 website including Power View reports which created by SQL server services service (SSRS). there is top level site and bi center as sub-site; both are working fine but problem is that when I try to view the report it said the error:
"the web application at [url] could not be found. verify that you have typed the url correctly. if the url should be serving existing content, the system administrator may need to add a new request url mapping to the intended application."I search about the error but It does not reach my target.
https://forums.asp.net/t/1970799.aspx?SQL+Reporting+Service+Runtime+Error+The+item+reports+Report1+cannot+be+found+rsItemNotFound+
note that the whole site is working fine in domain.
Please help...
Thanks...
Sorry for late guys...
i found that Power shell of SP cannot execute any command related to SSRS
it just need to reinstall SSRS service compatible with SP2016. then every thing is fine.
I have followed the relatively simple steps to migrating a Magento 2 site from my localhost to a live server. When I type in my new URL to see the site, I get an error screen with a message directing me to an error log.
From inside the error log I see the following error message:
a:4:{i:0;s:48:"SQLSTATE[HY000] [2002] No such file or directory";i:1;s:3133:"#0 /homepages/25/d336955856/htdocs/mfg_oldSite/product-catalog/lib/Zend/Db/Adapter/Pdo/Mysql.php(111): Zend_Db_Adapter_Pdo_Abstract->_connect()
I am not able to access either the regular public pages because of this error. I also get a 404 error when trying to access the admin page.
Any ideas? Any further info needed to make my question clear?
Check your host setting in /app/etc/local.xml
Try with changing it from "localhost" to "your server host"
have a look PDOException SQLSTATE[HY000] [2002] No such file or directory
EDIT
As per the whole discussion we have done. I am assuming that you have wrong credentials. this is why you are not able to connect to your DB.
have you checked your local.xml under app/etc or if you already done that then rename your local.xml and enter your website url on browser ,you will see installation panel, install your website again with right credentials i hope this work!!!
Hey please follow the following step it will remove the error
1) Rename the your local.xml file,
2) Delete all cache files form your system.
3) Run your site in your browser it will ask for the configuration steps.
4) Follow the steps and select the add database detail which you have updated in your live site.
It will setup all thing and the data will be same as it is.
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.