Aren B's questions

I've been trying to get my TFS (2010) environment to play nice for the last couple days but have been getting this error after using the TFS server a little while:

The Underlying connection was closed: An unexpected error occurred on a receive. / An existing connection was forcibly closed by the remote host.

I can't figure out why the TFS server will work flawlessly for a while, and then on a whim just decide to kick this out everywhere.

From Dynamics AX 2012 Developer Environment:

From Visual Studio 2010:

However here's the confusing part, neither the TFS Server or the Client computer have any errors/warnings in the Event Log. Additionally, the Web Portal can be accessed for the TFS Server:

Google searches don't really bring up much useful information. I found this article which prettymuch describes a similar problem, but I'm not using an ISA Server, so the solution isn't valid.

The majority of the remaining results involve a similar but different error with SSL Self-Signed Certs. The error is happening on a non-ssl port, and our SSL port (8081) has a proper Authority Signed SSL Certificate.

I'm running out of ideas, I need to be able to get my TFS consistent. The installation was smooth and simple, no bumps, just a little hurdle to get it to use a FQDN but after that was done the TFS server was usable, creating Team Projects / Etc.. No issues until it decides to kill all inbound connections with no reason/warning/log.

Here's a snapshot of my TFS Settings:

Does anyone know where I can look for more information, what might be happening or what I might be doing wrong here?

I've got the following websites set up:

• UpgradingSite - DefaultAppPool - d:\sites\upgrading - no host header (binding:80)
• Beta Site - BetaAppPool - d:\sites\beta - beta.mysite.com (binding:80)

The setup was made to have Beta Site serve when it's up, but when I disable the site, the upgrading site would take over. This also was done to have something nicer show up if the site ever accidentally got shut down.

Deploy sequence is as follows:

1. Disable Beta Site Website in IIS (Making the Upgrading page visible)
2. Pull down latest changes
3. Run build scripts
4. Enable Beta Site
5. Open IE & Warm up site. (2ish minutes)

Here's the problem:

I need a way to warm the site up while Beta Site is not enabled, however I cannot actually hit the site (since it's disabled). I don't want the site to be enabled till it's available because we don't want our beta users to experience the long load associated with a warm up cycle.

There was a really cool IIS module that did something like this but it's been discontinued and no longer supported.

Any ideas?

Let me clarify. When i meant disabled, I was talking the website entry (endpoint if you will), not the app pool.

The idea is to warm the site up while serving the updating page to users. Once the site is warm and good, then it would flip the switch to allow beta.mysite.com to be served by the now warmed app pool.

I know about scripts to pre-warm by calling pages, but I cannot call pages if the endpoint is down (So the upgrade page/site would still serve users while the site is being warmed up by the script)

I've got a application I've recently ported From IIS6 (Windows 2003) (7 Classic Pipeline) to IIS7 (Windows 2008) Integrated Pipeline.

The problem I've noticed is password hashes built on the IIS6 system no longer match when we try to log in on the IIS7 system. However, when we re-generate the hash on the IIS7 system, it works fine.

I read somewhere that there are differences in the cryptographic systems between the two (2003/2008) and thier respective IIS versions, but I couldn't find any additional information.

I'm at a loss here, I need existing hashes to work on the new system and I can't seem to find an starting point.

If anyone knows of any resources that may help with this, or a setting or something, I'd be greatly appreciative.

I am trying to migrate specific tables entire dataset from my DEV machine to our staging machine. (Has all the basic starting data for this feature).

Essentially what I want to do is akin to the backup/restore operation for databases, but I only want to do this for a select couple of tables in my database.

Is this possible? I've searched long and hard for MSSQL -> MSSQL Table Migration or export/import and I've come up with not a lot.

I've got a 2k8 router working here, and it works great for the most part. I own a domain hosted at a remote datacenter and I'd like to override part of it. Let me explain:

www.mydomain.com is my Website staging.mydomain.com is my Website's live staging copy hosted @ my DC, it's got pretty rigid accept/deny rules to lock it down to specific ips and whatnot.

beta.mydomain.com is an internal name that our internal development servers use to distinguish the site. (VirtualHost).

I'd like to override the dns for just beta.mydomain.com but i can't seem to figure out a way to do it without overriding the entire .mydomain.com record.

Any thoughts?

Related to my post here on SO:

https://stackoverflow.com/questions/3638584/smtpclient-sending-bad-messageids/3638682#3638682

It was brought to my attention that our exchange settings may be incorrect.

Overview

The messages sent by the emailer (SMTP) have incorrect MessageID headers.

Message-ID: <98bcd4e6-be30-4b22-8026-6047c8231b1f>

Where they should look something like this:

Message-ID: <F09A215A213060419E28A88E85FDC8FD0CCEB91C23@EXCHANGE-SERVER.MYDOMAIN.mycompany.com>

I'm assuming one of our settings are incorrect, anyone know what needs to change?

I've got this small problem, I've got a HG repository server set up and it works fine (at least as far as being a repository & working with HG)

I'm having a problem with the web view because it seems my server wont serve .cs or .csproject files (even though it technically isn't from the context of the hg web view)

My first instinct was to add the MIME type to the server as you can see here:

(I've added it at the root webserver level so all sites inherit it)

Anyway, after restarting the IIS Service / App pools / etc... It still is unable to serve .cs files

• http://myinternalserver/blah.txt Serves fine
• http://myinternalserver/blah.cs 404's

Am I missing a step here? Is there something funky about a .cs file? It doesn't make sense that it'd be a special type flagged as an "executable" or something because frankly .bat is servable, and it's way more prone to execution that an uncompiled C# file.

Anyone have ideas? Am I just going about this horribly wrong?