0x8000ffff Login failed for user 'DOMAIN\SAPServiceSID'...

While uninstalling/reinstalling an SRM 7.0 test system, I came across this error in the work process trace file after the SAP system failed to start before post-processing of the install. This was fairly common on Windows/SQL Server systems in the Pre-ECC world and I thought maybe a few new guys would not know how to address this. Basically it is a prblem with the Windows user and SQL Server login not matching up correctly or being mapped together just right. Here is the process I follow to correct this problem, if a simple shutdown-restart of Windows does not fix it:

(Please read through all the steps to make sure you know what you are doing before starting)

- First, make sure that the affected SAP system is completely shut down (the error will only stop the dispatcher, but the other processes may still be running) and stop the SAPSID_xx service. You may have to set the service to "disabled" to keep it from starting up again while you go through the rest of the steps.

- Second, go into SQL Server Enterprise Manager (or Management Studio, depending on what version you are running) and delete the database user DOMAIN\SAPServiceSID (under the database [SID] > Security > users).

- Third, delete the SQL Server Login DOMAIN\SAPServiceSID (don't confuse this with the database user which should already be deleted at this point). It is VERY IMPORTANT that you only remove the SQL Server Login AFTER you have deleted the database user, otherwise you will have to go through another process later to synchronize the database user with the SQL Server login.

- Fourth, create the DOMAIN\SAPServiceSID login for SQL Server with the following attributes:

1. Windows Authentication
2. Default Database: SID (your SAP database)
3. Server Roles: 'public' and 'sysadmin'
4. User Mapping: SID as DOMAIN\SAPServiceSID, default schema 'dbo', with database role membership in 'public' and 'db_owner'
5. Status: Grant 'connect' and enable login

- Fifth, start the SAPSID_xx service (you may need to set it back to 'automatic' if you disable it earlier)

- Sixth, start SAP

If you miss a few of the steps here or the SAPSID_xx service starts back up before you are finished with each step, you may get a 'login not associated with trusted SQL Server connection' error. In this case, you will just need to stop/restart the SAPSID_xx service again after completing all steps.

Hope this helps...

SAP SRM 7.0 Install...

I just went through a few days worth of frustration, and I have found it in my heart to share with you all the secret that I have unlocked so that perhaps you may be spared the same.
For those of you familiar with earlier releases of SRM, the installation option is found on the ERP installation master media. This is no longer the case with SRM 7.0. It is built on Netweaver, yes, but now the install is no longer available on the ERP media. Of course SAP's documentation on this is severely lacking. In fact all it tells you is that you must locate the "installation master DVD or download." What it fails to tell you, however, is which installation master you need to look for.
through trial and error I found that you will need to locate the Netweaver 7 Enhancement Package 1 installation media, which threw me off a bit. Usually, in the SAP world, an Enhancement Package provides for new functionality in an existing system. This is the first time I have seen an enhancement package be the required platform for a new product. Maybe I am not well-rounded enough, or perhaps my clairvoyance needs work. Regardless, if you are planning on installing SRM 7.0, make sure to locate the Netweaver 7.01 installation master for your platform. In my case the media name was BS 7 SR1 Installation Master Windows Server on x64 64bit.

Hope this helps...

RSA1: You Can Only Work in Client 001...

After installing a new BI system, we ran across this error before starting the BI configuration and creating connections to the ERP systems. We wanted to do all of our work in Client 100 instead of the default client 001. Of course, when you run RSA1 and get the message "You Can Only Work in Client 001" it stops you dead in your tracks.
Fortunately, there is a simple solution to this.
When you first import the BI content, the system decides what client will be your working client, though it never asks you for this input. By default it will go to client 001 if you do not already have another client built.
If you need to work in a client other than 001, you simply have to change an entry in table RSADMINA. Populate the client field (BWMANDT) in the correct row (most systems will only have 1 row in this table) with the client number you want to work from. Problem solved.
Sometimes this problem will manifest itself in the system log with an entry like this:
DIA 001 100 USER RSA1 D0 1 Transaction Canceled BRAIN 009 ( 001 )
The same process fixes this error as well.

Hope this helps...

"J2EE Status Info Unavailable" After a System Copy...

After performing a system copy with SAPINST, we recently encountered a problem where the SAP Management Console would display the message "J2EE Status Info Unavailable" at the end of the dispatcher status. Then under the Java work process folder, the message "No Info Available" would show up. The exact error messages will depend on your kernel version, but you get the point.
After countless hours pulling out my hair and working with SAP support, we finally discovered the issue. Apparently something went wrong with the Java extract from the source system, so settings were not transferred correctly to the extract files, and thus the target system was populated with erroneous information. Unfortunately, everything from my standpoint was showing to be correct and successful with the system copy. I was only able to correct the problem by returning to the source system and running a new System Copy, utilizing the "database specific" option so that SAPINST only ran the Java migration steps. I then went to the source system and re-ran the system copy target steps, and pointed it to the new Java Migration files.
Worked like a charm.

Hope this helps...

Change Spool Servers in SAP afetr Refresh...

Here is a little query I have used for a while, but for some reason I had not yet posted it on my blog.
If you are like me, and you like to frequently perform a refresh from PRD to QAS, you may find yourself having to change spool servers in SPAD... a lot. It is a very simple task, but there are 5 steps you have to complete for each printer just to change the SAP spooler server. Yes it is a pain, especially if you have hundreds of printers defined in SAP.

Here is a quick query you can run from the database side in order to do this MUCH faster:

update qas.TSP03D
set PAMSSERVER='sapqas1_QAS_00'
where PAMSSERVER='sapprd1_PRD_00'

Of course you will need to make sure you are using the correct schema, SID, and server name, but as you can see it is a very simple query.

Hope this helps...

Grant Management Special Ledgers Will Not Transport...

We encountered a particularly difficult problem this past week, and were directed to an OSS note for the fix, and the application of the note was so broad I thought I should go ahead and post our experience here in case anyone else finds themselves barking up trees and pulling hair out.

When prepping a production ERP 6.0 system for Go-Live, we encountered a problem with master data in the productive system, specifically Special Ledger 90 (an SAP-standard ledger, that should exist in the system). The information existed in both the development and quality assurance systems, but not completely in production (bits and pieces of the data were present, but not in all the necessary tables). The first thing we checked was to make sure the object was included in a transport, and that the transport had been imported into all systems. That all checked out. So, we went ahead and created a new transport to try it again. Same problem: exists in DEV and QAS, but not in PRD. After trying a few more things, but to no avail.

To make a long story short, we opened a message with SAP, and they provided a fix. Apparently this is a known issue with no solution other than a report that fixes the symptoms. SAP does not know why it happens, but there is a long list of programs and reports that it effects. The problem was actually a syntax error in an underlying program that made it look as if master data was not present, even though it was. The note to look for is 377053.

Hope this helps...

Cannot Install SAP License Key after System Copy...

When using the SAP-supplied method for a system copy, often you will find yourself in the situation that you cannot install the permanent license key for the target system since the information from the source system is stored in the database already. The SAP-recommended remedy for this is to delete the invalid license keys before proceeding with the new key install. Of course, it is not as easy as that for a few reasons:
1. If you do not have at least a temporary license installed, you must log in as user SAP*, which does not have the authorization to delete license keys.
2. If you do have a temporary license installed, and you are logged in as a user with authorization to delete license keys, you still cannot delete the invalid licenses because the delete step validates the key to be deleted with the system information. And guess what? They don't match , so you cannot delete the key.
This brings us to the real solution, which took a little digging inside the SAP Marketplace to find: You must manually remove the invalid keys from the database. That's it! Just remove the entries from table SAPLIKEY and all your troubles will be over. Well, at least you will be able to install the new license with the correct information, anyway.

Hope this helps...