Cynthia, I did some more research on this issue and it looks like others have had this issue but using MS Project 2010. http://social.msdn.microsoft.com/Forums/en-US/adodotnetdataproviders/thread/961fa23c-fc03-4cae-a9e4-7c0e7910804b/ It seems to be if the file is going to be greater then 1mb is when I get the blank xlsx file.  My web page is not running sas all my web page does is collect parameters then it starts sas on our server and runs the sas program.  At that point SAS is doing all the data work and then creating the xlsx file. Thank you ... View more

Cynthia, Thank you.  I will discuss this for sure with my lead next week.  I don't want to spend more time just testing what will and won't work.  I need to find a solution and I think tech support will be the only way. I am running on 9.2 TS2M0 and I did try using EXCELCS and PCFILES and both gave me DBMS type EXCELCS not valid for export. Using the libname way to export goes through the same engine correct?  I'm going to look to see if there is other avenues to create the file till we contact tech support. Thank you again ... View more

Cynthia, Thank you for your reply. I understand what you are saying.  There are many variables at play that are giving me inconsistant results.  I will have to ask my lead next wee if I can contact tech support again.  Its weird that if I run the original program through SAS it works fine but through the web it does and doesn't.  But all the web page does is make a call to a sas program.  The program is what creates the data and the xlsx file.  I'm just curious if DBMS=EXCEL is the wrong one which other one would you guess it could be?  Thanks again for the quick replies.  In the situation i'm dealing with it is much appreciated. ... View more

Cynthia, Thank you so much for your help and patience.  I did find some interesting things. When I user selects they want their output in excel my macro includes a program that has this proc export: proc export data = work.&fname             outfile= "&path.\&file2..xlsx"             dbms=excel replace ; run ; if I run it like this it doesn't work.  If I add (obs=25059) after data it works.  If I change this to (obs=25060) it stops working. I also tried to just create 1 variable with 110,000 rows. data temp ;     do i = 1 to 110000 ;         output ;     end ;    run ; proc export data = work.temp             outfile= "d:\temp\temp.xlsx"             dbms=excel replace ; run ; This will work but if I change it to 115,000 it stops working again.  I get an empty xlsx file with both and a tab name with letters and numbers. Is there a file size limit?  Am I using the wrong dbms? Thank you so much for your help ... View more

Cynthia, Thank you again for all your help trying to get this figured out.  I am running  SAS 9.2 (TS2M0). I had to jump on a different project and just started looking at this issue again. Is there any known issue of doing a proc export within a macro for an xlsx file?  ... View more

Cynthia, Thanks for the help.  I will have to exhaust all my tests first.  My lead thinks it's a settings issue. I did create a test page and pointed it to a regular sas program that creates 100,000 rows and exports it to an xlsx fine.  There is some setting I think i'm missing. I have also tried the following within my macro and it is still blank even though the log says it has 42,000 rows LIBNAME xdb EXCEL PATH="&out.\&file..xlsx" ; data xdb.&name ;     set WORK.&name ; run ; If I change the xlsx to xls it works fine.  What is causing sas not to create that file through a macro but it can create an xlsx file through a sas program? Thank you again I do appreciate your help. ... View more

Cynthia, Thank you for your reply The server i'm running on is a windows server 2003.  This is a virtual server.  The sas version i'm running is 9.2 (TS2M0). I have a different portion of my website that allows users to select data and export in excel(xlsx) and that works. Could it be some type of permissions issue for my web user account? If I change it back to xls and excel2000 it works fine. The tab name of the xlsx file has all different letters and numbers. If I run my program on the server through sas it works fine.  Thank you for any help you can give me. ... View more

I'm not sure this is the same issue.  I don't see this line in my error "NOTE: SASHELP.PROFILE has been copied to WORK.PROFILE." Can a user work with SAS even if this error appears?  What gets disabled? Thank you ... View more

So change the shortcut to include -verbose? I was thinking it might be a permissions issue. Can I go into the config and point his -SASUSER to a location I know he has permissions too? Thanks for the help. ... View more

This was a new install on this machine.  I'm just the user of the machine.  I logged off of windows and had a co-worker try and he is able to open sas without this error.  Could it be my rights or priviliages as a windows user that is blocking this profile from loading? Tom where is the existing profile located?  Do I just delete it and restart SAS? ... View more