BizTalk, Technical

Rename BizTalk 2006 Server (Details)

I posted about this previously, but I wanted to post the steps I used to actually rename the server.

  • Open BizTalk Server Configuration and Unconfigure all features
  • Exit the BizTalk Server Configuration
  • Open SQL Server Management Studio and connect to the server
  • Expand your server in the Object Explorer and expand the Notification Services node
  • Right click on the BAMAlerts instance and select Disable
  • Right click on the BAMAlerts instance and select Stop
  • Right click on the BAMAlerts instance, point to Tasks, and then select Unregister
  • Right click on the BAMAlerts instance, point to Tasks, and then select Delete
  • In the Object Explorer click on the Databases node
  • In the Summary tab on the right of the screen, highlight all databases (do not highlight System Databases or Database Snapshots)
  • Right click on the highlighted databases and select “Delete”
  • The Delete Objects screen will appear, as shown below. Ensure the options are selected as shown in this screenshot, and click OK
    • If you receive any errors while deleting databases, expand the Management – Activity Monitor option under your SQL server in Object Explorer and kill any processes running against the database you’re trying to delete
  • In Object Explorer, expand Security – Logins and delete all logins used by the previously deleted databases
  • Close the SQL Server Management Studio
  • Change computer name
  • Restart and log in (ignore any failed service startup messages)
  • Open SQL Server Management Studio and connect to server using new computer name assigned above
  • Open a New Query Window (click the New Query button in the toolbar)
  • Enter the following commands, replacing <old_name> and <new_name> with the old and new computer names, respectively
    sp_dropserver ‘<old_name>’
    GO
    sp_addserver ‘<new_name>’, ‘local’
    GO
  • Execute the commands by clicking the “Execute” button in the toolbar or hitting F5 on your keyboard
    • If you receive any errors during the sp_dropserver command, execute sp_helpserver and copy the value of network_name for the <old_name> server and paste it into your sp_dropserver parameter, including any spaces
  • Restart SQL Server (Right-click on your server under the Object Explorer and select “Restart”), ignoring any errors that appear
  • Open Internet Information Services (IIS) from the Start menu
    • Expand Web Sites, Default Web Site and delete the BAM application (if it’s not there, move on to the next step)
    • Expand Application Pools and delete the BAMAppPool (if it’s not there, move on to the next step)
  • Open BizTalk Server Configuration from the Start menu
  • Perform a Basic Configuration using your new computer name as the Database server name and a current local account as the username for the service credential
    • When the configuration is complete review the results to ensure all features were successfully configured. If any failed, there will be a red “X” next to the failed feature.
    • Any failed features will need to be manually configured, so ensure the option to launch the custom configuration is checked before closing the wizard
    • For each failed feature, click on the option in the left pane of the configuration screen and configure the options in the right pane. Usually, the configuration involves setting a username and password for a service.
  • Once the configuration is complete, export the configuration and save the file
  • Open BizTalk 2006 Administration Console
    • Expand BizTalk Server 2006 Administration and right-click on the BizTalk Group for <old_name> and select Remove (If the BizTalk Group shown is already using your new computer name skip this step)
    • Right-click on BizTalk Server 2006 Administration and select “Connect to Existing Group”
    • Select your new SQL Server
    • Select the database (BizTalkMgmtDb)
    • Click OK
  • Restart the machine

Turn on automatic updates and download and apply any available updates

Technical

Posting With Word 2007

Ok, that was a bit more work than I thought. I wanted to figure out how to post from Word since I have some cool documents with pictures in them I wanted to add to my blog. I knew Word had the blogging capability so I dove in. It wasn’t very easy and took a lot of trial and error. Publishing text wasn’t a problem, it was the images that caused issues.

First I tried using the Community Server provider pointing to my metablog.ashx service. Error.
Next I tried changing to FTP. Error (permissions issue I never figured out.)
Rinse, repeat, change small things each time…Error.

Actually, the trial and error didn’t do squat. What did help was finding a posting on codesecurely.org on Blogging from Microsoft Word. There’s a bug in Word 2007 in its call to metablog that needed to be corrected.  Once I fired up Fiddler and made the changes he recommended to intercept the service call, and changed Word to not use Community Server as the provider, it worked like a charm!

Now let’s see if I can get those documents uploaded…

.NET

No ASPNET in .NET 2.0

    Who would’ve guessed.  I recently rebuilt my work laptop.  I installed .NET 2.0 framework, but not 1.1.  When I went to try to browse to a website built on 2.0 on my local machine, I got access denied errors.  I did some searching and figured it was due to the ASPNET account not having permissions to the Framework folders, so I went to add it.  Turns out the ASPNET user isn’t there!  I did a quick google search and it hinted at installing .NET 1.1 to get the ASPNET account created, so I downoaded it and installed it.  I also then ran regiis -u and -i on both frameworks, and problem solved.

I didn’t test this as I was in a hurry to get it fixed so it may have been due to an install problem on 2.0 that the -u and -i fixed.  I don’t know.  Have to check that later.