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...