-----Original Message-----
From: emerald-request@iea-software.com
[mailto:emerald-request@iea-software.com] On Behalf Of RedConnect Admin
Sent: Tuesday, May 11, 1999 10:10 PM
To: Emerald List
Subject: Re: [Emerald] REALLY URGENT! PLEASE STOP IGNORING THIS THREAD!!!
Need Help with ServerID Problem
I know I will probably be accussed of having the wrong attitude or some such
problem, but we have requested help (on this one error) politely and with
thanks for MONTHS now. YES MONTHS. IEA no longer responds to this thread
which I am sure there will be some excuse for. If you don't want to fix it
SAY SO!, my managers have now bought in other consultants to make your
software work and IT DOESN'T. INTSTRUCTIONS HAVE BEEN FOLLOWED EXPLICITLY.
Multiple installs on multiple machines with multiple configurations have
failed with the same problem. HOW MUCH MONEY DO YOU WANT TO HELP US or WHO
WANTS TO PURCHASE A 3000 MBR LICENCE. This situations is ridiculous and
please do not start with the wrong DLL or ADMIN version read all previous
emails. We have downloaded your software multiple times. We are evaluating
other vendors software (not that I think you care).
We are very disapointed that it has come down to this, but we are left with
no option but to try this shock email to get a response. Even if it is to
tell us you don't care, so we can once and for all migrate our service to a
product that has professional support services.
To replicate this problem with minimal external variables:
format drive
Install NT4.0 (sp 3 or 4) (NTFS or FAT)
Install SQL 6.5 (sp 3 or 4 or 5 or 5a)
[optionally run NT sp 3 or 4 again]
Create DSN (Emerald and or Radius)
Install full distribution of Emerald 2.5 accepting all defaults and
installing Radius and Authentication.
When finshed start emerald admin login: sa with no password as per SQL
default.
Database select <new>
follow directions for new install
when finished click on NT Admin and the Server ports tab and presto the
"Ambiguous Error" that has been previously documented by us appears.
Now I know you should configure and have data and blah blah blah... We have
done that and we still get the same error. IT DOES NOT make any difference
if we use data or a fresh install EXACTLY THE SAME ERROR appears. This in
our logic negates the issue of a data related problem UNLESS there is
something we need to modify that the CREATE AND UPGRADE scripts omit.
Finally, if you are unable to replicate this which we are assuming is going
to be your standard response. We request that the following happen:
Give us access to the ACTUAL FULL DISTRIBUTION YOU USE not the same version
(THE ACTUAL ZIP).
Itemise the following.
NT Service packs used (when applied)
SQL Version and Service packs (sp3 or > and when applied)
Emerald options selected on intial install (what check boxes)
this is the only way we can be sure everything is the same.
I am assuming someone will respond to this email, but we'll see!
[Below are some messages that have already been sent and are in the list
archive]
Sent on the 28th of April with no response
Dale the Version is 2.5.232, We only recently less than 2 weeks ago
downloaded the full 11 meg distribution to ensure we had a fully compatible
distribution. I know you are not aware of our skill level but we try and
debug as much as we can (including reading the manuals) before sending mail
to the list. This install has been done multiple times (6) on multiple
machines from scratch including operating system, SQL, Emerald, Radius. As
indicated above, we have the current full distributions that are on the IEA
site, we also downloaded this twice in the unlikely event of corruption. So
unless the distribution on your site is faulty, there is more to this than
old DLL's or the wrong version of a module or corrupt registry or any other
common problems usually assoiciated with users not making a sufficient
effort to resolve trivial problems.
We are under a lot of pressure to resolve this as our current system is
taking up to five hours to do a consolidation mostly due to the machine it
runs on. We have new hardware which we want to install with 2.5 on but after
a number of weeks we are still at the same point.
Your help is very much appreciated but our management is frustrated with us.
>Dale wrote:
>
>Its probably a bug in the Admin. What Admin version are you using?
>You can find it from Help...About in the Emerald Admin.
>>RedConnect Admin wrote:
>>
>> The server we are doing the upgrade on was a clean install of all
software,
>> OS (NT4.0 SP4), SQL 6.5, Emerald 2.5 full distribution. Then we put the
2.67
>> version on to see it would help. We have also re installed a number of
>> times, 2.1 has never been loaded on this machine