How to make the speaker icon on Google Chrome function as mute button

Enter "chrome://flags/#enable-tab-audio-muting" into a tab, hit enter and click on enable.\

For the flag change to reflect, restart Chrome.

Getting your Grooveshark playlist from Chrome and Firefox

Grooveshark has been shut down. If you have opened Grooveshark with chrome and your local cache intact, you can retrieve your playlist from chrome's local storage.

  1. Go to in chrome (haven't tried in other browsers)
  2. Open "Developer Tools" (CTRL+SHIFT+I)
  3. Click on "Resources" Tab
  4. Expand "Local Storage" tree
  5. Click on ""
  6. Find the key that looks something like "Library32467954" (some 7+ digit number)
  7. Look at its "value" (it's a JSON string). You should see something like this "{"lastModified":.....blah blah some artist name...
  8. Right-Click on that cell, click "Edit Value", then hit CTRL+C (Copy)
  9. Paste the contents of your clipboard into the window @
  10. Download the resulting .CSV file in Open Office or Excel

Firefox users can run the following in the console (Ctrl+shift+k) to try and retrieve the information
for (var i = 0, k; k = window.localStorage.key(i); i++) {
    document.body.innerHTML += '<div>' + k + '<br/>' + window.localStorage.getItem(k) + '</div>';

If you cleared the cache or use any other browser try your luck at

Resetting SAP Upgrade

While SAP upgrade is in the preparation phases, SUM tool offers an option to reset the work done by SUM tool from the menu option: Update > Reset update

Resetting SAP Upgrade

This is the recommended method of resetting the upgrade.

If the upgrade was not properly reset from a previous attempt. The subsequent run can fail at the step PREP_INIT/VALCHK_INI with error similar to the following:

SAPup broke during phase VALCHK_INI in module PREP_INIT / Initialization
Error Message: SAP_ABA is in an undefined state, that is not safe to be upgraded, reason Upgrade wasn't completed - Call the SAP Support

This example shows SAP_ABA component, it could be any component(s) that may be in undefined state.

If you encounter this problem, you have the following two choices:
1. Reset from command prompt by executing SAPup with reset prepare option
cd <upgrade directory>/abap/bin
./SAPup reset prepare

2. Run the report RSUPGRES as DDIC user from 000 client
The report does not require any parameters and should be started in the background. The report takes between 20 and 60 minutes approximately. It is vital that you do not terminate the report manually. The report can be used with current SUM versions as of SUM SP10.

How to Approve Download Basket in SAP Solution Manager

When you generate a stack XML, the required software is automatically approved for download. However, when you want to download a single patch (to fix a bug for example), you would add the software to download basket, but it would be sitting there waiting for approval.

You can manually approve the software using the function module /TMWFLOW/MO_UI_BASKET_AUTHORIZ

Log in to Solution Manager system.

Call transaction SE37 and execute the function module  /TMWFLOW/MO_UI_BASKET_AUTHORIZ

How to Approve Download Basket in SAP Solution Manager

Set I_OSS_RFC = SAP-OSS and execute

How to Approve Download Basket in SAP Solution Manager

Select the software file and click on Confirm download

How to Approve Download Basket in SAP Solution Manager

Now the software will be ready to download in the Download Basket.

You can also use the report /TMWFLOW/RMOBASKETAPPROVAL to approve the software.

SUM Javaonly update on Dual Stack

SAP recommends using SUM tool for updates or upgrades, and at the same time they support SPAM and SAINT tools for updating ABAP stack. Using SPAM/SAINT is faster (and at the same time time tested method we all are comfortable with). As long as SAP continues supporting SPAM/SAINT, Basis admins are more likely to use it.

For J2EE stack, SAP has discontinued support of updating using using JSPM. Therefore patching J2EE can only be done using SUM.

In case of Dual Stack, because JSPM is not supported, J2EE can only be updated using SUM. You would still prefer to update the ABAP part using SPAM/SAINT. But you cannot patch ABAP and then start up SUM with default options to patch J2EE.

SUM Javaonly update on Dual Stack

It will error out on the ABAP side of SUM.

To patch J2EE on Dual Stack system, you can start SUM using the following option:
STARTUP javaonly

With this option, SUM will not patch ABAP stack and will only patch the J2EE patch.

The advantage? One can patch ABAP using SPAM/SAINT and then patch J2EE using SUM, eliminating the need for shadow instance and speeding up effort spent on SPS updates.