Message 2: Re: Remote Printing
from "Dale E. Reed Jr." <daler@iea-software.com>
Message 3: SQL Deadlock
from "Greg Dobinson" <gregd@kenora.com>
Message 4: Re: Remote Printing
from "Michael A. Davis Jr." <mike.davis@dcsol.com>
Message 5: Re: Remote Printing
from "Greg Dobinson" <gregd@kenora.com>
Message 6: Re: Remote Printing
from "Mohammed Ersan" <ersan@first.net.jo>
Message 7: Re: Remote Printing
from "Dale E. Reed Jr." <daler@iea-software.com>
Message 8: Re: SQL Deadlock
from "Dale E. Reed Jr." <daler@iea-software.com>
Message 9: Re: SQL Deadlock
from "Greg Dobinson" <gregd@kenora.com>
Message 10: Re: Remote Printing
from "Michael A. Davis Jr." <mike.davis@dcsol.com>
Message 11: Re: Remote Printing
from "Dale E. Reed Jr." <daler@iea-software.com>
Message 12: Re: SQL Deadlock
from "Dale E. Reed Jr." <daler@iea-software.com>
..------ ------ ------ ------ ------ ------ ------ ------ ------ ------.
| Message 1 |
'------ ------ ------ ------ ------ ------ ------ ------ ------ ------'
Subject: Re: Remote Printing
From: "Michael A. Davis Jr." <mike.davis@dcsol.com>
Date: Sat, 4 Jul 1998 20:24:55 -0400
I am also having problems getting invoices to print. I've created the DSN
as specified in the Emerald manual, and I've tried Trusted connection
checked and unchecked to no avail. It always tells me... The Emerald ODBC
DSN does not exist. You must create it before printing. But it's there...
really it is!
Mike
-----Original Message-----
From: Dale E. Reed Jr. <daler@iea-software.com>
To: emerald@iea-software.com <emerald@iea-software.com>
Date: Thursday, July 02, 1998 3:05 PM
Subject: Re: Remote Printing
>Daniel Wood wrote:
>>
>> I just set up a NT 4.0 machine to access use Emerald remotely. I can
>> get everything to work excepte the printing. When I set up the DSN
>> in the ODBC it can't seem to find the SQL Server. Emerald and the
>> SQL Enterprise can find the SQL Server just find. Does anybody have
>> any ideas on what I might be doing wrong.
>
>What version of ODBC are you using? If its 3.x are you specifying
>a trusted connection (which is the default and probably will not
>work) or use a name specified? Assuming you are not spelling the
>name incorrectly, its rare that once you have dblibe working (EM)
>that there is an odbc problem.
>
>--
>Dale E. Reed Jr. (daler@iea-software.com)
>_________________________________________________________________
> IEA Software, Inc. | RadiusNT, Emerald, and NT FAQs
> Internet Solutions for Today | http://www.iea-software.com
..------ ------ ------ ------ ------ ------ ------ ------ ------ ------.
| Message 2 |
'------ ------ ------ ------ ------ ------ ------ ------ ------ ------'
Subject: Re: Remote Printing
From: "Dale E. Reed Jr." <daler@iea-software.com>
Date: Sun, 05 Jul 1998 00:54:09 -0700
Michael A. Davis Jr. wrote:
>
> I am also having problems getting invoices to print. I've created the DSN
> as specified in the Emerald manual, and I've tried Trusted connection
> checked and unchecked to no avail. It always tells me... The Emerald ODBC
> DSN does not exist. You must create it before printing. But it's there...
> really it is!
Emerald 2.2 has an issue with the DSN and requiring it to be exactly
"Emerald". When its checking for the DSN, its does it case
sensitive.
-- Dale E. Reed Jr. (daler@iea-software.com)_________________________________________________________________ IEA Software, Inc. | RadiusNT, Emerald, and NT FAQs Internet Solutions for Today | http://www.iea-software.com
..------ ------ ------ ------ ------ ------ ------ ------ ------ ------.| Message 3 |'------ ------ ------ ------ ------ ------ ------ ------ ------ ------'Subject: SQL DeadlockFrom: "Greg Dobinson" <gregd@kenora.com>Date: Fri, 3 Jul 1998 16:25:54 -0500
In my quest to get the consolidation process to work I have come acrossthis error message when doing a consolidation 12 in the ISQL_w utility. SQL has detected a deadlock. Your connection has been chosen as thedeadlock victom.(not quite exactly of course).
I understand that a deadlock happens when two processes have locks on dataand each of the processes is waiting for the other to finish. How do Imake change it so the consolidation isn't picked as the deadlock victom?
I am running MS SQL Server 6.5 with SP4 on NT 4.0 SP3.
Thanks!
Greg Dobinson.
..------ ------ ------ ------ ------ ------ ------ ------ ------ ------.| Message 4 |'------ ------ ------ ------ ------ ------ ------ ------ ------ ------'Subject: Re: Remote PrintingFrom: "Michael A. Davis Jr." <mike.davis@dcsol.com>Date: Sun, 5 Jul 1998 09:56:58 -0400
I'm currently running 2.1.11 on this machine. I've double checked thespelling, and it is entered as "Emerald", but I've already tried it bothways. Any other ideas? Should I just upgrade the emerald on this machine?I've stuck with this version because it is the one you have available fromyour web site without going into the beta section. What is the currentsupported release?
Mike
-----Original Message-----From: Dale E. Reed Jr. <daler@iea-software.com>To: emerald@iea-software.com <emerald@iea-software.com>Date: Sunday, July 05, 1998 4:00 AMSubject: Re: Remote Printing
>Michael A. Davis Jr. wrote:>>>> I am also having problems getting invoices to print. I've created theDSN>> as specified in the Emerald manual, and I've tried Trusted connection>> checked and unchecked to no avail. It always tells me... The EmeraldODBC>> DSN does not exist. You must create it before printing. But it'sthere...>> really it is!>>Emerald 2.2 has an issue with the DSN and requiring it to be exactly>"Emerald". When its checking for the DSN, its does it case>sensitive.>>-->Dale E. Reed Jr. (daler@iea-software.com)>_________________________________________________________________> IEA Software, Inc. | RadiusNT, Emerald, and NT FAQs> Internet Solutions for Today | http://www.iea-software.com
..------ ------ ------ ------ ------ ------ ------ ------ ------ ------.| Message 5 |'------ ------ ------ ------ ------ ------ ------ ------ ------ ------'Subject: Re: Remote PrintingFrom: "Greg Dobinson" <gregd@kenora.com>Date: Tue, 5 May 1998 12:28:01 -0500
Try reinstalling the Emerald DSN. The same thing was happening to me andthat's how I solved it. (I'm not sure why but it did. Maybe it will workfor you as well.)
Greg Dobinson.
> From: Michael A. Davis Jr. <mike.davis@dcsol.com>> To: emerald@iea-software.com> Subject: Re: Remote Printing> Date: Saturday, July 04, 1998 7:24 PM> > I am also having problems getting invoices to print. I've created theDSN> as specified in the Emerald manual, and I've tried Trusted connection> checked and unchecked to no avail. It always tells me... The EmeraldODBC> DSN does not exist. You must create it before printing. But it'sthere...> really it is!> > Mike> > -----Original Message-----> From: Dale E. Reed Jr. <daler@iea-software.com>> To: emerald@iea-software.com <emerald@iea-software.com>> Date: Thursday, July 02, 1998 3:05 PM> Subject: Re: Remote Printing
..------ ------ ------ ------ ------ ------ ------ ------ ------ ------.| Message 6 |'------ ------ ------ ------ ------ ------ ------ ------ ------ ------'Subject: Re: Remote PrintingFrom: "Mohammed Ersan" <ersan@first.net.jo>Date: Sun, 05 Jul 1998 16:57:37 +0300
Hi Dale,
any news about emerald 2.5
At 09:56 AM 07/05/98 -0400, you wrote:
>I'm currently running 2.1.11 on this machine. I've double checked the
>spelling, and it is entered as "Emerald", but I've already tried it both
>ways. Any other ideas? Should I just upgrade the emerald on this machine?
>I've stuck with this version because it is the one you have available from
>your web site without going into the beta section. What is the current
>supported release?
>
>Mike
>
<center>Mohammed Ersan
ersan@first.net.jo
firstnet
</center>
..------ ------ ------ ------ ------ ------ ------ ------ ------ ------.| Message 7 |'------ ------ ------ ------ ------ ------ ------ ------ ------ ------'Subject: Re: Remote PrintingFrom: "Dale E. Reed Jr." <daler@iea-software.com>Date: Sun, 05 Jul 1998 16:16:08 -0700
Michael A. Davis Jr. wrote:> > I'm currently running 2.1.11 on this machine. I've double checked the> spelling, and it is entered as "Emerald", but I've already tried it both> ways. Any other ideas? Should I just upgrade the emerald on this machine?> I've stuck with this version because it is the one you have available from> your web site without going into the beta section. What is the current> supported release?
The 2.2 release (especially 2.2.38) is really stable and resolves manyof the printing problems. I would recommend anyone having problemsprinting install 2.2 on one machine and test it. The only reason2.2 isn't in the Emerald directory, is because we never officially released it. Most people are using it, though.
-- Dale E. Reed Jr. (daler@iea-software.com)_________________________________________________________________ IEA Software, Inc. | RadiusNT, Emerald, and NT FAQs Internet Solutions for Today | http://www.iea-software.com
..------ ------ ------ ------ ------ ------ ------ ------ ------ ------.| Message 8 |'------ ------ ------ ------ ------ ------ ------ ------ ------ ------'Subject: Re: SQL DeadlockFrom: "Dale E. Reed Jr." <daler@iea-software.com>Date: Sun, 05 Jul 1998 16:18:39 -0700
Greg Dobinson wrote:> > In my quest to get the consolidation process to work I have come across> this error message when doing a consolidation 12 in the ISQL_w utility.> SQL has detected a deadlock. Your connection has been chosen as the> deadlock victom.(not quite exactly of course).> > I understand that a deadlock happens when two processes have locks on data> and each of the processes is waiting for the other to finish. How do I> make change it so the consolidation isn't picked as the deadlock victom?> > I am running MS SQL Server 6.5 with SP4 on NT 4.0 SP3.
AFAIK, you can't. I'd be curious as to what could be contending withit for a lock, though. What else is running?
-- Dale E. Reed Jr. (daler@iea-software.com)_________________________________________________________________ IEA Software, Inc. | RadiusNT, Emerald, and NT FAQs Internet Solutions for Today | http://www.iea-software.com
..------ ------ ------ ------ ------ ------ ------ ------ ------ ------.| Message 9 |'------ ------ ------ ------ ------ ------ ------ ------ ------ ------'Subject: Re: SQL DeadlockFrom: "Greg Dobinson" <gregd@kenora.com>Date: Sun, 5 Jul 1998 19:44:33 -0500
Nothing else is using the SQL server for logging etc. However just todaywe tried another consolidation and this time things seem to beworking......??? Nothing that I can think of has changed since we lasttried and failed. The only thing I can think of is that there were fewerusers on when we tried and succeeded than when it was failing.
Any thoughts?(Not that I need to solve a solved problem but it would beinteresting to figure out what happened)
Greg.
----------> From: Dale E. Reed Jr. <daler@iea-software.com>> To: emerald@iea-software.com> Subject: Re: SQL Deadlock> Date: Sunday, July 05, 1998 6:18 PM> > Greg Dobinson wrote:> > > > In my quest to get the consolidation process to work I have come across> > this error message when doing a consolidation 12 in the ISQL_w utility.> > SQL has detected a deadlock. Your connection has been chosen as the> > deadlock victom.(not quite exactly of course).> > > > I understand that a deadlock happens when two processes have locks ondata> > and each of the processes is waiting for the other to finish. How do I> > make change it so the consolidation isn't picked as the deadlockvictom?> > > > I am running MS SQL Server 6.5 with SP4 on NT 4.0 SP3.> > AFAIK, you can't. I'd be curious as to what could be contending with> it for a lock, though. What else is running?> > -- > Dale E. Reed Jr. (daler@iea-software.com)> _________________________________________________________________> IEA Software, Inc. | RadiusNT, Emerald, and NT FAQs> Internet Solutions for Today | http://www.iea-software.com
..------ ------ ------ ------ ------ ------ ------ ------ ------ ------.| Message 10 |'------ ------ ------ ------ ------ ------ ------ ------ ------ ------'Subject: Re: Remote PrintingFrom: "Michael A. Davis Jr." <mike.davis@dcsol.com>Date: Sun, 5 Jul 1998 21:25:50 -0400
Are there any considerations at the server end with 2.2.38? Or can I justinstall it and run? I've never had any problems doing call consolidationwith my 2.1.11 installation and considered myself fortunate for that.Should I expect any required work arounds with 2.2.38?
Mike
-----Original Message-----From: Dale E. Reed Jr. <daler@iea-software.com>To: emerald@iea-software.com <emerald@iea-software.com>Date: Sunday, July 05, 1998 7:22 PMSubject: Re: Remote Printing
>>The 2.2 release (especially 2.2.38) is really stable and resolves many>of the printing problems. I would recommend anyone having problems>printing install 2.2 on one machine and test it. The only reason>2.2 isn't in the Emerald directory, is because we never officially>released it. Most people are using it, though.>>-->Dale E. Reed Jr. (daler@iea-software.com)>_________________________________________________________________> IEA Software, Inc. | RadiusNT, Emerald, and NT FAQs> Internet Solutions for Today | http://www.iea-software.com
..------ ------ ------ ------ ------ ------ ------ ------ ------ ------.| Message 11 |'------ ------ ------ ------ ------ ------ ------ ------ ------ ------'Subject: Re: Remote PrintingFrom: "Dale E. Reed Jr." <daler@iea-software.com>Date: Sun, 05 Jul 1998 22:43:20 -0700
Michael A. Davis Jr. wrote:> > Are there any considerations at the server end with 2.2.38? Or can I just> install it and run? I've never had any problems doing call consolidation> with my 2.1.11 installation and considered myself fortunate for that.> Should I expect any required work arounds with 2.2.38?
The only issue is that you have to install the Consolidation and DeleteCallsstored procs, which are in the consol.sql script. Other than that, I don'tthink there are any database upgrades required.
-- Dale E. Reed Jr. (daler@iea-software.com)_________________________________________________________________ IEA Software, Inc. | RadiusNT, Emerald, and NT FAQs Internet Solutions for Today | http://www.iea-software.com
..------ ------ ------ ------ ------ ------ ------ ------ ------ ------.| Message 12 |'------ ------ ------ ------ ------ ------ ------ ------ ------ ------'Subject: Re: SQL DeadlockFrom: "Dale E. Reed Jr." <daler@iea-software.com>Date: Sun, 05 Jul 1998 22:50:55 -0700
Greg Dobinson wrote:> > Nothing else is using the SQL server for logging etc. However just today> we tried another consolidation and this time things seem to be> working......??? Nothing that I can think of has changed since we last> tried and failed. The only thing I can think of is that there were fewer> users on when we tried and succeeded than when it was failing.> > Any thoughts?(Not that I need to solve a solved problem but it would be> interesting to figure out what happened)
The two typical problems with consolidation are the size of yourtempdb (typically needs to be about 12mb or larger) and how much freespace you have on your Emerald log segment. With Emerald 2.2, you cango into isql_w and execute:
Consolidation x
where x is the number you choose on the batch screen. It willeither return the full set of records, or give an error. Theerror should tell you the problem. You can do the same with theDeleteCalls if you have a failure on that part as well.
-- Dale E. Reed Jr. (daler@iea-software.com)_________________________________________________________________ IEA Software, Inc. | RadiusNT, Emerald, and NT FAQs Internet Solutions for Today | http://www.iea-software.com