dev

SAP BW Client

- SBIW : SAP Business Information Warehouse IMG (Implementation Guide)

- RSA1 : Modelling DW Workbench. This is Main Transaction

- SCC4 : Client Administration (BASIS Area)

- RSECADMIN : Authorization, Replacing Obselete RSSM

- SE10 : Transport Organizer

- RSPC : Process Chain Maintenance

- SE37 : ABAP Function Modules

- RSZC : Copy Query Between InfoCube

- RSRV : Analysis and Repair of BW Objects

- RSORBCT : BI Business Content Transfer

- SM37 : Overview Of Job Selection

- LISTCUBE: To display content of Info Providers

SAP R3 Client (Origin, Dev, or Quality Control)

- RSA9 : Content Application Transfer Component Hierarchy (One Time Setting)

- RSA2 : OLTP Metadata Repository, For Checking DELTA Capable

- RSA3 : Extractor Checker

- RSA 5 : Install Business Content

- RSA6 : Maintain DataSource

- RSA7 : BW Delta Queue Monitor

- LBWQ : Logistic Queue Overview

- LBWE : LO data Extraction : Customizing Cockpit

- LBWG : Deletion of Setup Data

- SBIW : SAP Business Information Warehouse IMG (Implementation Guide)

- OLI7BW : Statistical Setup for Old Documents : Order

- SE16 : Data Brrowser

- SE10 : Transport Organizer

- SE11 : ABAP Dictionary Maintenance

- RSO2 : OLTP Metadata Repository

Problem

1. Remote Desktop Connection (RDC) from Vista x86 as Client to Windows Server 2008 x64 as Server, lost (disconnected) in randomize duration.

The error message:

Because of an error in data encryption, this session will end. Please try connecting to the remote computer again

2. SQL Server Management Studio 2008  on Vista x86  cannot connect properly to  SQL Server 2008 x64 Standard Edition on Microsoft Windows server 2008 x64 Enterprise Edition.

Sometimes you can log in , sometimes you cannot. When you succeeded on log in , you cannot browse/expand  tables on a database or other folder such as log in folder.

The error message:

Internal connection fatal error. (System.Data)

Cause

After some Googling and Analyze the data traffic using Microsoft Network Monitor 3.3 . It seems that there’s a problem on HP Gigabyte LAN (HP NC373i).  The problem is on  IPv4 Large Send Offload method on delivering data.

Solution

Turn Off  (Disabled) the IPv4 Large Send Offload Feature On HP NC373i Network Adapter.

Goto :

1. Server Manager Application
2. Summary > Computer Information > View Network Connections
3. Right Click on Local Area Connection > Click Properties
4. Click Configure
5. Goto Advanced Tab
6. Select IPv4 Large Send Offload
7. Set the Value : Disable

Click Ok

Problem:

Suddenly, after detached and re-attached  a WSS 3.0 content database , the WSS 3.0 search service or Search Server 2008 Express (SS2008E) cannot crawl the portal anymore.

So i began to refresh the service and repopulate the search index by performing these  steps:

1. Redefined Alternate Address Mapping (AAM)
2. Reset all  Search Server 2008 Express crawled content
3. Restarting the WSS 3.0 search service and timer
4. Restarting the IIS web service.
5. performing a full index : STSADM.exe” -o spsearch -action “-fullcrawlstart” “

But still, nothing happen, the search action resulting an empty page.

Now, i look up at the server’s  Event Viewer > Application  Log , and i found this message:

Event Viewer > Application

Event Type:    Warning
Event Source:    Windows SharePoint Services 3 Search
Event Category:    Gatherer
Event ID:    2436
Date:        05/05/2009
Time:        0:29:03
User:        N/A
Computer:    WSSPORTAL1
Description:
The start address <sts3://WSSPORTAL1/contentdbid={33c8b862-f79b-42d1-8f8a-2ed0f2e1f984}> cannot be crawled.

Context: Application ‘Search index file on the search server’, Catalog ‘Search’

Details:
The crawler could not communicate with the server. Check that the server is available and that the firewall access is configured correctly.   (0×80041200)

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Cause:

After hours of searching and trial attempt to fix the problem…

finally i found the cause for the problem.

If your server running WSS 3.0 portal application, the default (start) sites address is located next to the “sites” url, such as:

http://WSSPORTAL1/sites/mysite

so there’s a big possibility that this URL :

http://WSSPORTAL1/

is empty , or resulting an error page.

Resulting :

The WSS 3.0 and SS2008E Search service cannot validate  the http://WSSPORTAL1/ address,  so it’s stop from crawling the root URL (/sites/../…etc)

Solution (workaround):

1. Modify the registry, or
2. Create a WSS 3.0 blank site at http://WSSPORTAL1/ (recommend)

And..boom.. it work..