Apache on windows cant view asp.net files? - apache

I wonder if its just apache isnt suited well for windows but im kind of a noobie at this and everywhere i go i cant find a way to view asp.net files on my apache server. im running my server on my windows computer.
edit my computer can run asp.net files just fine, but when its in my server and opened through it, only the source appears for it.
edit2 my question is unique because Im using windows and i cant find instructions on how to install mod_mono on windows

Related

Embarcadero RAD Server, cannot get Apache server to run RAD Server DLL

I've set up Embarcadero RAD Server on a web server, I've got the standalone executable running, which works perfectly. I'd like to get Apache to execute the DLL, so instead of having an application sitting there, it runs quietly in the background. RAD Server had a DLL which, from my understanding is supposed to plug into Apache and be executed by apache.
I've followed the tutorials on embarcadero's website for achieving this, what happens at the moment is apache just refuses to run when I've got it configured to use the RAD Server DLL, when I remove the lines from the httpd.conf file Apache starts again as normal.
Has anyone experienced a similar problem? it's not an issue with the configuration of RAD Server, as the standalone executable would not work if there was; that is unless there's something that needs to change for the Apache to use the DLL to run RAD Server.
Please let me know if there's anymore information that would be useful for me to supply.
I've followed the instructions from the Embarcadero website, so I've tried including all of the RAD Server DLL's in the same folder as the RAD Server DLL. I've tried modifying the config settings, removed my custom API BPL to allow just rad server to run, and it also fails. I would have expected that following the embardaero instructions with a basic RAD Server DLL file it should work.
There must be something I'm missing when I do the configuration.

Trying to deploy ASP.Net core website onto a debian server

I am trying to find a way to deploy a ASP.Net Core (version 6.0) Website onto a server provided by a domain provider.
The server is Debian and as far as I can understand I cant change things on the server except uploading the files required for the Website.
I have created a simple website in Visual Studio 2022, using MVC Framework. It has no database as it is not required.
So the issue is how would I go about deploying the website onto the server, I understand I have to change my files to be Debian compatible but also I read up on the documents from Microsoft, and they insist I need to install .Net onto the server. Which I cant seem to do.
I tried reading through other solutions but there doesn't seem to be any updated answers.
I am new to this so sorry if this has been asked before. but any help would be welcome.

500 internal server error - Hosting nopCommerce 4.0 on Godaddy with Windows Plesk (not VPS) Account

I know how to install and setup nopCommerce.
However this is specific to hosting it on Godaddy Windows Plesk account, I have searched, looked and read many threads, documents on nopCommerce 4.0 and hosting it or installing it. However I am unable to successfully install nopCommerce 4.0 on Godaddy Windows Plesk (not VPS) Hosting.
I get 500 internal server error, looks like .NET Core is not supported on Windows Plesk hosting on Godaddy, on VPS hosting it works.
So is any one able to successfully do it on Plesk?
As mentioned in my comment above:
You will need .net framework 4.61+ and .net core 2.0+ runtime to successfully run nopCommerce 4.0.
And as mentioned by you
GoDaddy with Plesk does not support .NET Core yet.
See https://in.godaddy.com/help/software-versions-on-hosting-accounts-897
In .net core, iis is not really used as a web service, its just use to point users to application. Application is a exe file so actually windows will run it, so i dont think that its a issue of plex or something like that.
I hade same error for nop4 on vps, but i cant tell you any advice if you don't check logs.
Try see the logs,application set logs automatically as a text file.
You may solve when check that file or create another question so we can help you and others who had the same error

Coldfusion COM not registered

First time ever using ColdFusion.
We have a website that uses ColdFusion 9 on our live server. It calls a COM DLL to encrypt certain things. The code on our live server works fine.
Since I may be taking over the project I installed ColdFusion 10 Developer edition on my local machine and copied all the source code and DLL's down to my local machine for testing.
I am getting an error that it can't instantiate the COM object because it is not registered but I KNOW it is registered because the DLL works on other parts of our website that are still in Classic ASP and will run on my local machine. I actually wrote a ASP script inside the the ColdFusion test site on my machine to test the DLL and everything works fine so it IS registered (via regsvr32.exe).
The ColdFusion page was done by an outside company that we are going to be breaking ties with and I don't have the password to their ColdFusion control panel even though it is on one of our servers. I wanted to look at their settings. Is there some setting that I need to set in the control panel on my machine? If there is I haven't found it yet.
Any ideas?
EDIT:
Here is the code:
<cfscript>
objEnc = CreateObject("com", "mycom.myclass");
</cfscript>
Also, I am running the 32-bit version of CF on a Windows 7 Pro 64-bit OS.
EDIT:
Another edit just for some more info:
The Windows 2008R2 server that it runs successfully on is a 64-bit server. So OS shouldn't have anything to do with it.
Should I try to find Version 9 developer edition on adobe's site and see if it works since it matches the CF version on the server? Haven't been able to find that yet and now Adobe just released 11.
After downgrading my local machine to ColdFusion 9 I can now access the COM DLL perfectly. Which is probably for the best since our server is running CF9. My testing will be with same version. Thanks for all you guy's input.
Randy

Use WebDav in Sharepoint 2010

I have done some research, based on the problem that my single server gives me when I try to open a document library in windows explorer from the ribbon menu item "Open in Windows Explorer".
The same problem occurs when I try to map sharepoint to a folder in windows explorer too.
The error is:
Your client does not support opening this list with Windows Explorer
From the net, suggestions are:
(Since I'm trying this operation from server itself) enable Desktop Experience
Install the KB907306 update.
Enable IIS webDav service (Some say, it's just for additional functions from the MS Whitepaper)
(Edit) Started webClient service
I've already done them. Nothing changed. Proper machine restart and iis too have done.
Need some serious advice.
Thanks in advance.
Not sure if we are having exactly the same problem BUT I have had similar problem while accessing SP via Windows Explorer in Windows Server 2k8.
What I done to fix it is following:
Install new server feature called Desktop Experience (it comes with WebDAV redirector, which allows you to connect to WebDAV) - Note: Server will need to be restarted.
In Services start WebClient service (go to properties and make sure it starts automatically)
You will now be able to access your sharepoint via entering network path such as \sharepointhost\application\myawesomeapplication\ etc.
Hope that helps.
If you are trying to do this from the server, test it from a server which is not on the SharePoint farm (or better yet, a client machine). Ensure all of your testing is done from machines which are not on the farm.
Do NOT enable the IIS WebDAV service, as SharePoint provides its own WebDAV service and the IIS one overrides it in the pipeline. Enabling this service is a sure path to breaking WebDAV.
If you have SSL enabled, you may be in for a rough time getting it to work. Start by understanding how to use the 'net use' command, and the #SSL suffix.
make sure your webdav is installed as feature
make the following registry fix (http://support.microsoft.com/kb/841215) :
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WebClient\Parameters
Add a new DWORD "BasicAuthLevel" and change this to "2"
Restart your machine (and make sure it is enabled in IIS)
Make sure that WebClient windows service is running in the server. This shall appear in client operating systems like Windows 7, windows 8 however, on the server operating systems like Windows Server 2008, it shall be installed by enabling the server feature "Desktop experience" using Server Manager
This issue nearly killed me. I found that I was using a 64 bit version of my browser and that is'nt supported. I changed over to the 32 bit and it works.