Was looking for ways to generate synthetic test data for a SharePoint out-of-the-box install today, and ran into the SharePoint 2010 Load Testing Kit. While it doesn’t help me in this stage of the project, I could see it being useful later or on other projects.
There appears to be a lot of dependencies though:
Could be hot though!
To setup the crawl configuration for the default local sites, you can use the script below:
$ssaName="Search Service Application" $context=[Microsoft.Office.Server.Search.Administration.SearchContext]::GetContext($ssaName) $incremental=New-Object Microsoft.Office.Server.Search.Administration.DailySchedule($context) $incremental.BeginDay="23" $incremental.BeginMonth="10" $incremental.BeginYear="2011" $incremental.StartHour="0" $incremental.StartMinute="00" $incremental.DaysInterval="1" $incremental.RepeatInterval="720" $incremental.RepeatDuration="1440" $fullCrawl=New-Object Microsoft.Office.Server.Search.Administration.WeeklySchedule($context) $fullCrawl.BeginDay="23" $fullCrawl.BeginMonth="10" $fullCrawl.BeginYear="2011" $fullCrawl.StartHour="6" $fullCrawl.StartMinute="00" $fullCrawl.WeeksInterval="1" $contentsource = Get-SPEnterpriseSearchCrawlContentSource -SearchApplication $ssaName -Identity "Local SharePoint Sites" $contentsource.IncrementalCrawlSchedule=$incremental $contentsource.FullCrawlSchedule=$fullCrawl $contentsource.Update()
Last week I was beating my head against the table, because a VM I had quickly created wasn’t allowing SQL to install. I kept receiving the following error in the detailed SQL error log:
Configuration action failed for feature SQL_Engine_Core_Inst during timing ConfigRC and scenario ConfigRC.
External component has thrown an exception.
The configuration failure category of current exception is ConfigurationFailure
Configuration action failed for feature SQL_Engine_Core_Inst during timing ConfigRC and scenario ConfigRC.
System.Runtime.InteropServices.SEHException: External component has thrown an exception.
at Microsoft.Win32.SafeNativeMethods.CloseHandle(IntPtr handle)
at System.Runtime.InteropServices.SafeHandle.InternalDispose()
at System.Runtime.InteropServices.SafeHandle.Dispose(Boolean disposing)
at System.Diagnostics.Process.Close()
at System.Diagnostics.Process.Dispose(Boolean disposing)
at System.ComponentModel.Component.Dispose()
at Microsoft.SqlServer.Configuration.SqlEngine.SqlServerServiceBase.WaitSqlServerStart(Process processSql)
at Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineDBStartConfig.ConfigSQLServerSystemDatabases(EffectiveProperties properties, Boolean isConfiguringTemplateDBs, Boolean useInstallInputs)
at Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineDBStartConfig.DoCommonDBStartConfig(ConfigActionTiming timing)
at Microsoft.SqlServer.Configuration.SqlConfigBase.SlpConfigAction.ExecuteAction(String actionId)
at Microsoft.SqlServer.Configuration.SqlConfigBase.SlpConfigAction.Execute(String actionId, TextWriter errorStream)
Exception: System.Runtime.InteropServices.SEHException.
Source: System.
Message: External component has thrown an exception.
It turns out that I accidentally downloaded the debug check build version of Windows 2008 R2 SP1, and well, you can’t install SQL with that version. Needless to say, the error message makes this completely obvious. Found the hint to look at the ISO I was using on MSDN social.
Just throwing this down as finding this math or an explanation of it has eluded us until we actually could do it based on paystubs. LAFHA is an in/out transaction (deduction and then addition).
With the application that I’m helping “make fast” one of the optimizations identified by an architect was to use net.pipe or net.tcp on the application tier. This was because the services on that tier call into each other, and waste a lot of time doing all the encapsulation that comes with wsHttpBinding.
We had tried to first use net.pipe because it is incredibly fast and it is all local. However, because of how they do security here, it didn’t work. Next up, net.tcp.
Overall, it wasn’t that difficult to setup the services with dual bindings (wsHttpBinding for calls from other servers and net.tcp for calls originating from the same server). Granted, there were a lot of changes, and since all the configs are manually done here, was very error-prone. I will be glad not to do any detailed configurations for a while.
Anyways, we did our testing of the build that incorporated it through 3 different environments, and over the weekend it went into Production. Of course, that is when the issues started.
Bright and early Monday morning, users were presented with a nice 500 error after they logged into the application. On the App tier servers we were getting the following error in the Application event log with every request to the services:
Log Name: Application Source: ASP.NET 4.0.30319.0 Event ID: 1088 Task Category: None Level: Error Keywords: Classic User: N/A Description: Failed to execute request because the App-Domain could not be created. Error: 0x8000ffff Catastrophic failure
Well, since it mentioned the App Domain, we ran an IISReset and all was well. I didn’t think too much into it at the time and only did some cursory searching as it was the first time we saw it. However, today it happened again.
Our app is consistently used between 7AM and about 7PM, but during the night it isn’t used at all. This is when the appPool is scheduled to be recycled (3AM). It had appeared as if the recycle was what was killing us, as only the App Domain is recycled and not the complete worker process.
Immediately we had the guys here remove the nightly recycle and change it to a full IISReset. At least that way we had a workaround until we could determine the actual root cause, come up with a fix, and test said fix. However, it didn’t take long to determine the actual root cause…
One of the interesting things about this issue, was after it started happening in Production, a few of the other environments started exhibiting similar symptoms: Prod-Like and a smaller, sandbox environment. Mind you, neither of these environments had these issues during testing.
So, I took some time to dive in and actually figure out the problem. At first I thought it was because there were some metabase misconfigurations in these environments. I wouldn’t say that all of these environments were pristine, nor consistent between each other. I found a few things, but nothing really stood out…until…
While I was doing diffs against the various applicationHost.config files, NotePad++ told me it had been edited and needed to be refreshed (them removing the appPool recycles). However, as soon as this happened the 500 errors started. It didn’t help they did both machines at the same time which took down the whole application, but that’s another story.
This led me to believe that it wasn’t something within the configuration, but it also showed me how to reproduce it, at least part way. The part that I was missing was that I had to first hit the website to invoke the services and then change the configs causing an app domain recycle.
Then I attempted to connect to the worker process with windbg to see what it was doing. However, that was a complete failure as nothing actually happened to the process. No exceptions being thrown, no threads stuck, etc. It appeared to just sit there.
A bit of searching later led me to an article that had the exact same issues we were having, and that changing from a Classic to Integrated appPool fixed it. However, it didn’t mention why. Of course I tried it and it worked. To appease the customer’s inquiries I knew I needed to find out why though.
I still don’t have a great solution, but apparently net.tcp and WAS activation has to be done in Integrated mode. If it isn’t, you get the 500 error. But ours works fine until the app domain is recycled. Well, according to SantoshOnline, “if you are using netTcpBinding along with wsHttpBinding on IIS7 with application pool running in Classic Mode, you may notice the ‘Server Application Unavailable’ errors. This happens if the first request to the application pool is served for a request coming over netTcpBinding. However if the first request for the application pool comes for an http resource served by .net framework, you will not notice this issue.”
That would’ve been nice to know from Microsoft’s article on it, or at least a few more details. I remember reading an article about the differences between Integrated and Classic, but I sure don’t remember anything specific to this.
Anyways, hope this helps someone who runs into the same issue…
This may seem silly to some of you, but I am still getting used to Windows 2008. Sadly, I don’t spend as much time actually administering servers as I used to (silly management), so it usually takes me a bit longer to make my way around 2008 than 2003. I like to think they made everything more complex, but for some reason I’m sure I’ll get booed about that.
Anyways, this morning I was attempting to setup some performance alerts on some servers we’re having issues with. Basically I wanted to have it email us when it reached a certain threshold. No big deal, thinking I had this, I created the email app, created a performance counter, and then manually added it in.
Needless to say that didn’t work. It took me awhile to figure out why too as my little email utility worked fine. So I began a new search in order to find out how stupid I was being.
Turns out, quite a lot of stupid. Instead of using the utility, you can now use scheduled task items…which includes an email action! I basically used the instructions over at Sam Martin’s blog, which, I may add, he posted about in April of this year. I’m not the only n00b. Plus, who doesn’t have an enterprise system that deals with this sort of stuff already (at least at the types of clients I work with)?
Perfmon
Done!
Since the performance counter was set to an application pool, whenever that pool disappears (IISReset, idle timeout, etc.) the counter stops.
Currently Reading (could take awhile): [amazon_image id=”B000QCS8TW” link=”true” target=”_blank” size=”medium” ]A Game of Thrones: A Song of Ice and Fire: Book One[/amazon_image]
We are doing some document uploading to SharePoint, and needed some test files of various sizes. If you have Visual Studio installed, you have the tools required to make these files. Just make sure you run as administrator, and use the following command.
FSUTIL FILE CREATENEW 100MBTest.mdb 104857600 Usage: FSUTIL FILE CREATENEW [Filename] [Size in bytes]
We were having a specific issue in our Dev and QA environments where K2 was consuming over 16GB of disk space, and subsequently causing our server to run out of disk space. We had an interim workaround of restarting the K2 service, but within a day of testing, it was possible that K2 would eat it all up again.
This was happening because workflow instances (cases in our example) are tied to specific versions of the workflow. Similar to .NET websites, in order for you to use a specific version it has to do a lot of pre-compiling. Now, I’m not sure why it was using so much disk space per version, but that is essentially what was causing all our issues.
There are a few things that could’ve made this better:
Turns out option #2 reduces the space an individual version uses by orders of magnitude. Sadly, there is no way to retrofit the processes that are actually already in K2.
The actual solution is to use some of the new APIs, specifically the Live Instance Management APIs (oh and that took awhile to find via searching). The downside is that these APIs were added in 4.5, so anyone on a version prior to that is screwed. Thankfully we were on 4.5.1!
Anyways, if you’re lazy, there is actually an already created utility on K2 Underground, and you can find out some additional info about it too.
Just be prepared for it not to work all that great. We received a ton of Null Reference errors while running the utility against our large database. It seemed to work fine in our POC, but not against the real thing. Some cases were changed, but not all, and we still had the same issue.
In the end, we had to manually go and delete the old cases in K2, which is definitely not supported. However, our app handles it gracefully, so it wasn’t a huge deal.
The folder gets large, but that is because of all the patches that are applied to your installation. Do not simply delete the files, because it could cause all sorts of havoc. The only way to actually reduce the size somewhat, is to have Windows remove any previous updates after you install a service pack. You can do this with the following command. I was able to clean up 4GB using the command. Nothing major, but amost 25% improvement.
dism /online /cleanup-image /spsuperseded
Run as administrator.
I’ve always hated creating self-signed SSL certs. It never seemed like there was a good and easy way to accomplish this. Yes, you could download the II6 Resource Kit, but that’s just one more thing I don’t need on my machine.
Well, in IIS7, there is actually an option to automatically create one. Technet has a good walkthrough of it. However, there are some limitations:
Thankfully a remake of SelfSSL was created for IIS7 and it is more powerful, and easier to use. Take a look at Thomas Deml’s post on it to see the syntax and download the program. I’ve also uploaded it here, just in case anything happens to that site.