Skip to Content

Server Busy error when creating Purchase Requisition

Hi, user received server busy error " The action cannot be completed because the other program is busy. Choose Switch to ' to activate the busy program and correct the problem, options in the dialogue bos , Switch to , Retry and Cancel is greyed out

User was entering text in the Long Text box and received a message " do you want to save this text? " the user pressed No and then the Server Busy error was received.

The user then pressed Retry and SAP closed down.

Once SAP was restarted the user was able to create the Purchase Requisition with long text and the action completed successfully.

The user advised that they have received this error one other time.

I have tried to see if there is an explanation as to why you would get this error to make sense of it occurring. I have read papers from Crystal Reports and Excelsius.

Does anyone have any theories or answers as to why this error is received , should you just carry on and select Switch To instead of retry?

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

1 Answer

  • Posted on Sep 23, 2009 at 12:39 AM

    I spoke with a collegue about this issue and he had created a note in the knowledge base:

    Hope this may help others:

    Please see the below Knowledge Base article David wrote a while ago - it relates to an Objective add-in for MS Word which interferes with the correct operation of "Long text" (aka PC Editor) in SAP (which essentially is a word snap-in for SAP). This may be the cause of the error Sandra is getting, given that she describes using long text just before this occurred. I suggest the following workarounds are implemented (there are 3 in total). There is no permanent solution to this, as I can see - SAP expects a 'standard' interface to MS word for correct operation of long text and cannot predict and take into account 3rd party add-ons like Objective which interfere with this interface, so I beileve the problem and ultimate resolution lies with Objective .

    Graphical PC Editor in SAP does not open Summary: The Graphical PC Editor in SAP does not open when the WINWORD.EXE process is running in the background under certain conditions. Problem: This problem arises due to a conflict between Microsoft Word with Objective integration and SAP. Because SAP's Graphical PC Editor is essentially a snap-in of Microsoft Word, the behaviour of Objective integration interferes with its proper operation under certain conditions.

    When you attempt to make changes to text within the Graphical PC Editor and then exit, you will be prompted to "Save changes in text first". This is a SAP dialog box and is to be expected. However, you are then prompted with a second (non-SAP) dialog box asking "Do you want to save the changes you made to Document in Continuous Text". If you then select "Yes" in response to this prompt, an Objective Error dialog box appears. When you next attempt to edit via the Graphical PC Editor snap-in, it will issue an error message and will default back to the line-based PC Editor in SAP. Resolution: There are several workarounds to this problem.

    In the first method, you can ensure that no WINWORD.EXE process is running in the background. Usually, closing down Microsoft Word will achieve this but sometimes you may need to kill the WINWORD.EXE process directly from Task Manager. From now on you should be able to use the Graphical PC Editor in SAP.

    In the second method, you can disable Objective Integration with Microsoft Word. To do this, navigate to C:Documents and Settings\Application DataMicrosoftWordSTARTUP and move the file to another location. Now you should be able to simultaneously have a instance of Microsoft Word open in the background while at the same time using Graphical PC Editor in SAP.

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.