Karthick's Blog!

Role tailored client issue Changing stored procedure to 64 bit in NAV 2009 Did install Dynamics NAV 2009 on windows 2008 64 bit / Windows 7 65 bit. When trying to connect to the database in classic client I got this error. The following SQL server error or errors occurred: 17750,“42000”,[Microsoft][ODBC SQL Server Driver][SQL Server]Could not load the DLL C:\Program Files (x86)\Microsoft Dynamics NAV\60\Database\xp_ndo.dll, or one of the DLLs it references. Reason: 193(failed to retrieve text for this error. Reason: 15100). SQL: INSERT INTO [#$ndo$groups] {CALL [master]..[xp_ndo_enumusergroups](?,?)} The reason for this error is that the installed xp_ndo.dll is 32 bit and not 64 bit. My solution was simple to replace xp_ndo.dll with the 64 bit version. 1. Stop SQL server 2. Copy \\vedfssrv01\DynamicsNAV2009\W1\DVD\Sql_esp\x64\ xp_ndo_x64.dll to C:\Program Files (x86)\Microsoft Dynamics NAV\60\Database 3. Rename existing xp_ndo.dll to xp_ndo_x32.dll 4. Rename xp...

Whenever you encounter this error, when having Server Side Script in your custom ASPX Page stored in your Pages Library, you just need to add this line in your site's web.config. Do not forget to replace the VirtualPath to point to the folder or library which has those pages. <PageParserPaths> <PageParserPath VirtualPath="/sites/TestSites/page/*" CompilationMode="Always" AllowServerSideScript="true" /> </PageParserPaths>

For people who were troubled with the 4 GB DB limit in SQL Express, here is the good news, the DB limit has been increased to 10 GB, enjoy!

For people who work in ISA or trying to explore, stop googling or binging for ISA, it is now ForeFront Threat Management Gateway 2010 or more popularly MS wanting us to call it as TMG! This works only on Win 2008. http://www.microsoft.com/forefront/threat-management-gateway/en/us/default.aspx - Explore more here

Create Backups Directory Create a backup directory for storing the scheduled SharePoint backups (e.g.d:\backupsharepoint) Create Bat File Directory Create a directory for storing the backup script file (e.g. d:\scriptssharepoint) Create Bat File Create a bat file using the code below, modified for your environment. Use UNC paths when using in a server farm environment. @echo off echo ==================================================== echo Backup Script For Office SharePoint Server 2007 echo ==================================================== cd \program files\common files\microsoft shared\web server extensions\12\bin @echo off stsadm.exe -o backup -url http://servername -filename d:\backupssharepoint\backupsharepoint.dat -overwrite @echo off echo completed Schedule bat file Schedule the backup to run frequently, during off peak hours. Open Start > Programs > Accessories > System Tools > Scheduled Tasks Add a Scheduled Task Schedule...

By default, MOSS 2007 has a setting of allowing file sizes of upto 50 MB. If you need to change it, do the following: 1. Change the Max Upload Size in Central Admin -> Application Management -> Web Application General Settings 2. Also in IIS 7, change the Connection Timeout to how many ever seconds you want - reason is, the more the file size, the longer it is going to take to upload, so to be safe, default is 120 seconds

Scenario : you are trying to use this ACE OLEDB provider to programmatically import from an excel file in your ASP.Net 2.0 application running on Windows Server 2003 64 bit What google / forums say: they tell you to change your target platform to x86 in VS 2008 and compile it, now unfortunately for a web app - you cannot do that. So we need to see some other means. Some facts to know: IIS 6.0 does not have the capability to have different application pools running on different bits, whereas IIS 7.0 on Win 2008 Server brings in that capability. But here we are with IIS 6.0 ASP.Net 2.0 however supports both 32 bit and 64 bit and IIS 6.0 supports runing them in parallel. This is what you need to do: 1. Enable 32bit on 64 bit App using the Adminutil script 2. Run Aspnet_regiis -i from the c:\windows\microsoft.net\framework folder - this represents 32 bit. 3. Changed ASP.Net v2 32 bit to Allowed in IIS 6 Web Service Extensions After that, your 32 bit ASP.Net code will run like ...