V8.03 printing Blank Title 53129

thank you Holly, Michael, and Bruce for your suggestions. I am going
goofy looking at PROPATH statements,
but I am no longer getting the "device not ready" error. Now the output
is going to the C:\mfgsysdata file on the server.
I can not find any path setting in the system agent or monitor or the
app servers that tell vantage to output the data there.
I am seriously considering taking my vantage 8 test server for a one-way
ride to Cuba.
thanks again for your help.




[Non-text portions of this message have been removed]
I am trying to print crystal forms out of 8.03. I verified that the
task processor is configured to the correct ports.
the XML output files are being sent to the mfgsysdata folder on the
server. I get a error message (viewable in the system monitor)
that states that the device is not ready. I am printing to a network
printer (which is the default printer for this client).
I uninstalled and reinstalled crystal runtime...started stopped the app
servers. Still no luck.
Has anyone encountered this, and does anyone have any ideas as to how to
overcome it?
regards,



[Non-text portions of this message have been removed]
Hello,

I can only suggest to check that ALL your task servers are directed to the correct ports. I had that problem recently, and although my Pilot database was setup correctly, my Test database was set to the Pilot ports, and that disabled printing functions in both databases.

Otherwise, it sounds like you covered everything I did. Good luck!
Holly
Cleveland, OH


----- Original Message ----
From: PLAMAN DICK <dplaman@...>
To: vantage@yahoogroups.com
Sent: Wednesday, November 15, 2006 11:41:43 AM
Subject: [Vantage] V8.03 printing

I am trying to print crystal forms out of 8.03. I verified that the
task processor is configured to the correct ports.
the XML output files are being sent to the mfgsysdata folder on the
server. I get a error message (viewable in the system monitor)
that states that the device is not ready. I am printing to a network
printer (which is the default printer for this client).
I uninstalled and reinstalled crystal runtime...started stopped the app
servers. Still no luck.
Has anyone encountered this, and does anyone have any ideas as to how to
overcome it?
regards,


[Non-text portions of this message have been removed]






[Non-text portions of this message have been removed]
I think I had this issue and The problem was the SystemAgent.
Although you have the correct ports if you look at the connection ID
it is not correct. I had to delete the SysAgent, the put it back in
and restart.

--- In vantage@yahoogroups.com, Holly Reed <hr.nook@...> wrote:
>
> Hello,
>
> I can only suggest to check that ALL your task servers are directed
to the correct ports. I had that problem recently, and although my
Pilot database was setup correctly, my Test database was set to the
Pilot ports, and that disabled printing functions in both databases.
>
> Otherwise, it sounds like you covered everything I did. Good luck!
> Holly
> Cleveland, OH
>
>
> ----- Original Message ----
> From: PLAMAN DICK <dplaman@...>
> To: vantage@yahoogroups.com
> Sent: Wednesday, November 15, 2006 11:41:43 AM
> Subject: [Vantage] V8.03 printing
>
> I am trying to print crystal forms out of 8.03. I verified that the
> task processor is configured to the correct ports.
> the XML output files are being sent to the mfgsysdata folder on the
> server. I get a error message (viewable in the system monitor)
> that states that the device is not ready. I am printing to a network
> printer (which is the default printer for this client).
> I uninstalled and reinstalled crystal runtime...started stopped the
app
> servers. Still no luck.
> Has anyone encountered this, and does anyone have any ideas as to
how to
> overcome it?
> regards,
>
>
> [Non-text portions of this message have been removed]
>
>
>
>
>
>
> [Non-text portions of this message have been removed]
>
I have run into this repeatedly each time we bring up a new copy of the
database to test with. I find the problem is usually with the paths in
the system agent. All my paths use UNC.



Bruce Butler

IT Manager

Knappe & Koester, Inc.

_____

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Michael McWilliams
Sent: Wednesday, November 15, 2006 2:59 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: V8.03 printing



I think I had this issue and The problem was the SystemAgent.
Although you have the correct ports if you look at the connection ID
it is not correct. I had to delete the SysAgent, the put it back in
and restart.

--- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ,
Holly Reed <hr.nook@...> wrote:
>
> Hello,
>
> I can only suggest to check that ALL your task servers are directed
to the correct ports. I had that problem recently, and although my
Pilot database was setup correctly, my Test database was set to the
Pilot ports, and that disabled printing functions in both databases.
>
> Otherwise, it sounds like you covered everything I did. Good luck!
> Holly
> Cleveland, OH
>
>
> ----- Original Message ----
> From: PLAMAN DICK <dplaman@...>
> To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> Sent: Wednesday, November 15, 2006 11:41:43 AM
> Subject: [Vantage] V8.03 printing
>
> I am trying to print crystal forms out of 8.03. I verified that the
> task processor is configured to the correct ports.
> the XML output files are being sent to the mfgsysdata folder on the
> server. I get a error message (viewable in the system monitor)
> that states that the device is not ready. I am printing to a network
> printer (which is the default printer for this client).
> I uninstalled and reinstalled crystal runtime...started stopped the
app
> servers. Still no luck.
> Has anyone encountered this, and does anyone have any ideas as to
how to
> overcome it?
> regards,
>
>
> [Non-text portions of this message have been removed]
>
>
>
>
>
>
> [Non-text portions of this message have been removed]
>





[Non-text portions of this message have been removed]
> I have run into this repeatedly each time we bring up a new copy of the
> database to test with. I find the problem is usually with the paths in
> the system agent. All my paths use UNC.

Absolutely it's usually something wrong with the System Agent setup. We had a
new one the other day. Before going live, we changed the password on the
MANAGER account. All printing stopped. I had forgotten that the system agent
needs a username and password to login. These credentials are entered on the
system agent screen.

Mark W.