Everything for SAP Hana / Basis /Technology / BO / BW

Seri Numaramızı girmeliyiz,Burada Enterprise özelliklerini kullanacaksak,Enterprise MOSS Lisansınızı Girin, Standart Kurulumda sadece kurulumla ilgili bilgileri aktardık. Bir sonraki makalemizde,Sharepoint Servislerinin nasıl kullanılacagı konusunda bili verecegiz..

Two ways: 1. check the Windows Registry for HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\InstallRoot 2. check for a local directory like %windir%\Microsoft.NET\Framework\ where is v1.1.4322 - for .NET Framework v1.1 v1.0.3705 - for .NET Framework v1.0

HTTP/1.1 200 OK Server: Microsoft-IIS/7.0 Date: Tue, 24 Mar 2009 06:58:05 GMT Connection: close If you get above error on IIS site,you must look first database connection user,check user between database and IIS Site. then you give full or write permission user, then this problem resolved... :)

The SharePoint Search web service query tool provides a great way to build your search queries and submit them to the MOSS/WSS Search web service Download from CodePlex here Toggle the server type to test against WSS/MOSS. Toggle the Query Type for keyword search or SQL Search. If you are trying to retrieve all Blog posts here is how your query would look “select title,author,LastModifiedTime,Path,bodydescription from scope() where “scope”=’Blog Posts’ order by 3 desc” Here we pull the different properties on a scope called “Blog Posts” Here is a link about this tool http://www.mosssearch.com/searchwebservice.html

"Faulting application ax32.exe, version 3.0.1951.3730, stamp 40589f7c, faulting module ax32.exe, version 3.0.1951.3730, stamp 40589f7c, debug? 0, fault address 0x0023a831." if you get above this error , you used client version than diffrent versions of aos. Make this, Check your aos version ! on ax 2009 with sp1 > 1000.52 Check your client version ! on ax 2009 with sp1> 1000.52 If this versions are identically then you must go to axapta cockpit. sync database... thats all.

Axapta 2009 AOS Upgrade AOS'u upgrade yaparken eger eskı versıyonda kalıyor ıse; Aosu sılıp sıfırdan kuruyoruz ardında sp1 pack gecıyoruz...(aos'u upgrade yapıyoruz)client versyonu eskı gorunurse clıentı kaldırıp yenıden kuruyoruz Client versiyonu upgrade yapıyoruz, kernel versıyonda boylelıkle guncel surume cekılıyoruz.100.52

he build version numbers are split into three parts. First the client version number is listed, followed by the application version. Formatted like: Build #client version/application version/localization vertsion e.g. #1951.7500/514-320/OP023-196 - for 3.0 KR2 client and 3.0 SP4 application. Client versions Build number Version AOCP version 1951.8 3.0 N/A 1951.17 ------ 3.0 SP1------- 60029 (0xEA7D) 1951.18 ------ 3.0 SP1------ N/A 1951.2410 ------3.0 SP2------ 60031 (0xEA7F) 1951.2411 ------3.0 SP2------ Hotfixed 60031 (0xEA7F) 1951.3730 ------3.0 SP3------ 60031 (0xEA7F) 1951.3733 ------3.0 SP3------ Hotfixed 60031 (0xEA7F) 1951.4060 ------3.0 SP4------ 60031 (0xEA7F) 1951.5160 ------3.0 SP5------ 61031 (0xEE67) 1951.6710 ------3.0------ Kernel Rollup 1 61031 (0xEE67) 1951.7500 ------3.0------ Kernel Rollup 2 63031 (0xF637) 1951.7609 ------3.0------ Kernel Rollup 3 63031 (0xF637) Application versions Build number Version 514-90 ------ 3.0 SP2 514-193 ------ 3.0 SP3 5...

he build version numbers are split into three parts. First the client version number is listed, followed by the application version. Formatted like: Build #client version/application version/localization vertsion e.g. #1951.7500/514-320/OP023-196 - for 3.0 KR2 client and 3.0 SP4 application. Client versions Build number Version AOCP version 1951.8 3.0 N/A 1951.17 3.0 SP1 60029 (0xEA7D) 1951.18 3.0 SP1 N/A 1951.2410 3.0 SP2 60031 (0xEA7F) 1951.2411 3.0 SP2 Hotfixed 60031 (0xEA7F) 1951.3730 3.0 SP3 60031 (0xEA7F) 1951.3733 3.0 SP3 Hotfixed 60031 (0xEA7F) 1951.4060 3.0 SP4 60031 (0xEA7F) 1951.5160 3.0 SP5 61031 (0xEE67) 1951.6710 3.0 Kernel Rollup 1 61031 (0xEE67) 1951.7500 3.0 Kernel Rollup 2 63031 (0xF637) 1951.7609 3.0 Kernel Rollup 3 63031 (0xF637) Application versions Build number Version 514-90 3.0 SP2 514-193 3.0 SP3 514-320 3.0 SP4 514-513 3.0 SP5 514-859 3.0 SP6 Dynamics AX Version 4.0 Build number Version AOCP version 4.0.1659.26 4.0 RTM 41638...

Note: All of the addresses of the KB / Articles - 2007 Products / MS / Non-MS Articles below were valid at the time I added them to the WSS FAQ site and to this file. I can't guarantee that they still are. (This is also posted to my blog at http://mikewalsh.bilsimser.com) (Items are added to the WSS FAQ throughout the week so you will find new items more quickly by checking at wss.collutions.com or www.wssfaq.com daily.) From 11th - 17th June 2007 I 2007 KB Articles (*now only one section for WSS and MOSS*) New http://support.microsoft.com/default.aspx?scid=kb;en-us;939015 Support WebCast: Microsoft Office Outlook 2007 integration with Microsoft Windows SharePoint Services (WSS) version 3 Contact Lists and Document Libraries 15th June 2007 http://support.microsoft.com/default.aspx?scid=kb;en-us;937208 Description of the SharePoint Server 2007 hotfix package: May 15, 2007 14th June 2007 http://support.microsoft.com/default.aspx?scid=kb;en-us;937203 Description of the Windows Shar...

Howto: Edit network card bindings in Windows Server 2008 Figuring out how to edit the order of NIC bindings on a Windows 2008 Server took quite a bit of Googling. It seems that you need to know a secret key combination to be able to view the Advanced tab, where the option to edit the NIC bindings is located. To edit the network card binding order in Windows Server 2008: Login to the server with administrative credentials Click Start > Control Panel > Network and Sharing Center On the left hand side select Manage network connections Press Alt+N to display the Advanced menu Select Advanced Settings. On the Adapters and Bindings tab, highlight your NIC and use the arrows on the right hand side to adjust it’s binding order. You can also access the Network Connections screen directly by clicking Start > Run , typing ncpa.cpl and pressing Enter