I have an asp app with C# back end. running .net 4.5. I am using  System.DirectoryServices.AccountManagement; and it compiles and runs fine straight out of VS, but when I publish it and go to the page I get an error 

Compilation Error
Description: An error occurred during the compilation of a resource required to service this request. Please review the following specific error details and modify your source code appropriately.

Compiler Error Message: CS0234: The type or namespace name 'AccountManagement' does not exist in the namespace 'System.DirectoryServices' (are you missing an assembly reference?)

Source Error:

Line 5: using System.Net;
Line 6: using System.Globalization;
Line 7: using System.DirectoryServices.AccountManagement;
Line 8: /// <summary>
Line 9: /// Summary description for ldapThirty

I have never seen this out side of VS. The reference is in the project. I am using 2017. I see there is an option to copy local, but I cant find it. Any help would be appreciated. 

Hello,

One of the ASP.NET websites that I am hosting in an IIS6 environment on a Windows 2003 server has this problem where every now and then the application pool has to be restarted because the site starts to show unexpected behavior. 

The following things happen:

• content is served only partially, with the missing parts replaced by gibberish.
• ASPX pages start throwing errors.
• There are errors in the SQL syntax of the queries that are run on the page.
• Stylesheets and other assets are suddenly not available anymore.

These problems appear on the same pages consistently. When I look into the code there is nothing irregular there.

When the application pool is restarted the application behaves normally again.

I had these results only on the production environment and never on the development or staging.

I was unable to find anything useful on the net, but I suspect that something in the application is causing it to become corrupted in this way.

The application does the following:

• run SQL queries.
• display DevExpress forms.
• generate PDF and Excel documents.

If someone has an idea what may be causing this I would be really grateful because I am completely stuck on this for months and so are my colleagues.

Thanks a lot for any replies!

I'm having a bit of trouble with getting an ASP.NET application to login to SQL Server using Windows Authentication.  IIS is passing machine credentials to the local installation of SQL Server (same VM) instead of the Application Pool Identity.  This is a site on IIS 10, connecting to SQL Server 2016, and running on Server 2016.  Prior to taking on this project, I have very little experience in IIS.  I've done Windows and Linux sysadmin work, but I have not worked with IIS. 

I understand what I'm trying to accomplish here, but my lack of IIS experience means there's probably something I'm missing.  I can see in SQL Server Logs on Windows logs tons of authentication failures with it trying to pass machine credentials (domain\machinename$) instead of the Application Pool Identity.  I would understand if this were a remote SQL instance, but it's on the same machine. 

I've followed what was laid out here: https://blogs.msdn.microsoft.com/ericparvin/2015/04/14/how-to-add-the-applicationpoolidentity-to-a-sql-server-login/

I've also read several posts from here, Stack Exchange, and Server Fault.  Task manager shows w3wp is running under the Application Pool Identity, not Network Service. I have set various settings in the IIS site configuration and application configurations. 

There is backstory to this.  I'm working with a network management application that I did not develop.  This is being set up as a standalone configuration with no domain and SQL Server installed locally.  The default configuration for this software out of the box violates several of our security policies.  Out of the box, this software creates a full user account added to the local Administrators group, sets the password never to expire, adds the account to about every account right it can, uses that account with admin rights to run the web application, creates a SQL Server user with the sysadmin role and dbo control over its databases, sets that password never to expire, and puts the unencrypted connection string in a few config files.  I have this now running under an IIS virtual account with only the permissions and rights it needs.  My next step is to get this site to use Windows Authentication instead of username/password.  I've created a login for the IIS virtual account and mapped it to the relevant databases.  I've set up the OBDC system DSNs to use Windows authentication and hunted through web.config and app.config files.  Using WIndows authentication is part of the security policy.  I noticed today that this application is not using connection strings in web.config files in the way I've seen it documented.  From what I have seen, it seems to store the database connection strings in a registry key but also relies on the ODBC configuration.  I have ventured a try at changing the connection strings there to have "Integrated Security=SSPI" or "Integrated Security=yes", but it still passes the machine credentials.  I believe the account that the software creates in the Administrators group can login via Windows Authentication.  I haven't gotten very much help from their support on this at this point.  I'd be grateful for someone with more experience that has some insight.

Window : Window Server 2008 R2 Standard

IIS version 7

After windows update. My company application sometime have problem. Checking Event log found Event ID 5009 & 5011 appeared during the time.

Event ID 5009 :


Event ID 5011 :


Any solution? Thanks

HI 

We've had this issue across 2 different instances of the same website (they're hosted on separate hardware, different OS and are in no way related).

The issue is that the IIS server is throwing a:

Server error in '/' Application. Stack trace is as follows:

The file '/Dashboard/Widgets/Widget.ascx' does not exist

This is a running server with no code changes over the past 1 year. On closer investigation it looks like the .NET framework has created a file called App_Web_widget.2caa704.dll.delete under the folder “C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files\root\1644ed21\6a29fba\assembly\dl3\a03785fe\002ec5a9_90e9d201

Renaming the ".delete" file to ".delete.old" gets the site working immediately.

The same error has occurred multiple times now under different instances with each time a different compiled DLL failing. And in each case a ".delete" file has been created within the Temporary .NET folder in different places.

Our investigation seems to conclude the following:

• 1) The “.NET cache” seems to have decided to update the code – which maybe incorrect as the code has never changed, but could also be IIS refreshing the files. We’re unclear of the nature of these refreshses
• 2) The refresh failed for whatever reason. Again, it is unclear why IIS could not update the DLL even though the files were available and permissions seem to be fine on these folders

So, what is causing running app cache to fail and why is it not completing the update of the code if it decides that the codebase needs to be update?

There also seems to be no way to raise a ticket with Microsoft for this issue rather than posting a thread here. support.microsoft.com does not even list IIS as a product under Windows Server in order for us to create a ticket

We are using IIS 6 SMTP relay to route mail through O365 for a few applications.  Have been doing so for 2 years with no trouble but recently, the SMTP relay has started sending multiple copies of an email if the recipients are in different email domains.  For example, one email has 3 recipients and they are jim@gmail.com,tom@outlook.com, and sarah@hotmail.com since they each have a different email domain, the relay server is sending it 3 times.  In the logging, you can see the relay open a new connection to O365 for each email domain and send the message.  Started happening around the Sept 13th 2018 timeframe.

This afternoon, one of our servers running 2008 R2 and IIS 6 started sending resets.  We were first alerted to the problem by a monitoring service that told us the connection was refused.  I dug into IIS and Windows Firewall logs and found that when the connection worked, IIS and the firewall both logged it as expected.  When the connection didn't work, neither of them logged it.

I logged into our hardware firewall/router and noticed the dropped connections were seen there, and were listed as being reset by the server.  I ran a packet capture on the IIS server and I was able to confirm that the packet comes in, and is immediately responded to with a reset most of the time.

I can find no logging as to why this might be the case.  We tried reverting the server to a backup from the previous day (when there were no issues), running on a separate physical host, and the issue persisted.

Any ideas?  I'm not sure what logs I would be able to look at since the reset happens immediately.  I don't think the firewall or IIS ever see the packet.

Thanks

Scriptkiddies giving me headaches. Having sometimes four or five attacks of this kind:

2018-11-24 07:36:25 192.168.2.35 GET /help.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:36:26 192.168.2.35 GET /java.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:36:25 192.168.2.35 GET /webdav/ - - 111.230.224.224 77.174.246.127:80 2
2018-11-24 07:36:25 192.168.2.35 PROPFIND / - - 111.230.224.224 localhost 1
2018-11-24 07:36:30 192.168.2.35 GET /_query.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:36:30 192.168.2.35 GET /test.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:36:32 192.168.2.35 GET /db_cts.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:36:32 192.168.2.35 GET /db_pma.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:36:32 192.168.2.35 GET /logon.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:36:33 192.168.2.35 GET /help-e.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:36:33 192.168.2.35 GET /license.php - - 111.230.224.224 77.174.246.127 50
2018-11-24 07:36:33 192.168.2.35 GET /log.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:36:34 192.168.2.35 GET /pmd_online.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:36:34 192.168.2.35 GET /hell.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:36:36 192.168.2.35 GET /x.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:36:36 192.168.2.35 GET /shell.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:36:36 192.168.2.35 GET /htdocs.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:36:37 192.168.2.35 GET /desktop.ini.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:36:39 192.168.2.35 GET /lala-dpr.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:36:37 192.168.2.35 GET /z.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:36:39 192.168.2.35 GET /wpc.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:36:39 192.168.2.35 GET /wpo.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:36:40 192.168.2.35 GET /wp-config.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:36:40 192.168.2.35 GET /text.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:36:42 192.168.2.35 GET /muhstik.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:36:42 192.168.2.35 GET /muhstiks.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:36:44 192.168.2.35 GET /lol.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:36:44 192.168.2.35 GET /uploader.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:36:44 192.168.2.35 GET /muhstik-dpr.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:36:45 192.168.2.35 GET /cmd.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:36:45 192.168.2.35 GET /cmx.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:36:45 192.168.2.35 GET /cmv.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:36:46 192.168.2.35 GET /cmdd.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:36:46 192.168.2.35 GET /knal.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:36:48 192.168.2.35 GET /shell.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:36:48 192.168.2.35 GET /appserv.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:36:48 192.168.2.35 GET /cmd.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:36:49 192.168.2.35 GET /scripts/setup.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:36:49 192.168.2.35 GET /phpmyadmin/scripts/setup.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:36:49 192.168.2.35 GET /phpMyAdmin/scripts/setup.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:36:50 192.168.2.35 GET /phpMyAdmin/scripts/db___.init.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:36:50 192.168.2.35 GET /phpmyadmin/scripts/db___.init.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:36:52 192.168.2.35 GET /plugins/weathermap/editor.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:36:52 192.168.2.35 GET /cacti/plugins/weathermap/editor.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:36:52 192.168.2.35 POST /wuwu11.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:36:54 192.168.2.35 POST /xw1.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:36:54 192.168.2.35 POST /xw.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:36:57 192.168.2.35 POST /wc.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:36:58 192.168.2.35 POST /xx.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:37:00 192.168.2.35 POST /w.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:37:00 192.168.2.35 POST /sheep.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:37:01 192.168.2.35 POST /db.init.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:37:00 192.168.2.35 POST /qaq.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:37:01 192.168.2.35 POST /db_session.init.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:37:01 192.168.2.35 POST /db__.init.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:37:03 192.168.2.35 POST /wp-admins.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:37:03 192.168.2.35 POST /m.php pbid=open - 111.230.224.224 77.174.246.127 2
2018-11-24 07:37:04 192.168.2.35 POST /db_desql.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:37:03 192.168.2.35 POST /db_dataml.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:37:04 192.168.2.35 POST /mx.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:37:04 192.168.2.35 POST /wshell.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:37:06 192.168.2.35 POST /xshell.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:37:06 192.168.2.35 POST /qq.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:37:08 192.168.2.35 POST /lindex.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:37:08 192.168.2.35 POST /phpstudy.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:37:09 192.168.2.35 POST /weixiao.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:37:08 192.168.2.35 POST /phpStudy.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:37:09 192.168.2.35 POST /feixiang.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:37:09 192.168.2.35 POST /ak47.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:37:11 192.168.2.35 POST /ak48.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:37:11 192.168.2.35 POST /xiao.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:37:11 192.168.2.35 POST /yao.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:37:13 192.168.2.35 POST /defect.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:37:13 192.168.2.35 POST /webslee.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:37:13 192.168.2.35 POST /q.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:37:14 192.168.2.35 POST /pe.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:37:16 192.168.2.35 POST /cainiao.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:37:16 192.168.2.35 POST /zuoshou.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:37:16 192.168.2.35 POST /zuo.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:37:17 192.168.2.35 POST /aotu.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:37:17 192.168.2.35 POST /bak.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:37:20 192.168.2.35 POST /l6.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:37:17 192.168.2.35 POST /cmd.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:37:20 192.168.2.35 POST /l7.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:37:20 192.168.2.35 POST /l8.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:37:22 192.168.2.35 POST /56.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:37:22 192.168.2.35 POST /q.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:37:22 192.168.2.35 POST /mz.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:37:23 192.168.2.35 POST /xx.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:37:23 192.168.2.35 POST /yumo.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:37:24 192.168.2.35 POST /min.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:37:27 192.168.2.35 POST /wan.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:37:27 192.168.2.35 POST /wanan.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:37:27 192.168.2.35 POST /ssaa.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:37:31 192.168.2.35 POST /aw.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:37:31 192.168.2.35 POST /12.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:37:32 192.168.2.35 POST /ak.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:37:31 192.168.2.35 POST /hh.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:37:35 192.168.2.35 POST /ip.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:37:35 192.168.2.35 POST /infoo.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:37:36 192.168.2.35 POST /qwe.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:37:36 192.168.2.35 POST /qq.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:37:36 192.168.2.35 POST /1213.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:37:38 192.168.2.35 POST /post.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:37:39 192.168.2.35 POST /aaaa.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:37:39 192.168.2.35 POST /h1.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:37:39 192.168.2.35 POST /test.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:37:41 192.168.2.35 POST /3.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:37:41 192.168.2.35 POST /phpinfi.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:37:41 192.168.2.35 POST /9510.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:37:44 192.168.2.35 POST /default.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:37:44 192.168.2.35 POST /sean.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:37:45 192.168.2.35 POST /help.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:37:44 192.168.2.35 POST /app.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:37:48 192.168.2.35 POST /miao.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:37:49 192.168.2.35 POST /xz.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:37:49 192.168.2.35 POST /linuxse.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:37:52 192.168.2.35 POST /zuoindex.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:37:52 192.168.2.35 POST /zshmindex.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:37:53 192.168.2.35 POST /ceshi.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:37:52 192.168.2.35 POST /tomcat.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:37:53 192.168.2.35 POST /1hou.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:37:55 192.168.2.35 POST /ou2.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:37:55 192.168.2.35 POST /zuos.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:37:55 192.168.2.35 POST /zuoss.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:37:56 192.168.2.35 POST /zuoshss.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:37:59 192.168.2.35 POST /she.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:37:59 192.168.2.35 POST /s.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:38:01 192.168.2.35 POST /test.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:38:01 192.168.2.35 POST /qw.php - - 111.230.224.224 77.174.246.127 2
2018-11-24 07:38:01 192.168.2.35 POST /caonma.php - - 111.230.224.224 77.174.246.127 2

[endquote]

Always there's that errorcode 2 at the end. Am I safe or can I taken countermeasures to prevent these attacks?

I'm used debug diag 1.2 to troubleshooting my high cpu problems.

All work fine and the report is generated and openned on Internet Explorer. The problems is i can navigate throw the table of content. When i click on an element, nothing appears.

I have an application that is being migrated from server 2008 to server 2016.  The files including the web.config have been copied from one server to the other.  I have converted the application in IIS and set the authentication.  A test html page was added to the project to verify the connection.  IT WORKS! The other pages .aspx in the project don't work.  The event viewer has the following entry.

Event code: 3005

Event message: An unhandled exception has occurred.

Event time: 12/14/2018 11:25:14 AM

Event time (UTC): 12/14/2018 7:25:14 PM

Event ID: 740c301e8c5648d881192a0d07e694f0

Event sequence: 35

Event occurrence: 1

Event detail code: 0

Exception information:

Exception type: FormatException

Exception message: Input string was not in a correct format.

at System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal)

at System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info)

at System.String.System.IConvertible.ToInt32(IFormatProvider provider)

at ASP.global_asax.Session_End(Object sender, EventArgs e)

Thread information:

Thread ID: 27

Is impersonating: False

Stack trace: at System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal)

at System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info)

at System.String.System.IConvertible.ToInt32(IFormatProvider provider)

at ASP.global_asax.Session_End(Object sender, EventArgs e)

Hello, I have inherited and IIS6  running a Virtual STMP server from which our App relays emails through.

Some iPhone users have commented that the HTML emails they should be receiving are coming thought as "quoted-printable".

I cannot see what I need to change to stop this.

There is only customer using the app that has commneted on having the problem, and it's not all iPhone user (some of them receive the email fine).

Android, windows, and MAC users seem fine also.

I've checked the email headers, and, it's going through office 365 mail protection. I can also NOT see 

Content-Transfer-Encoding: quoted-printable

I am at a loss as to why some would work, and others not.

has anyone else experienced the same issue, and care to share their solution ?

Thanks

I'm setting up a new dedicated server using Windows Server 2019. It's replacing an old one based on Windows Server 2008 R2. I have had the built-in SMTP server running on the old server with no issues. I have set up the new server to act as an SMTP server as well, using my own notes from setting up the old one, as well as double checking intructions online. Basically according to the instructions here:

http://www.vsysad.com/2017/05/install-and-configure-smtp-server-on-windows-server-2016/

It's pretty much the simplest setup possible, just using the SMTP server locally (only allows connections from 127.0.0.1) with anonymous access enabled.

The problem I'm having is that e-mail will not leave C:\inetpub\mailroot\Queue and will never reach the recipients. The Windows event log contains the following warning(s):

Event 4006, smtpsvc
"Message delivery to the host '204.79.197.212' failed while delivering to the remote domain 'hotmail.com' for the following reason: The remote server did not respond to a connection attempt."

The above is just an example using a Hotmail destination address. The same kind of message is received when trying to send to addresses on other domains.

What I've tried:

1. I have sent e-mail manually by using Telnet. The e-mail is created and received by the local SMTP server without issues, but doesn't leave the queue folder.
2. I have run SmtpDiag against both a Hotmail and a Gmail address. No issues. The MX records are listed as expected.
3. I have used Nslookup and confirmed that the MX records are resolved.
4. I have successfully connected to the Hotmail and Gmail SMTP servers using Telnet.
5. I have used Wireshark and been able to see that my server actually tries to access the IP address of the destination e-mail address domain, at port 25. So, for Hotmail, it simply resolves the IP address of hotmail.com (which is 204.79.197.212) and tries to open a connection to this address at port 25. This obviously fails, as there's no SMTP server there. My server never even attempts to access the SMTP server at the address specified in the MX record!

That last item above also ties into an interesting thing that I noticed, which is that the IP address listed in the event 4006 log message is not one of the IP addresses listed in the MX records. It is the IP address of the actual hotmail.com domain (or the IP of any other domain I try to send to). So, why is it attempting to contact the domain in the e-mail address and not one of the addresses listed in the MX records?

To futher investigate, I used Telnet to send to an e-mail in one of my own domains. Sure enough, I find a 4006 event in the log saying:

"Message delivery to the host '[my domain's IP]' failed while delivering to the remote domain '[my domain]' for the following reason: The connection was dropped by the remote host."

It again appears that the SMTP server is trying to connect to my domain's IP and port 25 and not to the address specified in the MX record.

This is as far as I've come. Maybe I'm misinterpreting something here, but it certainly looks like Windows' SMTP server is trying to connect to the e-mail address' domain directly at port 25 (ignoring MX records)... Any ideas on what I might be doing wrong or perhaps how I should proceed in troubleshooting this?

Hi guys, I have a big problem with a web service soap in php 7.2. everything works very well with requests up to about 40kb. With requests above this dimension, usually with attached PDFs, the request remains pending until the timeout. Of these timeouts I can not find a trace in the failed request trace. In the c: / windows / temp folder I also find all these requests of various sizes, from 40kb to few mb truncated in the last lines of the file. I raised all the possible values ​​in the configuration editor, but I could not solve it

EDIT: Wrong section, i ve IIS 8.5 and windows server 2012R

Hello, 

I do not have much experience with this, but there is nobody else.  I have a client that has voicemail going to email that stopped working after a storm that knocked out power.  The last time this happened, scan to email went down too.  Restarting SMTP services fixed the issue.  This time, the scan to email started working again but not voicemail to email.  Voicemail getting this error: 554+5.2.0+STOREDRV.Submission.Exception:SendAsDeniedException.MapiExceptionSendAsDenied  In the Mitel application we have,voicemail@XXX.com is the sendas.  I don't think any settings would have changed so it would seem to be server side.  

I have put two pictures at this link: https://imgur.com/a/L76uQxD  The first picture is when it was working and the second picture is after it stopped working.  The noticiable difference in the second picture is that 25 has changed to 0.  I would think that the SMTP port has an issue, but Scanning still works.  Also,scanner@xxx.com has an account on office365 butvoicemail@xxx.com doesn't and doesn't appear to ever have.  All settings IIS 6.0 look correct but I can answer any questions and appreciate any input.  

Thanks,

-ZP

Hello All,

Disabled TLS 1.0 and 1.1 at registry level in the web server but iis site hosted in web server is still accessing through TLS1.0 and 1.1

We have checked through browser as well as through open ssl command in putty.

Can you please help me where it is going wrong?

Thanks

I am new to managing IIS.

One of our web services is run by it's own Application Pool.

It takes the requests, runs a SQL query, and returns some JSON.
Roughly once to twice a month the service will seemingly freeze, and stop responding to requests.

IIS reports the app pool as running, and no log that I know of reports an error.
Restarting the app pool solves the problem, until it decides to hang again.

I have tested requests to the service that I logged as occurring shortly before I believe the  app pool froze, but have been unable to duplicate the problem purposefully.

Per some colleague's advice, as they have a similar problem, I have started a task that regularly restarts the app pool.

Is there a way to tell exactly what request - if that is indeed the cause - is causing the app pool to hang?

Are there any causes that might be easy to test for?

Using IIS 6.0, SMTP Virtual Server, we are able to send without issue, but when sending to an invalid email address, we are not receiving the NDR in the inbox of the Reply-To address. This only happens when we configure the Reply-To address to be a Microsoft Exchange email account. I have tested this using an email group, and a single-user email inbox, but both tests yielded the same results. I have been in communication with Microsoft Support for a week regarding this issue, and they have simply stopped offering more help beyond referring me to other Microsoft Support avenues, i.e. the forum, or signing up for a support package. I have plenty of logs to share, but am unwilling to post them on a public forum. Please provide an address to which I can forward those logs in your reply. Thank you.

Hi,

in the Event Viewer of the IIS server I find Warnings of the type:

"Message delivery to the host 'XXX.XXX.XXX.XXX' failed while delivering to the remote domain 'xxxx ****.' for the following reason: The remote SMTP service does not support TLS.The SMTP verb which caused the error is 'STARTTLS'. "

EventID: 4007

Configuration of the Virtual Servers of the IIS is correct, I think, but some domains do not reach the mails.

Any suggestions?

Regards,

Hi,

I have an IIS 6.0 (with 3 SMTP virtual servers) installed on Windows Server 2016. 

Issue: memory (RAM) is always increasing till 100%. Then I just can restart IIS. Hours later, it happens same.

Any idea?

Thanks

[ yesterday]

Iv'e been using IIS and asp.net for several years now, and this one stumped me.  I built some simple changes in a website (vs 2010) and the single assembly for the website works fine when built to a folder that my local IIS (v 7) is mapped to.  This works fine, but when I copied the same dll to a folder on a test server (running IIS6 with .net 4.0), the app domainSHOULD have refreshed since the dll SHOULD have been seen as different, correct?

After several iterations of build, recycle the app pool, cleaning the temp asp.net files, copying over the dll, test the site, rinse and repeat....the dll changesFINALLY showed themselves.  What gives?

I dont recally having this much trouble with deploying changes to IIS6 in the past.  

[today]
This morning, after going through a few more iterations, I think I know what my problem was. I need to do a VIsual Studio REBUILD, not just BUILD.  One clue all along that my app domain was infact restarting, was that I would have to re-login to the app because the session had been terminated.  So after all my headaches, it was something as simple as this.  Everytime I do a make changes, do a rebuild (not just build), and then copy over the dll, the changes show up correctly on the IIS6 box.  Ok, so now Im still wondering why this wasnt a problem with my local instance of IIS7....hmmm