There will numerous problems introduced to your configuration if you run the SAS Deployment Wizard a second time on one machine and specifying a completely different plan.xml file. Problems will also arise if you configure a client-tier over an existing server-tier configuration. If you desire to add components to a configured system, you will need to edit your original plan.xml file and add the new products. Please ask your Sale Executive to help in altering your plan.xml file.

Possible problems that could be introduced to your configuration include:

• Inability to access or validate Workspace Server, Stored Process Server, or Pooled Workspace Servers.

  Failed to start server
  
  Details:
  INFO: Starting extended validation for workspace server [ level 1 ] - making a connection
  SEVERE: failed to start the server
  

• Errors in the Object Spawner log

  ERROR: the child process terminated before accepting the transfer of open handles
  the child process terminated with exit status 0x0
  

  or

  The TCP/IP tcpSockWrite() support routine failed with error 10038 (The specified parameter is not a socket.).
  The Bridge Protocol Engine Socket Access Method was unable to send data to its peer.
  

• SAS OLAP server, Table Server, and Connect and Share services will no longer start.
  Errors in the log will indicate "Error 1067: The process terminated unexpectely.
  The logs will indicate errors such as:

  • Error authenticating user @oma.person.trustusr.login.userid@ in function LogonUser. 
     Access denied.
     Invalid credentials.

• Tiers that are dependent on this machine will fail to configure

To correct the problems introduced by the second iteration of the SDW, restore files found in C:\SAS\Your_Config\Lev1\Backup.

Specifically, ensure that your file C:\SAS\Your_Config\Lev1\level_env.bat has the definitions for SASROOT and SAS_COMMAND.

Example:

SET SASROOT=C:\Program Files\SAS\SASFoundation\9.2
SET SAS_COMMAND=%SASROOT%\sas.exe

Operating System and Release Information

Product Family	Product	System	Product Release		SAS Release
			Reported	Fixed*	Reported	Fixed*
SAS System	SAS Enterprise BI Server	Microsoft Windows 2000 Server	4.2
		Microsoft Windows 2000 Advanced Server	4.2
		Microsoft Windows 2000 Datacenter Server	4.2
		Microsoft Windows 95/98	4.2
		Microsoft® Windows® for x64	4.2
		Microsoft® Windows® for 64-Bit Itanium-based Systems	4.2
		Microsoft Windows Server 2003 Datacenter 64-bit Edition	4.2
		Microsoft Windows XP Professional	4.2
		Microsoft Windows Server 2008	4.2
		Microsoft Windows Server 2003 Standard Edition	4.2
		Microsoft Windows Server 2003 Enterprise Edition	4.2
		Microsoft Windows Server 2003 Datacenter Edition	4.2
		Microsoft Windows NT Workstation	4.2
		Microsoft Windows 2000 Professional	4.2
		Microsoft Windows XP 64-bit Edition	4.2
		Microsoft Windows Server 2003 Enterprise 64-bit Edition	4.2
		Windows 7 Enterprise x64	4.2
		Windows 7 Enterprise 32 bit	4.2
		Windows 7 Home Premium 32 bit	4.2
		Windows 7 Home Premium x64	4.2
		Windows 7 Professional 32 bit	4.2
		Windows 7 Professional x64	4.2
		Windows 7 Ultimate 32 bit	4.2
		Windows 7 Ultimate x64	4.2
		Windows Millennium Edition (Me)	4.2
		Windows Vista	4.2

* For software releases that are not yet generally available, the Fixed Release is the software release in which the problem is planned to be fixed.

---

There will numerous problems introduced to your configuration if you run the SSAS Deployment Wizard a second time on one machine specifying a completely different plan.xml file or selecting a different tier from your original plan.xml.

Type:	Usage Note
Priority:

Date Modified:	2010-05-28 14:10:33
Date Created:	2009-07-16 15:12:09