If you have come to this blog searching for the error mentioned above then probably you’re doing some modifications to ADFS 2.0 site.
Following would be the symptoms that you have done so far:
- You have opened adfs\ls website as Website project in Visual Studio.
- If the project type is Website, you probably had a message from Visual Studio to upgrade for the .Net v4.0.
- You have created a new project Empty Web Application and imported adfs\ls website content to the project.
- You are modifying this site/application on local machine and not on Windows Server where ADFS is installed.
Follow these steps to successfully start modifying ADFS site:
- Install Visual Studio 2010 on Windows Server where ADFS is installed and configured.
- Create an Empty Web Application
- Import all the files from adfs\ls directory to the Web Application. (generally, you can find it on c:\inetpub\adfs\ls)
- Right click on the project in Solution Explorer and click on “Convert to Web Application”.
- You’re ready to go!
You do not need to add reference of any files to this web application. Just Build and Publish the site to the same directory where adfs is installed.
Microsoft.IdentityServer.Compression and other required files will be referenced from GAC as you are developing the project on the server itself.
Happy Programming! 🙂
If you are installing Microsoft Dynamics CRM 4.0 and if you face installation error.
Action Microsoft.Crm.Setup.Server.ConfigureAspNetAccountAction failed. The group name could not be found.
Certainly you are installing CRM 4.0 on Windows Server 2008 R2 and you must have installed IIS 6.0 Compatibility mode from the features. This is where the problem lies. IIS 6.0 Compatibility mode does not create IIS_WPG group by default. In this case there are two options:
- If you select the Network service to start Microsoft Dynamics CRM 4.0, the installation would go smooth and successful. You need to cancel the setup and retry installing with Network Service.
- Do not cancel the setup, create a Local Group called IIS_WPG. Try below command:
- Open Command Prompt and type: net LOCALGROUP IIS_WPG /add
- On successfully creation of the group, click on retry button. You’re done! Setup will continue.
Are you missing the aero effect in Windows Server 2008 R2? Here are some simple steps, just follow them:
Command to install the Aero effect [Windows 7 Basic theme]: Open PowerShell/cmd and run the command: ServerManagerCmd -i Desktop-Experience
You would have to restart the server once installed successfully. After the restart, go to Control Panel -> Appearance and Personalization -> Click Personalization and select Aero theme. Or right click on the desktop and click personalization and select the Aero theme.
If the themes are there, but disabled; do the following:
Go to Start -> Run -> services.msc -> Themes -> Set the properties matching with the screenshot given below:
Log off and login again to see if the effect.
If the theme is still disabled then shut down the server, go to VMWare Settings -> Hardware -> Display and enable the “Accelerate 3D Graphics” checkbox.
Power on the Server 2008 R2.
Enjoy the Aero!!
I just installed latest version of MyGeneration 1.3.1 on my Windows Server 2008 R2 and on the first run I came to know that the “Drivers” dropdown list is empty.
Tried with different solutions from different sources on the net and none of them worked…
– Tried working DefaultSettings.xml replaced.
– Tried with different drivers installations.
– Tried without MDAC 2.7+ driver check.
– Checked if the problem is for 64-bit only, etc.
How it can be fixed? Here, follow these steps:
The problem is because of multiple .Net Frameworks installed. MyGeneration Setup program registers MyMeta.dll with .Net v2.0 while the program should be registered with the .Net v4.0:
1. Uninstall MyGeneration if already installed.
2. Uncheck the option for MDAC 2.7+ checkbox while setup.
3. After installation click “No” when asked – “Launch MyGeneration?”
4. Go to Visual Studio 2010 Command Prompt and enter following command
5. regasm.exe “c:\Program Files (x86)\MyGeneration13\MyMeta.dll” / tlb: MyMeta.tlb
6. Exit Command Prompt when successfully registered.
7. Run MyGeneration with Drivers dropdown list full of available drivers.