VMware Horizon Community
nxion
Enthusiast
Enthusiast

Unable to see print preview in Excel 2007

So I am seeing a weird issue. All the other office products are able to produce the print preview except Excel. I get an error:

"Current printer unavaiable. Select another printer."

If you click th ok butten it shows the printers you are attached to, I select it and it still gives the above error. There is a setup button but when you press it, nothing happends. Also the is a networked printer and not a local one. Ive done the test and it seems that it does this with both local and networked.

Any ideas?

Reply
0 Kudos
7 Replies
nxion
Enthusiast
Enthusiast

To add to the above, the print function as well as the print preview produces the same errors.

Reply
0 Kudos
pbjork
VMware Employee
VMware Employee

Can you see anything releated to printing in your sandbox?

All other Office applications are in the same package and working?

nxion
Enthusiast
Enthusiast

Peter Bjork wrote:

Can you see anything releated to printing in your sandbox?

All other Office applications are in the same package and working?

As far as printing I see a spool folder lol. I deleted and rebuilt and still no change.

Yes, all others(Powerpoint, Word, Outlook) all work.

Reply
0 Kudos
pbjork
VMware Employee
VMware Employee

Do you see a spool folder in the Sandbox? You shouldn't..

Reply
0 Kudos
nxion
Enthusiast
Enthusiast

Im sorry, no I dont, I meant the Spool folder in the project folder. There is not a spool folder in the sandbox.

Reply
0 Kudos
Cievo
Commander
Commander

Can you, please, attach output dir /s from your Sandbox directory.

***Good question is half of the answer...***
Reply
0 Kudos
TobyFruthParson
Enthusiast
Enthusiast

The %SystemSystem%\spool folder is present by default and is set to Merged isolation mode by default.  If other apps work with these default settings then I would be hesitant to change them to accommodate Excel.

Perhaps you could capture Excel by itself, as a test, to see what happens.  Only capture Excel and the Office shared components.

Perhaps you could use the log monitor tool or Microsoft's process monitor to isolate the exact point at which the error occurs.

Toby Fruth, Sr. Specialist, The Parsons Corporation
Reply
0 Kudos