9.05 Bug? Anomaly? Oddity?

Ned, I did have the same thing on a brand new install recently. When i called
support they said it was related to a bug they were having with logging levels.
I changed it as well and my app servers started.




________________________________
From: Ned <TechnoBabbly@...>
To: vantage@yahoogroups.com
Sent: Tue, November 16, 2010 9:45:48 AM
Subject: [Vantage] 9.05 Bug? Anomaly? Oddity?

Â
I was just curious if anyone had ever come across anything like this before.

I am in Epicor 9.05.601B 64-bit SQL, I just did the update, ran conversions
and everything seemed to be fine.

I then couldn't start the AppServers and was getting the good old
"IOException : Pipe to Server Broken (8117)" error.

I tested out all the traditional things that it could be, permissions, ODBC,
etc etc and none of those were working.

I then decided to set my logging to verbose to get more information to try
to solve the problem, and the problem went away, the AppServers would start.

I didn't believe this would be the actual solution so I tested it a few
times, changing the logging level and only the logging level of the
AppServers back and forth from Error Only to Verbose to Error Only, and
apparently that is why the AppServers weren't starting, I didn't have enough
logging setup.

Has anyone ever run into something like that? It defies any and all logic in
my mind.

Ned







[Non-text portions of this message have been removed]
I was just curious if anyone had ever come across anything like this before.

I am in Epicor 9.05.601B 64-bit SQL, I just did the update, ran conversions
and everything seemed to be fine.

I then couldn't start the AppServers and was getting the good old
"IOException : Pipe to Server Broken (8117)" error.

I tested out all the traditional things that it could be, permissions, ODBC,
etc etc and none of those were working.

I then decided to set my logging to verbose to get more information to try
to solve the problem, and the problem went away, the AppServers would start.

I didn't believe this would be the actual solution so I tested it a few
times, changing the logging level and only the logging level of the
AppServers back and forth from Error Only to Verbose to Error Only, and
apparently that is why the AppServers weren't starting, I didn't have enough
logging setup.

Has anyone ever run into something like that? It defies any and all logic in
my mind.

Ned
Yes, this is a bug! There is a bug in 9.05.600 that prevents the appservers from starting if the logging is set to 'verbose'. They "fixed" this in 9.05.601, but goofed the logic by stating that it can only start if logging is set to 'verbose'. I think there is an SCR on this.

:-)

Jennifer Mesiano
Walton Signage

--- In vantage@yahoogroups.com, "Ned" <TechnoBabbly@...> wrote:
>
> I was just curious if anyone had ever come across anything like this before.
>
> I am in Epicor 9.05.601B 64-bit SQL, I just did the update, ran conversions
> and everything seemed to be fine.
>
> I then couldn't start the AppServers and was getting the good old
> "IOException : Pipe to Server Broken (8117)" error.
>
> I tested out all the traditional things that it could be, permissions, ODBC,
> etc etc and none of those were working.
>
> I then decided to set my logging to verbose to get more information to try
> to solve the problem, and the problem went away, the AppServers would start.
>
> I didn't believe this would be the actual solution so I tested it a few
> times, changing the logging level and only the logging level of the
> AppServers back and forth from Error Only to Verbose to Error Only, and
> apparently that is why the AppServers weren't starting, I didn't have enough
> logging setup.
>
> Has anyone ever run into something like that? It defies any and all logic in
> my mind.
>
> Ned
>
Not sure if it's the same issue but it sounds like the same error we got
at one point. We didn't have pipes enabled under client protocols at
first. Once we enabled Named Pipes under SQL Server Configuration
Manager we connected fine.



As far as the app servers, I thought there was a recent bug fix that
required us to use Basic only. I had set it to error only because I had
a note that it was a bug fix at one point. When I couldn't get my app
servers to start last time, support did a webex and set them to Basic.
Those have to be set under Broker & Agent in each of the app servers
(process & task too).



Jennifer Lisser
Business Analyst
Dorner Mfg. Corp.







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