Permalink problem, please help

I just setp up a blog (https://www.cenksonmezsoy.com) with hosting from godaddy. I apparently selected the windows option instead of linux and when I change my permalink structure, the code WordPress provides is for a web.config file and NOT a htaccess file as I am used to in my other blogs. I thought a web.config file was created just like a htaccess so I went ahead and input the code in a text file and renamed it web.config, but that doesn’t work. After I upload it via ftp program, it displays web.config.txt as the file name no matter what I do. So I am back to the ugly permalink structure but now there’s another problem. The website is giving the below error message every other hour especially if I am posting or playing around editing posts. It goes back to normal after 10 minutes but it is annoying. Does anyone know how to solve this problem without switching to a linux server (which is a huge headache for me). Here’s the error message displayed on a hourly basis (not sure if it’s related me playing with the permalink but I need a web.config file to display the error message in detail as well):

Server Error in ‘/’ Application.
Runtime Error
Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a “web.config” configuration file located in the root directory of the current web application. This <customErrors> tag should then have its “mode” attribute set to “Off”.

<!– Web.Config Configuration File –>

<configuration>
<system.web>
<customErrors mode=”Off”/>
</system.web>
</configuration>

Notes: The current error page you are seeing can be replaced by a custom error page by modifying the “defaultRedirect” attribute of the application’s <customErrors> configuration tag to point to a custom error page URL.

<!– Web.Config Configuration File –>

<configuration>
<system.web>
<customErrors mode=”RemoteOnly” defaultRedirect=”mycustompage.htm”/>
</system.web>
</configuration>