I have two cents here :-) Admittedly I don't deal with dbms much but as for
the connection problem; perhaps run it under the same account as you run
Sambar?
If it is creating a new connection each time it is accessed, then I can see
the connection limit being exceeded - but working around that so that you're
shifting the weight to be seen as an ongoing connection might make all the
difference.
Might work, might not. An idea to think about.
----- Original Message -----
From: "Michael J. Cook" <[EMAIL PROTECTED]>
To: "sambar List Member" <[EMAIL PROTECTED]>
Sent: Friday, December 06, 2002 5:42 PM
Subject: [sambar] System Resource Exceeded {01}
> >The other thing is that I'm running Samabar as a Service, and I read
> >in the Microsoft docs that need I may need licensing above 10
> >connections that uses Windows Server Services. Would Sambar as a
> >service not be regarded as a Windows Server Service?
>
> >Sambar should be seen as an app and not a Server Service in Windows.
>
> >The 10 connections only apply to Windows file & print services user
> >connections.
>
> >Alex
> >PS: Pls correct me if I'm wrong
>
> Alex,
>
> Why should Sambar be set up as an app and not a service? I thought there
were
> performance, functionality (fail then restart), and security advantages to
> running as a service.
>
> I gather from the list archives that the 10 connection limit applied to
Windows
> file and print sharing. However, the "System Resource Exceeded" error
message
> only occurred with Sambar's dbms functionality. As soon as that resource
was
> exceeded (through ODBC), Sambar dbms died, but other http requests
continued.
> when I checked my logs, I noticed that the "System Resource Exceeded"
error
> message refers to a 10 connection limit. So, I have a theory.
>
> First my set-up...
>
> Win2K Professional
> Sambar 5.1
> ODBC MDAC 2.7
> Typical Sambar dbms configuration:
> -Max Connections 100
> -Min Connections 1
> -Idle Timeout 1 min
>
> Now the theory...
>
> Windows ODBC is built to work with the Win2k OS (obviously). The OS sees
the 10
> connection limit that the ODBC is trying to exceed, refuses additional
> connections, and somehow kills ODBC and/or Sambar dbms stops responding.
>
> If I'm way out in left field, start calling me back in right now ;-))
> -------------------------------------------------------
> To unsubscribe please go to http://www.sambar.ch/list/
>
>
>
-------------------------------------------------------
To unsubscribe please go to http://www.sambar.ch/list/
