Just little about C#, .NET, SQL Server, SharePoint and SAP

Archive for February, 2011

SAP IDES Installation – Import ABAP Phase taking too long issue

Posted by zieglers on February 19, 2011

So far I lost the count on how many SAP IDES installations I made on different environments. Every installation is a new challenge and comes with own unique problems if there exists any.

Recently I tried SAP IDES ECC 6.0 Installation on Hyper-V environment with a host of 8GB Ram. This time I allocated 6GB Ram to WinServer 2003 R2 Standard Edition client, and took some screenshots to share with you all. I read lots of people out there especially complaining about import ABAP taking too long. Of course there are several factors to that like number of parallel import jobs running or memory allocated for client machine and SQL Server … etc.

Here I’m not going to make any conclusions on that. Simply I want to show you my experience of SAP IDES ECC 6.0 Installation on Hyper-V. Yes, import ABAP phase is going to take a long time, and yes it’ll take a lot longer than you expect. Since this is the case, just be patient and let it run smoothly. During this phase, make sure that your client is not going to run out of disk space. Also, set your power options to ‘always on’ so that your host doesn’t go into sleep mode during installation.

Here is the first minutes of Import ABAP Phase.. Note SQL Server memory consumption. 2.7 GB, not too bad for a 6GB client.

As you can see, below screen clearly shows that my IMPORT ABAP Phase almost took 1 day to complete.

(Yes, I was doing SAP Installation on Valentine’s Day 🙂 Well, technically I was only monitoring it, so no harm done to family life..)

Also, another thing to check is that, make sure all 105 import jobs completed successfully as seen below. You can check this from installer log screen.

Following Import ABAP Phase, sometimes first time start of central instance can take some time, but nothing more than 10-20 minutes. There is a time-out limit for that. Once the central instance is up and running, you’ll see disp+work processes like this.

And finally once the installation is complete, here is what you get.

Now you can go ahead and if you haven’t done already, install your SAP GUI and connect to your SAP System for the first time.You can use your DDIC user and password you provided during installation to log on.


P.S. Note that your temp license will expire in 1 month.



Posted in IT Stuff, SAP | Tagged: , , , , , , , , , , , , , , , , , , , | 3 Comments »

A Real Life Example on why you need localization in SharePoint

Posted by zieglers on February 4, 2011

In this post, i’d like to mention a recent issue i ran into in a client environment in terms of Localization of SharePoint. I’ll give a real life example why they needed localization and what I had to do to support it.

Once you browse the web there are many articles out there talking about what localization is and why you need it. I won’t talk about those here. Rather, i’ll try to explain when a company can face the question ‘When do I have to support localization in my SharePoint applications?‘.

Actually answer is pretty easy! The day you start deploying your SharePoint applications for geographical locations speaking a language other than English, you should start thinking of ‘localizing‘ your applications. Although you deploy your applications in English, sooner or later you’ll get the requests for your application to support different languages. 

Fine. Solution is easy right. Ask infrastructure folks to install necessary language pack on servers and start creating sites in that language, that’s it!

Is it really so??? Not really..

Maybe more important than localizing your SharePoint application, is to code your SharePoint application language-proof. This is the first thing you need to focus on. Once this is properly done, you can start localizing your application for different languages.

But, what do I mean by saying ‘Code your SharePoint application language-proof‘? This is exactly where our Real Life Example kicks in..

Before I go head and show the specifics of the example, here is a good practice.

Search your source code for constant strings in English.

This is a good starting point. Now, let’s be careful here. I’m not saying your code should not have any constant strings at all. Based on your logic you might need them.

However, having some constants in code in English, usually gives you a hint on if that constant might be needed or not if you’d deploy your code in an environment other than English.

Here is an example of that. Following you can see a code snippet where content type names are initially defined in English.

Presumably this means that those constant strings will be used later in that class to refer to OOTB and some custom content types.

Now let’s assume your code needs to remove ootb document content type and add a custom content type to all document libraries.

Somewhere in the code you notice a line like that, which is trying to check if the list you are working on has ootb content type or not.

Obviously, above code won’t work on any SharePoint sites other than English.

Once again I want to emphasize here. We are not applying localization to our SharePoint application yet. We are just trying to make sure that our code can successfully execute on environments deployed other than English.

I found the issue. What do I do now?

If you know that you’ll be using a SharePoint related constant, it’s a best practice to get localized version of that constant from resource files shown as below.

Now, your code can execute without any errors or side effects.


Hope this example helps you to see how easy to determine a localization issue in your code and actually how easy to fix it before errors or any side effects are encountered.


Posted in SharePoint | Tagged: , , , , , , , , | Leave a Comment »