I have been using DotNetNuke (DNN) A LOT recently. For building a web framework, it absolutely rocks and is very easy to use. It is also very popular (I think 800k sites and growing) so there are loads of add-ons, videos, help guides, etc. Plus, it is free. I may need to put my demos site under it and showcase SAS a bit.
Normally, it is also pretty easy to use. Recently, though, I encountered a tough issue to debug.
I encountered the following error on opening the site:
An error has occurred. An error has occurred.
As I read up on it and understood it a bit more, lots of things can cause it. Basically, DNN has a serious error and it will not start.
To help diagnose it:
Go to the SQL Server database and open up the EventLog. Go to the last events in the log. An error on compilation or missing files typically will generate multiple entries. Look for the cluster of errors at the bottom of the log.For the first record of the error, select the LogProperties, right-click and copy. Save this to a…
Well, I recently was asked if I could support XPT files, you know, the SAS transport format. Well, SAS transport formats are documented and fairly straight-forward to read so 'why not?'.
Got started coding, client provided a nice sample, all went well. Around 8-10 hours after starting, I was happily reading SAS transport files and writing them to a tab-delimited file.
However, things weren't happy on Big Rock Candy Mountain.Seems the numbers were off. A little bit of reading in the SAS XPORT Documentation indicated the problem:
"All floating-point numbers in the file are stored using the IBM mainframe representation. If your application is to read from or write to transport files, it will be necessary to convert native floating-point numbers to or from the transport representation."
Not a problem. Let's go track down a C# library that handles IBM 370 floats and does the conversion. One small problem...I couldn't find one. What I did find was that this was…
Ok, so I am deep in the depths of the SAS Deployment Manager and am learning things the hard way (and spending time curled into a fetal position).
Ok, let's start with uninstall because it is this morning's pain point.
When creating a quiet uninstall, here is the command I was using:
"C:\Program Files\SAS 9.3.0 (SAS BI Solutions)\SASDeploymentManager\9.3\sasdm.exe" -uninstall -record -responsefile "c:\temp\uninstall2.txt"
I have highlighted in yellow my mistake. By including the -uninstall, the resulting responsefile was missing a critical component:
Why SAS does not ignore it, I am unsure of. How do you know it fails? Well, you don't easily. It seems to run, then just goes back to a command prompt. The sas.mif file will show a failure if you go and look at it:
cd %TEMP% type sas.mif
Watch this issue on the install as well. Per the SAS documentation:
If you use any other command line options while using record, those options are not incl…