<?xml version="1.0" encoding="utf-8"?>
<ManualTopic ID="/baanerp/install/bw/in000610" xml:lang="en">
   <Header>
      <Title>Server Busy message when starting a .bwl file</Title>
      <Keyword type="header" order="d1e1061635">
         <Level1>Server Busy message</Level1>
      </Keyword>
   </Header>
   <GeneralSection>
      <Paragraph>BECS (the Infor BW Environment and Configuration Selector) can
		also be used to open a .bwl file. Such a file is created when one or more
		records are dragged from a multi-occurrence grid session and dropped into any
		folder, such as the Windows desktop. In such a session, the menu item <GUIRef>
            <GUIRef href="" role="manual">File</GUIRef> &gt;   &gt; <GUIRef href="" role="manual">Send To</GUIRef> &gt;   &gt; <GUIRef href="" role="manual">Desktop</GUIRef>
         </GUIRef> has the same
		functionality.</Paragraph>
      <Paragraph>When a .bwl file is opened, such as by double-clicking, BECS is
		started and tries to find a .bwc file with the correct hostname, bse, and
		bshell which can be used to start BW. When multiple candidate .bwc files are
		found, the user will be prompted to select one of them.</Paragraph>
      <Figure space-and-orientation="indented-estimated">
         <FigIntro>BECS then tries to connect to BW using the Windows OLE
		  Automation technology. First, a connection to any running BW which uses the
		  same .bwc file is attempted; if that fails, a new BW is started. When the OLE
		  connection with BW cannot be established within a timeout period of 5 seconds,
		  OLE displays the following message dialog:</FigIntro>
         <HTML:IMG xmlns:HTML="http://www.w3.org/TR/REC-html40" height="149" width="327"
                   SRC="images/tr_screen_in000610_1.png"
                   alt="[...]"/>
      </Figure>
      <List>
         <ListIntro>Two scenarios are described in which this situation can
		  occur.</ListIntro>
         <ListItemHead>Scenario 1</ListItemHead>
         <ListItem>The connection with BW can still be established. For example,
		  the delay can be caused by a slow network connection or an intermediate login
		  dialog which had to be filled in. When BW has established the connection with
		  the backend, click the Retry button of the Server Busy dialog.</ListItem>
         <ListItemHead>Scenario 2</ListItemHead>
         <ListItem>
            <Paragraph>The connection with BW cannot be established. This can be
			 caused by several reasons, two of which are discussed below, but the solution
			 is always the same: stop the BW with which BECS tries to establish a
			 connection, and click the Retry button of the Server Busy dialog. If it was a
			 running BW, OLE will start a fresh BW. If establishing a connection with the
			 fresh BW also fails, then stop that BW and click the Retry button of the Server
			 Busy dialog.</Paragraph>
            <Figure space-and-orientation="indented-estimated">
               <FigIntro>Finally, the following message dialog will
				appear:</FigIntro>
               <HTML:IMG xmlns:HTML="http://www.w3.org/TR/REC-html40" height="119" width="552"
                         SRC="images/tr_screen_in000610_2.png"
                         alt="[...]"/>
            </Figure>
            <Paragraph>One reason the connection with BW fails can be that the
			 login at the backend fails. To stop BW in such a case, on the login dialog,
			 click <GUIRef href="" role="manual">Cancel</GUIRef>.</Paragraph>
            <Paragraph>Another reason can be that the .bwc file contains a session
			 to be started in its Command field. In such a case, BW will start normally, but
			 OLE is not able to establish a connection. Stopping the normally running BW
			 needs no further explanation. When trying the next time with the same .bwl
			 file, ensure you select a .bwc file without a session to be started in its
			 Command field.</Paragraph>
         </ListItem>
      </List>
   </GeneralSection>
</ManualTopic>