ODBC connections

Yahoo Archive
1
Thanks for the input.
I think have to blame my self for this. After more investigation I have an app making an ODBC connection to Vantage & in one of the calls I was failing to close the connection.


--- In vantage@yahoogroups.com, "Jerry W. Rodden" <jrodden@...> wrote:
>
> I am on 8.0.811 B version.
>
>
>
> I get the ODBC login from within Vantage whenever there is too many ODBC
> connections because the system wasn't releasing the connections like
> they were supposed to.
>
>
>
> You can stop and restart the database & app servers to clear or what I
> have done is to set up a Proman session on my Live Server. Since the
> ODBC connections are a "Progress" user, they show up in the users list
> in Proman. Option 8 Shut Down Database will allow you to disconnect the
> ODBC connections and open them back up for use.
>
>
>
> Be careful and only disconnect the odbcuser. (note the name of the
> progress user id we use for our ODBC connection is called odbcuser and
> so are easily identifiable.)
>
>
>
>
>
> Probably once a month I go in to Proman and clean out the odbcusers,
> especially ones that have old date time stamps.
>
>
>
> Worse case is that if you accidently delete an active ODBC connection,
> it recreates a new one and goes on its merry way.
>
>
>
> Jerry W. Rodden
>
> Staff Administrator
>
> Production Planning
>
> Cardington Yutaka Technologies Inc
>
> Phone: 419-864-8777 ext. 6209
>
> FAX: 419-864-7771
>
> jrodden@...
>
>
>
>
>
>
>
> [Non-text portions of this message have been removed]
>
2
We keep getting database login prompts for ODBC reports that started today.
The ODBC group is set to 32 servers but the mfgsys.lg file is giving no sql servers available error.

What is the best way to troubleshoot or fix this. This is the first time we are having this problem. Could there be some connections to the servers that are not getting released?
3
Is it happening on only Windows 7 workstations? That is where we are having the issue.

Kent



To: vantage@yahoogroups.com
From: mmcwilliams22@...
Date: Wed, 6 Apr 2011 17:31:28 +0000
Subject: [Vantage] ODBC connections






We keep getting database login prompts for ODBC reports that started today.
The ODBC group is set to 32 servers but the mfgsys.lg file is giving no sql servers available error.

What is the best way to troubleshoot or fix this. This is the first time we are having this problem. Could there be some connections to the servers that are not getting released?





[Non-text portions of this message have been removed]
4
Every workstation XP, Windows 7 and even our 2003 Terminal Server.


--- In vantage@yahoogroups.com, Kent Rooen <krrooen25@...> wrote:
>
>
> Is it happening on only Windows 7 workstations? That is where we are having the issue.
>
> Kent
>
>
>
> To: vantage@yahoogroups.com
> From: mmcwilliams22@...
> Date: Wed, 6 Apr 2011 17:31:28 +0000
> Subject: [Vantage] ODBC connections
>
>
>
>
>
>
> We keep getting database login prompts for ODBC reports that started today.
> The ODBC group is set to 32 servers but the mfgsys.lg file is giving no sql servers available error.
>
> What is the best way to troubleshoot or fix this. This is the first time we are having this problem. Could there be some connections to the servers that are not getting released?
>
>
>
>
>
> [Non-text portions of this message have been removed]
>
5
I actually walked around and found one user had 15 reports open at one time. I am not sure if it waits to release the connection until the report is closed or keeps it just while reading data. It seems to be OK after I booted them from Vantage but we shall see.

--- In vantage@yahoogroups.com, "mmcwilliams22" <mmcwilliams22@...> wrote:
>
> Every workstation XP, Windows 7 and even our 2003 Terminal Server.
>
>
> --- In vantage@yahoogroups.com, Kent Rooen <krrooen25@> wrote:
> >
> >
> > Is it happening on only Windows 7 workstations? That is where we are having the issue.
> >
> > Kent
> >
> >
> >
> > To: vantage@yahoogroups.com
> > From: mmcwilliams22@
> > Date: Wed, 6 Apr 2011 17:31:28 +0000
> > Subject: [Vantage] ODBC connections
> >
> >
> >
> >
> >
> >
> > We keep getting database login prompts for ODBC reports that started today.
> > The ODBC group is set to 32 servers but the mfgsys.lg file is giving no sql servers available error.
> >
> > What is the best way to troubleshoot or fix this. This is the first time we are having this problem. Could there be some connections to the servers that are not getting released?
> >
> >
> >
> >
> >
> > [Non-text portions of this message have been removed]
> >
>
6
Here's what we were told when we went live.
CR Bypass the login ID and prompt for a Crystal Report using an ODBC connection.
Summary: CR Bypass the login ID and prompt for a Crystal Report using an ODBC connection.
Book: Support Solutions
Page: 5947MPS

PROBLEM: Bypass the login ID and prompt for a Crystal Report using an ODBC connection.

A Crystal form that has been modified with a subreport written using an ODBC connection continues to prompt for the ODBC System DSN login ID and password parameters.

The ODBC Driver for Open Edge 10.0B must be installed on each client that will be using an ODBC modified report. See document 4778MPS for instructions on modifying a Crystal Report to use ODBC.

For V8.03, an ODBC driver is not necessary for a customer Crystal Report. See document 7931MPS for instructions on creating a Crystal Report from a BAQ within V8.03.

RESOLUTION:
1. Go to Start->Run, and type in REGEDIT.
2. This will bring up your Registry Editor.
3. Find the HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI.
4. Find your specific ODBC connection that is setup in your ODBC datasources and double-click on it.
5. Go up to the Edit -> New -> String Value in the menu.
6. Give your New String Value the name of User ID.
7. Then double-click and give it a value of sysprogress. (Or whatever your user id is setup to be.)
8. Repeat the process for your Password.
9. Exit the Registry.
10. In the SystemTaskAgent (System Management->Utilities->System Agent), under ODBC Connection, put in the User ID and Password above.
11. In the Progress Explorer Too, stop and start the TaskAgent and ProcessServer for this database.
12. Test your report and you should not get prompted.



--- In vantage@yahoogroups.com, "mmcwilliams22" <mmcwilliams22@...> wrote:
>
> We keep getting database login prompts for ODBC reports that started today.
> The ODBC group is set to 32 servers but the mfgsys.lg file is giving no sql servers available error.
>
> What is the best way to troubleshoot or fix this. This is the first time we are having this problem. Could there be some connections to the servers that are not getting released?
>
7
This is a completely different issue. All stations are setup correctly we need to make some adjusments to our mfgsys group and ODBC groups for the database. Too many people accessing things at once it what is seems to be. Or we have some connections that won't release.

--- In vantage@yahoogroups.com, "pklein256" <pklein@...> wrote:
>
> Here's what we were told when we went live.
> CR Bypass the login ID and prompt for a Crystal Report using an ODBC connection.
> Summary: CR Bypass the login ID and prompt for a Crystal Report using an ODBC connection.
> Book: Support Solutions
> Page: 5947MPS
>
> PROBLEM: Bypass the login ID and prompt for a Crystal Report using an ODBC connection.
>
> A Crystal form that has been modified with a subreport written using an ODBC connection continues to prompt for the ODBC System DSN login ID and password parameters.
>
> The ODBC Driver for Open Edge 10.0B must be installed on each client that will be using an ODBC modified report. See document 4778MPS for instructions on modifying a Crystal Report to use ODBC.
>
> For V8.03, an ODBC driver is not necessary for a customer Crystal Report. See document 7931MPS for instructions on creating a Crystal Report from a BAQ within V8.03.
>
> RESOLUTION:
> 1. Go to Start->Run, and type in REGEDIT.
> 2. This will bring up your Registry Editor.
> 3. Find the HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI.
> 4. Find your specific ODBC connection that is setup in your ODBC datasources and double-click on it.
> 5. Go up to the Edit -> New -> String Value in the menu.
> 6. Give your New String Value the name of User ID.
> 7. Then double-click and give it a value of sysprogress. (Or whatever your user id is setup to be.)
> 8. Repeat the process for your Password.
> 9. Exit the Registry.
> 10. In the SystemTaskAgent (System Management->Utilities->System Agent), under ODBC Connection, put in the User ID and Password above.
> 11. In the Progress Explorer Too, stop and start the TaskAgent and ProcessServer for this database.
> 12. Test your report and you should not get prompted.
>
>
>
> --- In vantage@yahoogroups.com, "mmcwilliams22" <mmcwilliams22@> wrote:
> >
> > We keep getting database login prompts for ODBC reports that started today.
> > The ODBC group is set to 32 servers but the mfgsys.lg file is giving no sql servers available error.
> >
> > What is the best way to troubleshoot or fix this. This is the first time we are having this problem. Could there be some connections to the servers that are not getting released?
> >
>
8
My guess is that the connections aren't releasing... at least that's
what we've run into over the years. I'm sure there's an elegant
solution to the problem but it's been intermittent for us so we haven't
invested a large chunk of time to resolve. When it becomes a problem we
just manually close the excess connections using Promon.



Mike



From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of mmcwilliams22
Sent: Thursday, April 07, 2011 12:15 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: ODBC connections





This is a completely different issue. All stations are setup correctly
we need to make some adjusments to our mfgsys group and ODBC groups for
the database. Too many people accessing things at once it what is seems
to be. Or we have some connections that won't release.

--- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ,
"pklein256" <pklein@...> wrote:
>
> Here's what we were told when we went live.
> CR Bypass the login ID and prompt for a Crystal Report using an ODBC
connection.
> Summary: CR Bypass the login ID and prompt for a Crystal Report using
an ODBC connection.
> Book: Support Solutions
> Page: 5947MPS
>
> PROBLEM: Bypass the login ID and prompt for a Crystal Report using an
ODBC connection.
>
> A Crystal form that has been modified with a subreport written using
an ODBC connection continues to prompt for the ODBC System DSN login ID
and password parameters.
>
> The ODBC Driver for Open Edge 10.0B must be installed on each client
that will be using an ODBC modified report. See document 4778MPS for
instructions on modifying a Crystal Report to use ODBC.
>
> For V8.03, an ODBC driver is not necessary for a customer Crystal
Report. See document 7931MPS for instructions on creating a Crystal
Report from a BAQ within V8.03.
>
> RESOLUTION:
> 1. Go to Start->Run, and type in REGEDIT.
> 2. This will bring up your Registry Editor.
> 3. Find the HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI.
> 4. Find your specific ODBC connection that is setup in your ODBC
datasources and double-click on it.
> 5. Go up to the Edit -> New -> String Value in the menu.
> 6. Give your New String Value the name of User ID.
> 7. Then double-click and give it a value of sysprogress. (Or whatever
your user id is setup to be.)
> 8. Repeat the process for your Password.
> 9. Exit the Registry.
> 10. In the SystemTaskAgent (System Management->Utilities->System
Agent), under ODBC Connection, put in the User ID and Password above.
> 11. In the Progress Explorer Too, stop and start the TaskAgent and
ProcessServer for this database.
> 12. Test your report and you should not get prompted.
>
>
>
> --- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ,
"mmcwilliams22" <mmcwilliams22@> wrote:
> >
> > We keep getting database login prompts for ODBC reports that started
today.
> > The ODBC group is set to 32 servers but the mfgsys.lg file is giving
no sql servers available error.
> >
> > What is the best way to troubleshoot or fix this. This is the first
time we are having this problem. Could there be some connections to the
servers that are not getting released?
> >
>




______________________________________________________________________
This email has been scanned by the Connor Manufacturing Services Email
Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________



[Non-text portions of this message have been removed]
9
I am on 8.0.811 B version.



I get the ODBC login from within Vantage whenever there is too many ODBC
connections because the system wasn't releasing the connections like
they were supposed to.



You can stop and restart the database & app servers to clear or what I
have done is to set up a Proman session on my Live Server. Since the
ODBC connections are a "Progress" user, they show up in the users list
in Proman. Option 8 Shut Down Database will allow you to disconnect the
ODBC connections and open them back up for use.



Be careful and only disconnect the odbcuser. (note the name of the
progress user id we use for our ODBC connection is called odbcuser and
so are easily identifiable.)





Probably once a month I go in to Proman and clean out the odbcusers,
especially ones that have old date time stamps.



Worse case is that if you accidently delete an active ODBC connection,
it recreates a new one and goes on its merry way.



Jerry W. Rodden

Staff Administrator

Production Planning

Cardington Yutaka Technologies Inc

Phone: 419-864-8777 ext. 6209

FAX: 419-864-7771

jrodden@...







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