404 Error when copying Orchard CMS - http-status-code-404

I have one knowingly good site. It works as expected. I copied all the files from that one directory to a new directory. I created a new website with the correct host header and pointed it to the new directory. When you browse to the new site you get a 404 error.
I have checked the file permissions. I have even made the two sites share the same app pool.
Any suggestions would be helpful.

If you look in /App_Data/Logs you can see the error message. As it turned out for me, it was because I was trying to run the same "tenant" twice on the same server.

Related

SSRS - Managing Folder, GET AllowedActions Method Returns 404

I'm using SQL Server 2017 Reporting Service and I see that something is wrong with my permissions. I'm in Administrator group in SSRS machine, I'm can manage most of the folders in SSRS browser web app but I can't manage some of them...
For example,
I newly created a folder called CWB, I can manage CWB folder's own permissions
When I navigate into CWB folder, I can't manage folders or permissions inside of CWB folder
Then I realize that when i click to manage button on folder, SSRS sends GET request called AllowedActions and the request returns with users permitted actions, so I examine the body of that request and found this,
For CWB folder, I get the permissions successfuly AllowedActions method returns Status: (200),
But when I navigate into CWB folder and try to manage another folder inside of CWB folder, AllowedActions method returns Status: (404) as seen below,
And the error message says,
An error has occurred. Something went wrong. Please try again later.
Other group members of Administrator can manage/edit same folder/folders except me. I will very appreciate if anyone help me to fix this issue.
Thank you for reading my issue.
According to this article,
Encoding should be the problem. So try and look at your browser language. Changing your broweser language to English will fix your problem.

How do I configure Bolt CMS on an subdomain correctly?

I currently have a working Bolt installation on my main domain (i.e. example.com). But I also wanted a subdomain (i.e. blog.example.com).
I created it, but when I uploaded Bolt to it, but when I tried to access it I only got 404 errors.
I tried copying the Bolt installation from the main domain, then only the main page works, but when I try to access the CMS I get a 404 error. Also if I try to access other pages (i.e. blog.example.com/images) I get a 404.
I tried to change the RewriteBase in the .htaccess to all possible things, but no result.
Also if I do it on another hosting company it is just working, does anyone have a suggestion?
Thanks in advance!
if it is working at another hosting company, maybe that is something non-bolt related issue.
I assume that both of them Apache, so after checking file access rights then I would check apache log.
I had the exact same issue and found out that mod_rewrite was disabled on my sub domain.

symphony datasource error

When creating a data source that pulls from any of my sections and pressing "create data source", I get the following error:
Forbidden
You don't have permission to access /symph-page/symphony/blueprints/datasources/new/ on this server.
Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.
Strangely, if I pull from the system or provide custom xml, the data source is created fine and I don't get the previous message. Running symphony 2.3 on server that should be meeting the technical requirements. I have run Symphony before and never encountered this sort of issue.
It sounds like you need to change the workspace/data-sources directory file permissions so that the web server user can write files into it.
For example, on a Linux server (777 may not be necessary and depends on your webserver's configuration):
chmod 777 /symph-page/symphony/blueprints/datasources
If you access the server via FTP, your FTP client will probably let you do this.
Edit: Re-reading your question, I think I was mistaken in saying this is a workspace writing permissions issue. I don't recognise the "blueprints" directory path. Does this directory exist within your installation, and does your webserver have read permissions?
You might also want to make sure that you .htaccess file is present.

404 returned from a file that exists in ASP.Net on IIS 5

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.

getcolumntype() function in model.php script giving problem

The site that I worked on is working very fine on the test server. I downloaded the same copy and uploaded onto the new server (live). I changed the database.php in app/config folder to set the db connection variables. And I get this following error when I try to open the link.
Cannot access empty property in {serverinformation}/cake/libs/model/model.php on line 1002
I am not able to find any help on this anywhere. Can somebody help me please. I need to get the site live... and I am not sure what could be the problem and where to debug for it.
Is that the only error message?
Check file permissions on the live server.
Try clearing your cache files - all files in and below app/tmp/cache, but leave the directories themselves intact.

Resources