I suspect that there's something about the "Other" by group or group that is incompatible with options or sub-options you have specified. Without looking at your code -- at least the complete invocation statement, that's only a guess.
You might wish to open a track with Tech Support for more complete help. They can look at your data and look at your code and help you find a resolution.
Thanks for the response. Unfortunately, the 'Other' group was something of a red herring. However, I've managed to pinpoint the issue. If I take out the nozero option from the define statement (bbi_solus), I no longer receive the error. My next question is, are there limitations to the nozero option when used in combination with nesting variables. Some of the levels of the nesting variable are populated and some are blank. Would this cause issues when using the nozero option? I pasted below a copy of the code I'm running.
You might wish to work with Tech Support on this issue. This note explains that NOZERO is ignored by all destinations except for LISTING destination. http://support.sas.com/kb/31/262.html
I no longer have 9.1.3 to test with...so if you are using NOZERO in SAS 9.1.3, Tech Support will have to answer your question about how NOZERO might impact TAGSETS.EXCELXP output in SAS 9.1.3. My understanding is that if you are using SAS 9.2, that NOZERO is ignored except for LISTING. http://support.sas.com/documentation/cdl/en/proc/61895/HTML/default/a002473627.htm#a003072103 (references to "monospace output" means the LISTING destination in the documentation)
Again, if you are using SAS 9.1.3, you may want to work with Tech Support on this issue.