Here is a link to the slides from a presentation I did this past week to the Web Server Team at work on AJAX, JSON, and REST.
This is a presentation I created last year for work about HTML5. It’s often used a buzzword so I wanted to tell the story of the web and demonstrate why it matters and how it can be used to both a tech and non-tech audience.
I registered this domain a while back and figured it was finally time to put something up. Enjoy with a modern browser!
I recently finished developing a site for my friend Colin. He’s an artist and needed a way to easily post to his site and display his work so I used WordPress and created a custom template. Check it out … www.colinmatthes.com.
My VPC C:\ drive is full so I created a second partition X:\ with the remaining space leftover. I moved over all my Visual Studio projects to X:\ & remapped my Virtual Directories in IIS. Thinking there might be drive references inside project / solution related meta data files I checked the .sln file contents & the .csproj file contents but found no drive references as far as where the project file is located. However, when I tried to open up the solution in Visual Studio I received the following error when it tried to open the two web projects in the solution:
“Unable to read the project file xxxx. The system cannot find the path specified.”
After searching around online for a while I found that solution.suo file contains references but you cannot edit them via Notepad.
A co-worker of mine recently rebuilt our web server according to MSIB documentation from Microsoft (Windows 2003). When he put the server live everything worked great except for the final step in the order process on our e-commerce website (powered by Microsoft Commerce Server). We’ve had issues at the SaveAsOrder step before but it was related to the web server having the same CID as the database server (see my previous post). However, this time the CIDs were unique so that wasn’t the issue. After some extensive troubleshooting Rob was able to find the issue.
The SaveAsOrder() failure was related to a MSDTC security configuration specific to W2K3 servers which is under “Start – Administration Tools – Component Services – Computers – My Computer – Properties”. Within the properties window, there is a setting under “MSDTC – Security Configuration” to specify “No Authentication Required”. Originally, the setting was set to”Mutual Authentication Required”. This google post helped lead to the solution.
If you change the IP of a server in a domain you may need to flush the DNS cache in order for the change to take affect. To do this open up a command window and type:
One of the issues I’ve had to deal with extensively in our server environment is low disk space. The servers were built with the C:\ drives being far too small to accommodate the MSIB (MCMS/CS) environment and since MCMS creates temp files during content exports you can encounter many cryptic error messages. Today was the first time I came across these errors during the content export:
1) Error Window Title: NRProgress
Error Message: Run-time error ’402′: Must close or hide topmost modal form first
followed by . . .
2) Error: 0
Description: Automation error
The callee (server [not server application]) is not available and disappeared; all connections are invalid. The call may have executed.
Debug info: N/A
Extra info: N/A
Client Source: CProgressHelper::EndProgress
Recommended Action: N/A
followed by . . .
3) Error Window Title: Framework
Error Message: Unhandled exception occurred during FireEvent: EventName = Is, ModFlag = Is
As part of the export process MCMS creates temp .sdo files in the cache folder (rdonlyres). They look something like: SD-021D67F4-D658-4DE2-8644-6A1193DCAFEF-31425.SDO. If these start to fill up the cache folder and exceed the defined limit of cache in the Server Configuration Application then exports will start to fail (exhibiting the errors I mention above).
So if you are tight on space on your C:\ drive (and your MCMS instance is also located on C:\) you will want to delete these temp .sdos after each export.
Written in VB ….
Microsoft & Free … two words perhaps not thought to co-exist.