gulbis
2nd February 2010, 11:51
Hi all.

I am new to the forums and I hope someone is able to shed some light on a problem I have.

We have recently moved our Baan server to a new network in another location.

The clients are able to connect to the Baan and work normally on the new network except for some report functions.

I am not sure if this will come out correctly as we are running a German Baan installation, I am however not a native German speaker.

The problem I am having is that when a client tries to print to Word, Excel, Notepad, Email, nothing happens...

As an example here is what we have under Email Printer:

Command: RTF: outlook.exe /a %s
Path: email.rtf

Any help would be greatly appreciated.

ayushk
2nd February 2010, 12:31
On the client computer, go to Start menu ==> Run Program and run the executable "outlook.exe".

For the Baan device to work, Outlook must open when call from Run program

gulbis
2nd February 2010, 14:26
Hi there.

Thank you for your reply, but I'm afraid that is not the issue.

Outlook is open on the client computer.

The same problem occurs if the user tries to print to a Word doc or an Excel doc or a Notepad doc.

The hourglass comes up for a second and then nothing happens.

ayushk
2nd February 2010, 14:54
Sometimes reports do not print if there is no space on the server. Please check if $BSE/tmp on the server has space.

Also check if any error messages are logged in Event viewer or $BSE/log

gulbis
2nd February 2010, 17:52
$BSE/log has plenty of space.

Event viewer shows no signs of any errors relating to Baan.

gulbis
2nd February 2010, 18:44
I got it fixed.

Two problems existed. I didn't think this would have caused a problem but we had also moved the client software to new computers and the %BSE% Path was not defined. This fixed printing to word and excel.

The other problem with the Outlook part was that for some reason the "/a" switch was not present in the printer config. This fixed the Outlook problems.

zlatan24
10th February 2010, 19:46
I got it fixed.

Two problems existed. I didn't think this would have caused a problem but we had also moved the client software to new computers and the %BSE% Path was not defined. This fixed printing to word and excel.

The other problem with the Outlook part was that for some reason the "/a" switch was not present in the printer config. This fixed the Outlook problems.
So,I heard about some interesting tools and one of it were especial to my mind and I downloaded it-outlook message viewer (http://www.recoverytoolbox.com/outlook_pst_viewer.html).I was amazed,because application recovered all my old damaged mails in a minute and without payment.Moreover utility showed me how it decrypts *.ost format and extracts your data as a set of files in *.eml, *.txt and *.vcf formats.

preethish
8th September 2011, 14:55
I got it fixed.

Two problems existed. I didn't think this would have caused a problem but we had also moved the client software to new computers and the %BSE% Path was not defined. This fixed printing to word and excel.

The other problem with the Outlook part was that for some reason the "/a" switch was not present in the printer config. This fixed the Outlook problems.

Hi,

Can you tell me in detail how u solved that outlook prob. I am facing the same issue now.

Thanks in advance
Preethish