SUPPORT / SAMPLES & SAS NOTES
 

Support

Problem Note 58301: Using a range that contains empty cells as an input stream for a stored process might produce an error in SAS® Add-In for Microsoft Office

DetailsHotfixAboutRate It

In SAS Add-In for Microsoft Office, you can specify to use a range of cells as input to execute a stored process. This technique is described in the paper Excelling with Excel. However, if the selected range contains one or more empty cells, the stored process might fail to execute. Here is an example of an error that you might see:

------------------------------------------------------------------------------------ Exception information ------------------------------------------------------------------------------------ Object reference not set to an instance of an object. -------------------------- Technical Information Follows -------------------------- Exception Details: ---------------------------------------- Exception type: System.NullReferenceException Message: Object reference not set to an instance of an object. Source: SAS.OfficeAddin Target Site: GenerateInputStreamXml Stack Trace: at SAS.OfficeAddin.ExcelDataSource.GenerateInputStreamXml() at SAS.OfficeAddin.StoredProcess.PromptForOutputParameterLocations(Boolean bShowDialog) at SAS.OfficeAddin.StoredProcess.BeforeExecute(BeforeExecuteEventArgs e) at SAS.OfficeAddin.OfficeAddinBase.LaunchRunnable(LaunchRunnableArgs args) at SAS.OfficeAddin.OfficeAddinBase.DisplaySasContentsDialog() at SAS.OfficeAddin.RibbonManager.OnButtonClick(IRibbonControl control)

To avoid this problem, ensure that there are no empty cells in the range that you are using as input to the stored process.

Click the Hot Fix tab in this note to access the hot fix for this issue.



Operating System and Release Information

Product FamilyProductSystemProduct ReleaseSAS Release
ReportedFixed*ReportedFixed*
SAS SystemSAS Add-In for Microsoft OfficeWindows 7 Ultimate x647.127.139.4 TS1M39.4 TS1M3
Windows 7 Ultimate 32 bit7.127.139.4 TS1M39.4 TS1M3
Windows 7 Professional x647.127.139.4 TS1M39.4 TS1M3
Windows 7 Professional 32 bit7.127.139.4 TS1M39.4 TS1M3
Windows 7 Home Premium x647.127.139.4 TS1M39.4 TS1M3
Windows 7 Home Premium 32 bit7.127.139.4 TS1M39.4 TS1M3
Windows 7 Enterprise x647.127.139.4 TS1M39.4 TS1M3
Windows 7 Enterprise 32 bit7.127.139.4 TS1M39.4 TS1M3
Microsoft Windows Server 2012 Std7.127.139.4 TS1M39.4 TS1M3
Microsoft Windows Server 2012 R2 Std7.127.139.4 TS1M39.4 TS1M3
Microsoft Windows Server 2012 R2 Datacenter7.127.139.4 TS1M39.4 TS1M3
Microsoft Windows Server 2012 Datacenter7.127.139.4 TS1M39.4 TS1M3
Microsoft Windows Server 2008 for x647.127.139.4 TS1M39.4 TS1M3
Microsoft Windows Server 2008 R27.127.139.4 TS1M39.4 TS1M3
Microsoft Windows Server 20087.127.139.4 TS1M39.4 TS1M3
Microsoft Windows 107.127.139.4 TS1M39.4 TS1M3
Microsoft Windows 8.1 Pro x647.127.139.4 TS1M39.4 TS1M3
Microsoft Windows 8.1 Pro 32-bit7.127.139.4 TS1M39.4 TS1M3
Microsoft Windows 8.1 Enterprise x647.127.139.4 TS1M39.4 TS1M3
Microsoft Windows 8.1 Enterprise 32-bit7.127.139.4 TS1M39.4 TS1M3
Microsoft Windows 8 Pro x647.127.139.4 TS1M39.4 TS1M3
Microsoft Windows 8 Pro 32-bit7.127.139.4 TS1M39.4 TS1M3
Microsoft Windows 8 Enterprise x647.127.139.4 TS1M39.4 TS1M3
Microsoft Windows 8 Enterprise 32-bit7.127.139.4 TS1M39.4 TS1M3
Microsoft® Windows® for x647.127.139.4 TS1M39.4 TS1M3
* 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.