Saturday, June 05, 2010

SSO Error - Password Change

I was reminded today - again - of why you should never change your password that runs the BizTalk servers.  My Tech Ed demo is running in a VPC and the other day the password of the account on the VPC (yes I use only one for VPCs) expired and I changed the account.  Well, I was doing a run through today and my receive locations would not start (Panic!).  They were giving me this error:

Cannot perform encryption or decryption because the secret is not available from the master secret server.

The master secret is on the computer (I verified) and the SSO Service is started - so what was the problem?  First let me state, I did go back and change my password back to the original password, but that did not solve the issue.  I opened the SSO Administration console and noticed that under servers - there were no servers listed.  I added my computer, then in the SSO Admin console, I selected the server and did a stop then a start.  I was then able to Enable my receive locations.

Oh, this was on a BizTalk 2010 beta installation - but in general it is a bad idea to change you password when running BizTalk.

Wednesday, May 12, 2010

Receiving Large amounts of Data through a WCF Receive Location

Recently I have been working on a project where an application will break a file down into a 64 bit byte stream and then send the file to BizTalk.  I am receiving all types of files, including pictures and documents.  I am using WCF for the communication protocol and of course I instantly got a 400 Bad Request error message - telling me message size was too big.  First I changed the client config file, changed the maxReceivedMessageSize and the maxBufferPoolSize.  While these changes were necessary to get the messages to BizTalk, I was still getting the 400 Bad Request error message.  I had generated the WCF service using the BizTalk WCF Publishing Wizard and knew that the maxReceivedMessageSize property was not in the web.config of my service.  The property is in fact located on the receive location, see below:




















I increased the value to 500,000 and everything worked. 

Its one of those property values that you look at everyday, but when you actually need to set the value you forget all about it.

Wednesday, March 03, 2010

Installing CRM - How to prepare One Box Environment

Technorati Tags:

If you have ever read the installation guide for CRM, you know that it’s not an easy task. The problem isn’t the actual installation, but rather the setup of all the fields and preparing the information so that CRM can be used correctly. While those steps are defiantly needed, there are times when a developer may need to install CRM just to connect and verify how data is sent to CRM. The following documentation details how to install CRM on a single Virtual PC.  Please note that some of the  items listed below I had not installed the first time through and had to go back and install them, so if they do not look exactly the same or I am missing a screen shot, that is the reason why.

Background information:

I created a Virtual PC running on Windows 7. The operating system is Windows Server 2008 x86.

Server Manager Roles/Features Installation

Make your Virtual PC a domain controller.  For more information on how to create a domain controller in Windows Server 2009 look here:  Installing Active Directory on Windows Server 2008.  I used Method 3 (dcpromo).

Install IIS 7 from the Server Manager.  You must install II6 Management Compatibility and Application Development (ASP.NET) and Security (Windows Authentication):

imageimage 

Install File Services Role from Server Manager, after several tries I discovered that you must install the Windows Server 2003 File Services:image image

SQL Server Installation

  1. Install SQL Server 2005 or 2008. I installed SQL Server 2008 and used a named instance of CRM, no real need that I am aware of to install on a named instance; BizTalk has just made me wary.
  2. Install SQL Reporting Services
  3. Be sure to open SQL Server and start the SQL Server Agent.

Office 2007 Installation

Install Office 2007. I installed Enterprise Edition.

CRM Installation

Install Microsoft Dynamics CRM Server from the CRM Installation options.

image

Choose Custom Installation and select both Server Roles:

image

If you get the following error, you are not connected to a network and need to install the domain controller (step 1).

image

Enter the name of the server, if you installed using a named instance you will have to use the named instance.  I had to type the SQL Server name into the box.  It was not in the drop down list.

image

Enter a Organization name.

image

Select a web site, a reporting server site and continue.

In the Active Directory Users and Computers, add a new Organizational Unit to store the CRM System groups.  Go back to the CRM installation and select the group.

image

Select the security account for CRM.  I kept the defaults:

image

I did not install the Email Router, but will install the CRM Outlook client:

image

By following the directions above, there should not be any red x’s on the following screen.  If there are, you will have to fix the issues before continuing.

image

Restart your virtual PC

Outlook Configuration

Open Outlook and configure your email.  Since this is a all-in-one box, you will need to create a POP3 account.  I used hMailServer for the first time, and so far so good.  Up until this point I had always used Windows Server 2003’s POP3 service, so I am not an SMTP/Exchange person and it took me some time to get hMailServer configured correctly, but once I did everything went smoothly.

CRM Outlook Client

Next, bring up the CRM installation screen and select Install Microsoft Dynamics Client for Outlook

image

Be sure to change the installation location as it cannot be installed in the same location as the server.

image

After the installation , the configuration wizard will appear:

image

Again, this is an all-in-one box, so select My Company as the option.

image

Internet Address is localhost:

image

Everything should be green on the Requirements screen:

image

I also installed the CRM Data Migration Manager, but the installation was straight forward.

Sample Data

There is sample data located at http://www.microsoft.com/downloads/details.aspx?familyid=D5F77EE7-3D01-4944-B5DC-C8CDC8123DF4&displaylang=en

My next steps was to start loading the sample data and to start understanding how everything works in CRM.

Monday, March 01, 2010

IIS Unauthorized Error

After installing CRM, I continued to get a 401 Error message when I opened the CRM web site.  I quickly realized this was not a CRM issue, but an IIS issue.

Error Summary:
HTTP Error 401.2 - Unauthorized
You are not authorized to view this page due to invalid authentication headers.

Detailed Error Information
ModuleIIS Web Core
NotificationAuthenticateRequest
HandlerPageHandlerFactory-ISAPI-2.0
Error Code0x80070005
Requested URLhttp://localhost:80/loader.aspx
Physical PathC:\inetpub\wwwroot\loader.aspx
Logon MethodNot yet determined
Logon UserNot yet determined
Fix:
To fix this error, open Server Manager and expand Roles.  Then select Web Server (IIS) and select Add Role Services from the right hand side.  When the wizard pops up, scroll down and select Security.  This specific error relates to Windows Authentication not being installed, but I selected all items under Security to ensure I did not run into any other errors.

Side note - this is my first post published by Live Writer.  Very nice!

Tuesday, February 23, 2010

UDDI Installation Error

My coworker, Sachin, found this error and discovered the solution for the problem.  Since I could not find any information on the web about this error I thought I would post the story here:

During the installation of UDDI the following error was encountered:

Attempt to configure UDDI Service Web Application Failed. Exception has been thrown by the target of an invocation. Biztalk uddi service web application cannot be installed because IIS reports an error.

However, there was no error being reported.  The problem was that the default web site had been renamed and was not the standard "Default Web Site".  UDDI must have an issue installing to web sites named something other the the default, because when Sachin added a new site named "Default Web Site" the installation completed without any errors.

Monday, January 04, 2010

Hotfix available for BizTalk 2009 and Visual Studio 2008

If you have developed with BizTalk 2009 and Visual Studio its a safe bet that you have encountered the error(s) where one BizTalk project suddenly loses the reference to another BizTalk project. When looking at the project references for Project A, you can still see the reference to Project B, but the orchestration is complaining that it cannot find the schema, or the map cannot find the destination schema, etc. The solution was to either switch the "Copy Local" value to False then switch it back to True. Or - and I found this to work better - to delete and re-add the reference.

I am glad to announce that there is now a hotfix for this issue (KB 977428):
FIX: You experience various problems when you develop a BizTalk project that references another BizTalk project in Visual Studio on a computer that is running BizTalk Server 2009

Go and get it!

ESB with UDDI on separate server - can this be done?

The answer to this is yes. To have the ESB Toolkit use a separate server, the server location must be changed in the esb.config file found in the installation folder of the ESB Install (not the bin folder). Change the url in the baseUri tag of the UDDI resolver element to the correct server.















However, if you want to add the esb binding information or publish a server to UDDI using the UDDIPublisher tool, you will need to copy the following files to the UDDI Server (all from the ESB Toolkit/bin directory):

Microsoft.Practices.ESB.ExceptionManagement.dll
Microsoft.Practices.ESB.UDDI3.dll
TransportTypes.xml
Microsoft.Practices.ESB.UDDIPublisher.exe
Microsoft.Practices.ESB.UDDIPublisher.exe.config

Place the files in the same folder, add the dlls to the GAC, and then run the UDDIPublisher.exe from a command line.