Thursday, March 1, 2012

SPS 2010 Shell Management Error

Problem
When you run powershell on your server you get the following error:The local farm is not accessible. Cmdlets with FeatureDependencyId are not registered.
Solution
Make sure the logged in user has rights to the SharePoint_Configuration databaseSharePoint_Shell_AccessDB_owner (try reducing the privileges after you get it working in order to support “least privileges

Wednesday, February 22, 2012

Ax 2012 Version Check

Dynamics AX 2012 RTM 6.0.947.06.0.947.0 RTM

Dynamics AX 2012 RTM Hotfix6.0.947.xxx6.0.947.xxx Published Hotfixes

Dynamics AX 2012 CU 16.0.947.616.0.947.61 Cumulative Update 1

Dynamics AX 2012 CU26.0.947.2806.0.947.280 Cumulative Update 2

Lock Drive Without Any Software

Lock Drive Without Any Software
  • Step 1 : Goto "RUN" and type "gpedit.msc"
  • Step 2 : A window will be opened (Group Policy).You will find two options in left side of the page.
  • Step 3 : Drop down the "user configuration" and again drop down sub menu "Administrative Templetes" and again drop down another sub menu "Windows Components" and click on "Windows Explorer".
  • Step 4 : Right click on "Prevent Access To Drives From My Computers" and then click on properties.
  • Step 5 : Click on the radio button "Enabled" and you can select any option in the menu.
  • Step 6 : Follow the same procedure for disabling it.

Wednesday, January 25, 2012

2003 Terminal server – users denied logon because not enough resources are available, happens occasionally requires reboot to fix

Hi All,

The problem is that the terminal server will function just fine for a week or so and then suddenly when a new user tries to log on they get an error message indicating that not enough resources are available to log them on

Resolution:

1) Create/edit these values in the registry:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\MemoryManagement“PoolUsageMaximum”=dword:00000030“PagedPoolSize”=dword:ffffffff2) Restart.
Also Refer to the KB: http://support.microsoft.com/kb/312362

Tuesday, January 24, 2012

"Service ‘MSExchangeTransport’ failed to reach status ‘Running’ on this server."






I turned military service and write back smoothly. In this case i setup exchange 2010. but suddenlty i become above transport message "MsExchangeTransport"

You can use my solution on this text.

I hope you help!

After disabling my setup went smoothly, follow the below instructions to disable IPv6 from your system.To completely disable IPv6 on a Windows Server 2008-based system, follow these steps:






1. Open Registry Editor.



2. Locate the following registry subkey:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters



3. In the details pane, click New, and then click DWORD (32-bit) Value.



4. Type DisabledComponents, and then press ENTER.



5. Double-click DisabledComponents, and then type 0xffffffff in Hexadecimal or 4294967295 in Decimal.If setup still gives error, remove IPv6 entry from “hosts” file %systemroot%\system32\drivers\etc



then enable ip6 from network by changing adapter settings.

Thursday, February 24, 2011

Missing AX EP web project in Visual Studio 2008


So you have installed the Enterprise Portal Development tools add in for Visual Studio 2008. Everything works for you, but other users are complaining that they can’t see the AX web project template:

Here's what you need to do:

1 - Verify the installation of VS2008
The EP dev tools setup installs EP project, control templates and Visual studio Add-In for VS 2008. Remember that EP dev tools must be installed on the same machine as Enterprise Portal

The Web Site project template (AxWebProject.zip is installed in My Documents folder under:
Visual Studio 2008\Templates\ProjectTemplates\Visual Web Developer\CSharp

Page and control templates AxWebpartPage.zip and AxWebUserControl.zip under:
Visual Studio 2008 \Templates\ItemTemplates\Visual Web Developer\CSharp

The Add-in is installed in
Program Files\Microsoft Dynamics AX\50\EnterprisePortalTools
and is added to the VS Add-in files path and enabled.


You can check this in VS Tools->Options->Add-in you should see

In VS Tools -> Add-In Manager Dynamics AX Enterprise Portal Tools must be enabled.


To check if everything is installed correctly, when you create a new Web Site Project in VS 2008 C#, you should see Dynamics AX Web project template.



If a user can see Microsoft Dynamics Ax Web Project template it’s because in his/her profile on system the template is available. In general the template is located on a windows 2003 server at
C:\Documents and Settings\[user id ]\My Documents\Visual Studio 2008\Templates\ProjectTemplates\Visual Web Developer\CSharp\ AxWebProject.zip

To make Microsoft Dynamics Ax Web Project template available for other users copy the Templates folder from the user who can see template and paste it to other users’ profile.

It assumed that your templates are available in the default located as mentioned in above path

· Go to C:\Documents and Settings\[user id ]\My Documents\Visual Studio 2008
· Copy Templates folder
· Open the other users’ profile and go to C:\Documents and Settings\[user id ]\My Documents\Visual Studio 2008\
· Paste the Templates folder. If system says to overwrite it click on yes option.

Then, you may need to refresh Visual Studios cache of templates after copying them:
· Open the Visual Studio command prompt (Start \ Programs \ Microsoft Visual Studio 2008 \ Visual Studio Tools \ Visual Studio 2008 Command Prompt) and type devenv /installvstemplates.

If you still don't see the template, remember that you need to select C# as your project programming language before it shows up.
If you can see the template but can't connect to the AX AOS from Visual Studio check the following:

· Check that .NET Business Connector has been correctly installed and that the configuration points to the correct AOS instance.
Check that the user you run Visual Studio with, has login and proper development permissions in AX.
· Check that the "Dynamics AX Enterprise Portal Tools" Add-in is correctly installed in Visual Studio. Open Visual Studio / Tools / Add-in Manager to verify that Add-in is correctly installed and configured. If you can't see it, you must reinstall the EP Development Tools.