Multi-user issue

I have a medium sized application running on Windows Mobile 5.0 devices.
This app was developed in VS 2005 and uses the Microsoft application blocks
for data access - running a stored proc. This app has been in use for
several years and works well. I've added a class for the unloading of
containers from our overseas operations. This app works well when one user
is scanning cases, but additional users keep getting kicked out. The
original user never has any trouble. When monitoring the SQL profiler I see
the "Audit Logout" message 7 or 8 times each time a user is kicked out. All
other functionality is working fine, we also have nearly 100 pc's running .
Net apps against this database - all with no problems. This one class/stored
proc is the only one giving trouble. The only real difference with this one
is that I am using the "SaveNoTransaction" method instead of the "Save"
method in the application blocks. I've looked at the code in this method and
see no problem there either. Any suggestions? I'm running out of ideas.
Thanks
Hi
"RickBentley" wrote:

> I have a medium sized application running on Windows Mobile 5.0 devices.
> This app was developed in VS 2005 and uses the Microsoft application blocks
> for data access - running a stored proc. This app has been in use for
> several years and works well. I've added a class for the unloading of
> containers from our overseas operations. This app works well when one user
> is scanning cases, but additional users keep getting kicked out. The
> original user never has any trouble. When monitoring the SQL profiler I see
> the "Audit Logout" message 7 or 8 times each time a user is kicked out. All
> other functionality is working fine, we also have nearly 100 pc's running .
> Net apps against this database - all with no problems. This one class/stored
> proc is the only one giving trouble. The only real difference with this one
> is that I am using the "SaveNoTransaction" method instead of the "Save"
> method in the application blocks. I've looked at the code in this method and
> see no problem there either. Any suggestions? I'm running out of ideas.
> Thanks
>
With the audit logouts I would expect that the connection is deliberately
being closed. Have you got try-catch blocks in the code to trap errors? Have
you also looked at the Errors and Warnings exceptions in Profiler?
John

Multi-user issue

I have a medium sized application running on Windows Mobile 5.0 devices.
This app was developed in VS 2005 and uses the Microsoft application blocks
for data access - running a stored proc. This app has been in use for
several years and works well. I've added a class for the unloading of
containers from our overseas operations. This app works well when one user
is scanning cases, but additional users keep getting kicked out. The
original user never has any trouble. When monitoring the SQL profiler I see
the "Audit Logout" message 7 or 8 times each time a user is kicked out. All
other functionality is working fine, we also have nearly 100 pc's running .
Net apps against this database - all with no problems. This one class/stored
proc is the only one giving trouble. The only real difference with this one
is that I am using the "SaveNoTransaction" method instead of the "Save"
method in the application blocks. I've looked at the code in this method and
see no problem there either. Any suggestions? I'm running out of ideas.
ThanksHi
"RickBentley" wrote:
> I have a medium sized application running on Windows Mobile 5.0 devices.
> This app was developed in VS 2005 and uses the Microsoft application blocks
> for data access - running a stored proc. This app has been in use for
> several years and works well. I've added a class for the unloading of
> containers from our overseas operations. This app works well when one user
> is scanning cases, but additional users keep getting kicked out. The
> original user never has any trouble. When monitoring the SQL profiler I see
> the "Audit Logout" message 7 or 8 times each time a user is kicked out. All
> other functionality is working fine, we also have nearly 100 pc's running .
> Net apps against this database - all with no problems. This one class/stored
> proc is the only one giving trouble. The only real difference with this one
> is that I am using the "SaveNoTransaction" method instead of the "Save"
> method in the application blocks. I've looked at the code in this method and
> see no problem there either. Any suggestions? I'm running out of ideas.
> Thanks
>
With the audit logouts I would expect that the connection is deliberately
being closed. Have you got try-catch blocks in the code to trap errors? Have
you also looked at the Errors and Warnings exceptions in Profiler?
John

Multi-user issue

I have a medium sized application running on Windows Mobile 5.0 devices.
This app was developed in VS 2005 and uses the Microsoft application blocks
for data access - running a stored proc. This app has been in use for
several years and works well. I've added a class for the unloading of
containers from our overseas operations. This app works well when one user
is scanning cases, but additional users keep getting kicked out. The
original user never has any trouble. When monitoring the SQL profiler I see
the "Audit Logout" message 7 or 8 times each time a user is kicked out. All
other functionality is working fine, we also have nearly 100 pc's running .
Net apps against this database - all with no problems. This one class/store
d
proc is the only one giving trouble. The only real difference with this one
is that I am using the "SaveNoTransaction" method instead of the "Save"
method in the application blocks. I've looked at the code in this method an
d
see no problem there either. Any suggestions? I'm running out of ideas.
ThanksHi
"RickBentley" wrote:

> I have a medium sized application running on Windows Mobile 5.0 devices.
> This app was developed in VS 2005 and uses the Microsoft application block
s
> for data access - running a stored proc. This app has been in use for
> several years and works well. I've added a class for the unloading of
> containers from our overseas operations. This app works well when one use
r
> is scanning cases, but additional users keep getting kicked out. The
> original user never has any trouble. When monitoring the SQL profiler I s
ee
> the "Audit Logout" message 7 or 8 times each time a user is kicked out. A
ll
> other functionality is working fine, we also have nearly 100 pc's running
.
> Net apps against this database - all with no problems. This one class/sto
red
> proc is the only one giving trouble. The only real difference with this o
ne
> is that I am using the "SaveNoTransaction" method instead of the "Save"
> method in the application blocks. I've looked at the code in this method
and
> see no problem there either. Any suggestions? I'm running out of ideas.
> Thanks
>
With the audit logouts I would expect that the connection is deliberately
being closed. Have you got try-catch blocks in the code to trap errors? Have
you also looked at the Errors and Warnings exceptions in Profiler?
John

Multi-user environment

Hi,
I’m working on a project that has MSDE installed on a Server (Windows Small
Business Server 2003 Standard with Veritas Backup V.9.1) for the back-end
database and for the front-end an Access Project (.adp) which I plan to have
on each user's computer.
The Server Administrator is pushing for an update to SBS 2003 Premium with 5
licenses as the only solution. Personally I think MSDE would do the job…
There are few things I’m not so sure:
- How many users can access the server at the same time with MSDE?
- Is there a way to let the user know if a record is being used? Like
displaying a message before any changes are made?
- I’ve created a table for users with username, password and group they
belong to. Is there a way to integrate this with the MSDE Groups and
Permissions or Transact-SQL? So Users, passwords and Groups can be setup from
a form in the front-end.
I’m doing some research on Veritas and see if it would backup the Instance
of MSDE.
Any help on this matter would be greatly appreciated
gaba
hi,
gaba wrote:
> - How many users can access the server at the same time with MSDE?
it's not a matter of users but concurrent batches... a study by Microsoft
indicates a magic number of 25, but it really depends on the application
type/design, database type/design...
of course bad ADO serverside cursors design will be worse then excellent
clientside disconnected design code...
but actually there's no limit, just the buuilt-in Workloads Gevernor that
kicks in when more then 8 concurrent batches are in progress... you can have
a look at
http://msdn.microsoft.com/library/?u...asp?frame=true
fro further info about that governor...

> - Is there a way to let the user know if a record is being used? Like
> displaying a message before any changes are made?
actually not... you have to test saving and trap the relative exception...

> - I've created a table for users with username, password and group
> they belong to. Is there a way to integrate this with the MSDE Groups
> and Permissions or Transact-SQL? So Users, passwords and Groups can
> be setup from a form in the front-end.
I think you've better drop your user tables and rely on the standard SQL
Server users and roles...you are duplicating all and incurring in troubles..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Andrea,
Thanks so much for your answer. I see I need to change directions in few
settings but I'm on the right track. A lot of information to catch up...
gaba
"gaba" wrote:

> Hi,
> I’m working on a project that has MSDE installed on a Server (Windows Small
> Business Server 2003 Standard with Veritas Backup V.9.1) for the back-end
> database and for the front-end an Access Project (.adp) which I plan to have
> on each user's computer.
> The Server Administrator is pushing for an update to SBS 2003 Premium with 5
> licenses as the only solution. Personally I think MSDE would do the job…
> There are few things I’m not so sure:
> - How many users can access the server at the same time with MSDE?
> - Is there a way to let the user know if a record is being used? Like
> displaying a message before any changes are made?
> - I’ve created a table for users with username, password and group they
> belong to. Is there a way to integrate this with the MSDE Groups and
> Permissions or Transact-SQL? So Users, passwords and Groups can be setup from
> a form in the front-end.
> I’m doing some research on Veritas and see if it would backup the Instance
> of MSDE.
> Any help on this matter would be greatly appreciated
> --
> gaba
sql

Multiuser Databinding in SQL Server 2000?

Hi

I am developing one multi user application in windows environment using VC++ .NET with SQL Server 2000. How Can I create dataset for multi user data updating in my SQL Server 2000. Where I can get help and sample code?

Thanks

Jose

Jose,

The DataSet is an off-line data cache. The DataAdapter is used to submit the pending changes stored in the DataSet. In the DataAdapter's updating logic, you can specify your own concurrency options to control whether you want to use a "last in wins" approach with only the primary key column(s) in the WHERE clause, or use other columns in the WHERE clause to ensure you don't overwrite changes made by another user.

I hope this information proves helpful.

David Sceppa
ADO.NET Program Manager
Microsoft|||Hi

Thankyou for the nice explanation. One more question how can I write custom primary key value. for example (50710000001) like this. 5 is for year, 07 is for month, 10 is for place, and remaining is unique automatic generating number. How can I write program in SQL Server 2000.

Regards,
Jose

Multiples Instance of SQL server 2000/SQL server 7.0 on Windows server 2003

Hi,

Is it possible to install on a Windows server 2003,
SQL SERVER 2000 in the folowing configuration :

SQL server 7.0 as a default Instance

and

SQL server 2000 as a named instance.

Thanks for your answer.riless (g.carali@.voila.fr) writes:
> Is it possible to install on a Windows server 2003,
> SQL SERVER 2000 in the folowing configuration :
> SQL server 7.0 as a default Instance
> and
> SQL server 2000 as a named instance.

If SQL 7 can be installed on Win2003, yes. But I would not really
expect SQL 7 to be welcome on Windows 2003, although I don't know
for sure. If it installs, it may still noe be supported.

For SQL 2000 you need SP3 to run on Win 2003. That I know.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp

multiple tables

hi,

I have 3 tables: Unix, Windows & Sybase

there are 3 dropdownlists in .asp page,

dropdown1=<displays the lists of table> (Unix, Windows & Sybase) variable as @.table

dropdown2=<displays the list of Columns from the dropdown1 selected table> variable as @.server

dropdown3=<displays the list of Row Header from the dropdown1 selected table> variable as @.user

how shal i define the select statement for this:

it should be something like,

Select * from @.table WHERE Server= @.server AND Row-Header = @.user

I appreciate if you could kindly help me in getting the correct syntax, thanx in advance.

Hi,

the tablename cannot be defined at runtime without using dynamic Sql, compose your SQLString first (e.g. in a stored procedure) then execute it via sp_executesql:

DECLARE @.SQLString VARCHAR(4000)

SET @.SQLString ='Select * from ' + @.table + ' WHERE Server= ''' + @.server + ''' AND Row-Header = ''' + @.user + ''''

But keep in mind that dynamic sql can be dangerous, read the aarticle of Erland first: http://www.sommarskog.se/dynamic_sql.html

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de
--

|||

hi,

Thanks a million Jens,

I have done the same way as you explained ( First line: DECLARE @.SQLString VARCHAR(4000) Second line: SET @.SQLString ='Select * from ' + @.table + ' WHERE Server= ''' + @.server + ''' AND Row-Header = ''' + @.user + '''').executed the .asp page: it shows only the dropdown & no table. Appreciate your help, many thanks again for this:

-

execution script part:
-
<script runat="server">
Sub OSClick1(ByVal sender As Object, ByVal e As EventArgs)
'EXEC "@.SQLString"'
End Sub
</script>
-
processing script part:
-
<asp:Button ID="btnOSClick1" runat="server" Text="Get" Width="90px" OnClick="OSClick1" /><br />
<br />
<asp:GridView ID="GridView1" runat="server" DataSourceID="SqlDataSource4">
</asp:GridView>
<asp:SqlDataSource ID="SqlDataSource4" runat="server" ConnectionString="<%$ ConnectionStrings:Unix.Primary %>"
SelectCommand="CREATE PROCEDURE general_select @.table nvarchar(127), @.server nvarchar(127), @.user nvarchar(127),&#13;&#10;DECLARE @.SQLString VARCHAR(4000)&#13;&#10;SET @.SQLString ='Select * from ' + @.table + ' WHERE Server= ''' + @.server + ''' AND Row-Header = ''' + @.user + ''''&#13;&#10;'">
<SelectParameters>
<asp:ControlParameter ControlID="txtOS" Name="table" PropertyName="SelectedValue" />
<asp:ControlParameter ControlID="txtSrvUnix" Name="server" PropertyName="SelectedValue" />
<asp:ControlParameter ControlID="txtUnixDes" Name="user" PropertyName="SelectedValue" />
<asp:Parameter Name="SQLString" />
</SelectParameters>
</asp:SqlDataSource>
-

|||Hi,

I am not very familiar with those new SQLDataSource mechanism, but you do not need to create the procedure as a Select Command. Create the procedure before and do just execute the procedure as the Select Command. In plain C# code you will have to assign the Commandtype = StoredProcedure first to the Select command (You will probably have to do this here also) and then just write something like SelectCommand="general_Select"

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de

MULTIPLE SQL INSTANCES

SQL 2K / WINDOWS 2003 SERVER
I have a box with 2 SQL INSTANCES and each instances with few databases.
Memory is setup to 'Use a fix memory size' and setup with half and one GB
each .
Almost 250 GB free hard-disk space and both instances using 4 processors.
I have different SQL jobs running on each instances.
My issue is , few jobs which usually runs within 4-5 hrs, running for 12-15
hrs and this is not happening always.
Checked for SQL LOCKS and found NONE.
Please advice me , how to trouble-shoot this ?
Rgds
MS-USER
Hi
Without knowing the nature of the jobs it is hard to give detailed advice,
but I would start by looking at performance monitor and try and see if there
is a bottleneck. Your may well have contention on the discs as this is a
common resource that each instance will be competing with, therefore disc
queue lengths, also if your logs and data are on the same set of discs there
potentially there would be problems even with a single instance. Another area
that may cause problems is processor affinity. You may want to change the
affinity mask and see if that helps or use the MAXDOPS hint on your queries.
You may want to read the SQL Server 2000 Performance Tuning Technical
Reference Manual ISBN ISBN 0-7356-1270-6 and Inside SQL Server 2000 by Kalen
Delaney ISBN 0-7356-0998-5
John
"MS User" wrote:

> SQL 2K / WINDOWS 2003 SERVER
> I have a box with 2 SQL INSTANCES and each instances with few databases.
> Memory is setup to 'Use a fix memory size' and setup with half and one GB
> each .
> Almost 250 GB free hard-disk space and both instances using 4 processors.
> I have different SQL jobs running on each instances.
> My issue is , few jobs which usually runs within 4-5 hrs, running for 12-15
> hrs and this is not happening always.
> Checked for SQL LOCKS and found NONE.
> Please advice me , how to trouble-shoot this ?
> Rgds
> MS-USER
>
>

MULTIPLE SQL INSTANCES

SQL 2K / WINDOWS 2003 SERVER
I have a box with 2 SQL INSTANCES and each instances with few databases.
Memory is setup to 'Use a fix memory size' and setup with half and one GB
each .
Almost 250 GB free hard-disk space and both instances using 4 processors.
I have different SQL jobs running on each instances.
My issue is , few jobs which usually runs within 4-5 hrs, running for 12-15
hrs and this is not happening always.
Checked for SQL LOCKS and found NONE.
Please advice me , how to trouble-shoot this '
Rgds
MS-USERHi
Without knowing the nature of the jobs it is hard to give detailed advice,
but I would start by looking at performance monitor and try and see if there
is a bottleneck. Your may well have contention on the discs as this is a
common resource that each instance will be competing with, therefore disc
queue lengths, also if your logs and data are on the same set of discs there
potentially there would be problems even with a single instance. Another area
that may cause problems is processor affinity. You may want to change the
affinity mask and see if that helps or use the MAXDOPS hint on your queries.
You may want to read the SQL Server 2000 Performance Tuning Technical
Reference Manual ISBN ISBN 0-7356-1270-6 and Inside SQL Server 2000 by Kalen
Delaney ISBN 0-7356-0998-5
John
"MS User" wrote:
> SQL 2K / WINDOWS 2003 SERVER
> I have a box with 2 SQL INSTANCES and each instances with few databases.
> Memory is setup to 'Use a fix memory size' and setup with half and one GB
> each .
> Almost 250 GB free hard-disk space and both instances using 4 processors.
> I have different SQL jobs running on each instances.
> My issue is , few jobs which usually runs within 4-5 hrs, running for 12-15
> hrs and this is not happening always.
> Checked for SQL LOCKS and found NONE.
> Please advice me , how to trouble-shoot this '
> Rgds
> MS-USER
>
>

MULTIPLE SQL INSTANCES

SQL 2K / WINDOWS 2003 SERVER
I have a box with 2 SQL INSTANCES and each instances with few databases.
Memory is setup to 'Use a fix memory size' and setup with half and one GB
each .
Almost 250 GB free hard-disk space and both instances using 4 processors.
I have different SQL jobs running on each instances.
My issue is , few jobs which usually runs within 4-5 hrs, running for 12-15
hrs and this is not happening always.
Checked for SQL LOCKS and found NONE.
Please advice me , how to trouble-shoot this '
Rgds
MS-USERHi
Without knowing the nature of the jobs it is hard to give detailed advice,
but I would start by looking at performance monitor and try and see if there
is a bottleneck. Your may well have contention on the discs as this is a
common resource that each instance will be competing with, therefore disc
queue lengths, also if your logs and data are on the same set of discs there
potentially there would be problems even with a single instance. Another are
a
that may cause problems is processor affinity. You may want to change the
affinity mask and see if that helps or use the MAXDOPS hint on your queries.
You may want to read the SQL Server 2000 Performance Tuning Technical
Reference Manual ISBN ISBN 0-7356-1270-6 and Inside SQL Server 2000 by Kalen
Delaney ISBN 0-7356-0998-5
John
"MS User" wrote:

> SQL 2K / WINDOWS 2003 SERVER
> I have a box with 2 SQL INSTANCES and each instances with few databases.
> Memory is setup to 'Use a fix memory size' and setup with half and one GB
> each .
> Almost 250 GB free hard-disk space and both instances using 4 processors.
> I have different SQL jobs running on each instances.
> My issue is , few jobs which usually runs within 4-5 hrs, running for 12-1
5
> hrs and this is not happening always.
> Checked for SQL LOCKS and found NONE.
> Please advice me , how to trouble-shoot this '
> Rgds
> MS-USER
>
>

Multiple simultaneous osql network connections fail

I am attempting to make 1000 simultaneous osql connections from one Windows
2000 server with sp4 to another Windows 2000 sever with sp4 that is hosting
a SQL 2000 server database with sp3a, but I reach an upper limit of about
30 - 40 connections.
Is osql limited to the number of simultaneous connections it can open to
another server? The database server isn't limited, so it must be the
client. If so, can that be increased?There isn't an OSQL limitation for connection requests other than the
resources on the box. There's something else going on if you can only make
30 to 40 connections. What happens when you try to make the 41st
connection? What error does the client receive?
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||This is the error I get for the jobs that failed after, in this case,
submitting 50 osql jobs simultaneously. 42 succeeded and 8 did not.
Application popup: osql.exe - Application Error : The application failed to
initialize properly (0xc0000142). Click on OK to terminate the application.
event id 26
"Kevin McDonnell [MSFT]" <kevmc@.online.microsoft.com> wrote in message
news:kMxpahY0DHA.3564@.cpmsftngxa07.phx.gbl...

quote:

---

> There isn't an OSQL limitation for connection requests other than the
> resources on the box. There's something else going on if you can only

---

make

quote:

---

> 30 to 40 connections. What happens when you try to make the 41st
> connection? What error does the client receive?
>
> Thanks,
> Kevin McDonnell
> Microsoft Corporation
> This posting is provided AS IS with no warranties, and confers no rights.
>
>

---

|||SQL Server uses a non-interactive desktop heap. The non-interactive desktop
heap
may run out of memory if a lot of processes are created. When there is not
sufficient memory to satisfy an
allocation request, an error is returned and the user is notified that the
computer is low on memory. Some programs may not handle the
failure, and sometimes there may not be sufficient memory to create the
error
message dialog box. When there is not sufficient memory to create the error
message dialog box, the requested operation may fail without generating an
error message.
WARNING: If you use Registry Editor incorrectly, you may cause serious
problems that may require you to reinstall your operating system. Microsoft
cannot guarantee that you can solve problems that result from using
Registry
Editor incorrectly. Use Registry Editor at your own risk.
To work around this problem, follow these steps:
1. At a command prompt, type "REGEDT32.EXE" to start Registry Editor.
2. In Registry Editor, locate the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControl
Set\Control\Session
Manager\SubSystems
3. In the right pane of Registry Editor, click "Windows".
4. On the "Edit" menu, click "Modify".
5. In the "Edit String" dialog box, locate the "SharedSection"
parameter string in the "Value
data" text box, and then specify an increased value for the
"SharedSection" parameter.
Note The SharedSection parameter specifies the system and desktop by using
the following
format, where <<xxxx>> defines the maximum size of the system-wide heap
(in
kilobytes), <<yyyy>> defines the size of the per desktop heap, and
<<zzzz>> is the size of the desktop heap for each desktop that is
associated with a non-interactive Windows station:
SharedSection=<<xxxx>>,<<yyyy>>,<<zzzz>>
6. Click "OK".
Increasing the non-interactive desktop heap by 256K or 512K
typically provides sufficient memory to resolve the problem.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Does Windows Server 2003 still have the 48 MB limitation in
system-wide space for the heaps?
David Martin
kevmc@.online.microsoft.com (Kevin McDonnell [MSFT]) wrote in message news:<WfRfCD90DHA.2256@.cpmsftngxa07
.phx.gbl>...

quote:

---

> SQL Server uses a non-interactive desktop heap. The non-interactive deskto
p
> heap
> may run out of memory if a lot of processes are created. When there is not
> sufficient memory to satisfy an
> allocation request, an error is returned and the user is notified that the
> computer is low on memory. Some programs may not handle the
> failure, and sometimes there may not be sufficient memory to create the
> error
> message dialog box. When there is not sufficient memory to create the erro
r
> message dialog box, the requested operation may fail without generating an
> error message.
>
> WARNING: If you use Registry Editor incorrectly, you may cause serious
> problems that may require you to reinstall your operating system. Microso
ft
> cannot guarantee that you can solve problems that result from using
> Registry
> Editor incorrectly. Use Registry Editor at your own risk.
>
> To work around this problem, follow these steps:
> 1. At a command prompt, type "REGEDT32.EXE" to start Registry Editor.
> 2. In Registry Editor, locate the following registry key:
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControl
Set\Control\Session
> Manager\SubSystems
> 3. In the right pane of Registry Editor, click "Windows".
> 4. On the "Edit" menu, click "Modify".
> 5. In the "Edit String" dialog box, locate the "SharedSection"
> parameter string in the "Value
> data" text box, and then specify an increased value for the
> "SharedSection" parameter.
> Note The SharedSection parameter specifies the system and desktop by using
> the following
> format, where <<xxxx>> defines the maximum size of the system-wide hea
p
> (in
> kilobytes), <<yyyy>> defines the size of the per desktop heap, and
> <<zzzz>> is the size of the desktop heap for each desktop that is
> associated with a non-interactive Windows station:
> SharedSection=<<xxxx>>,<<yyyy>>,<<zzzz>>
> 6. Click "OK".
>
> Increasing the non-interactive desktop heap by 256K or 512K
> typically provides sufficient memory to resolve the problem.
>
> Thanks,
> Kevin McDonnell
> Microsoft Corporation
> This posting is provided AS IS with no warranties, and confers no rights.

---

|||The Windows 2003 default setting is:
SharedSection=1024,3072,512
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||That did the trick.
Thanks!
"Kevin McDonnell [MSFT]" <kevmc@.online.microsoft.com> wrote in message
news:d9bDOnU1DHA.3564@.cpmsftngxa07.phx.gbl...

quote:

---

> The Windows 2003 default setting is:
> SharedSection=1024,3072,512
> Thanks,
> Kevin McDonnell
> Microsoft Corporation
> This posting is provided AS IS with no warranties, and confers no rights.
>
>

---

|||I'm having a problem that I think is related to this non-interactive
desktop heap thing. In Windows 2003, I'm using ASP.NET to start a
large number of processes (about 250 processes that use very little CPU
and about 2KB per process). After the first 150 or so are started, I
get the "The application failed to initialize properly (0xc0000142)"
error. The processes show up in Windows Task Manager but don't
function properly. The ASP.NET application runs in its own application
pool that runs under the System account. Also, after attempting to
launch this large number of processes from an ASP.NET page, all other
ASP.NET pages running under the same application pool randomly get a
"Compiler Error 128". I've tried changing the SharedSection key to
1024,3072,1024 which should be more than sufficient if this is the
problem. Any suggestions?
Kevin McDonnell [MSFT] wrote:
> *The Windows 2003 default setting is:
> SharedSection=1024,3072,512
> Thanks,
> Kevin McDonnell
> Microsoft Corporation
> This posting is provided AS IS with no warranties, and confers no
> rights. *
DavidGrampa
---
Posted via http://www.mcse.ms
---
View this thread: http://www.mcse.ms/message237589.html

Multiple Servers in ODBC Client Setup

OK, something weird is happening.
I have a standard Windows XP client and I am trying to set up a simple ODBC
entry. So I go to Control Panel/Administrative Tools/ODBC/System Tab. From
there I create a new ODBC entry connecting to a SQL Server. I enter in the
name of my ODBC and a descripton. When I hit the drop-down button to select
a server I see my 2 SQL Server machines (local machine also named "Jim" and
sbserver) but they are listed twice or even 3 times (see below) and the local
machine has even more entries. What gives and how do I clean this up? Both
seem to work when I "test" at the last step but I have a local application
using this ODBC and it is failing to run so I think it is having "issues"
with these multiple entries.
Thanks!
-Richard
e.g.
(local)
(local)
Jim
Jim
jim
sbserver
sbserver
Make sure your MDAC installation isn't flaky - you can use
component checker to verity the MDAC version and
installation. You can download the tool from:
http://msdn2.microsoft.com/en-us/data/aa937730.aspx
How many instances do you have on each of those servers?
Do you get the same list if you execute the following from
the command prompt:
osql -L
-Sue
On Fri, 16 Mar 2007 04:47:05 -0700, Richard K
<RichardK@.discussions.microsoft.com> wrote:

>OK, something weird is happening.
>I have a standard Windows XP client and I am trying to set up a simple ODBC
>entry. So I go to Control Panel/Administrative Tools/ODBC/System Tab. From
>there I create a new ODBC entry connecting to a SQL Server. I enter in the
>name of my ODBC and a descripton. When I hit the drop-down button to select
>a server I see my 2 SQL Server machines (local machine also named "Jim" and
>sbserver) but they are listed twice or even 3 times (see below) and the local
>machine has even more entries. What gives and how do I clean this up? Both
>seem to work when I "test" at the last step but I have a local application
>using this ODBC and it is failing to run so I think it is having "issues"
>with these multiple entries.
>Thanks!
>-Richard
>e.g.
>(local)
>(local)
>Jim
>Jim
>jim
>sbserver
>sbserver