Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsFormsForms ProgrammingQueriesModules / DAO / VBAReports / PrintingMacrosDatabase DesignSecurityConversionImporting / LinkingSQL Server / ADPMultiuser / NetworkingReplicationSetup / ConfigurationDeveloper ToolkitsActiveX ControlsNew UsersGeneral 1General 2
Access DirectoryToolsTutorialsUser Groups
Related Topics
SQL ServerOther DB ProductsMS OfficeMore Topics ...

MS Access Forum / Multiuser / Networking / July 2005

Tip: Looking for answers? Try searching our database.

Terminalserver 2003, multiuser appl. Access 2003 hangs up

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Ing Chris - 12 Jul 2005 18:04 GMT
Hello,

I´m new here; congratulation to accessmonster.com --> the postings/answers
here are very interesting and I got already some helping information...

My problem:
I try to use a multiuser application in Access 2003, SP1 (Office 2003, SP1)
running on a terminalserver 2003, SP1 (German Version!).
Sometimes after starting the connection to the TS and starting the Access-DB
I have the problem that access hangs up (Event Id: 1000, Source: MS Office 11,
faulting application: msaccess.exe, version: 11.0.6355.0, stamp: 40aa97a8,
faulting module: ntdll.dll, version 5.2.3790.1830, stamp 4243729a, debug?0,
fault address 0x0002fa21), sometimes the faulting module is mso.dll.

- Access - application is one .Mdb-File in a shared folder on the TS, NO
FE+BE!
- First I installed Access 2000 (Office2000) on the TS, now I work with
Access 2003,SP1 (Office2003,SP1)
- I cant say exactly , but I think the problem could be since installing
Windows server 2003, SP1 ?!
-The error occurs also with a very simple, new DB (one TB, one Form, one
report)!)

I read all the postings here about terminalserver/Access and I read hours on
microsoft- and some other homepages/newsgroups, but I didn´t find any helpful
answers...

My questions:
1) In some posting here I read that is recommended to split the DB into BE
and FE on a Terminalserver? Is this really necessary/useful ?

2) Is there anybody who had the same problem and can help?

Thank you and Best regards
Chris
Van T. Dinh - 13 Jul 2005 01:45 GMT
You should (mnearly must, actually) always split a multi-user Access
database application to Front-End and Back-End regardless of running it in
normal mode or Terminal Server mode.

See Tony Toews' Web site:

http://www.granite.ab.ca/access/terminalserver.htm

and

http://www.granite.ab.ca/access/autofe.htm

Signature

HTH
Van T. Dinh
MVP (Access)

> Hello,
>
[quoted text clipped - 37 lines]
> Thank you and Best regards
> Chris
Tony Toews - 19 Jul 2005 05:09 GMT
>I try to use a multiuser application in Access 2003, SP1 (Office 2003, SP1)
>running on a terminalserver 2003, SP1 (German Version!).
[quoted text clipped - 3 lines]
>faulting module: ntdll.dll, version 5.2.3790.1830, stamp 4243729a, debug?0,
>fault address 0x0002fa21), sometimes the faulting module is mso.dll.

<snip>

>My questions:
>1) In some posting here I read that is recommended to split the DB into BE
>and FE on a Terminalserver? Is this really necessary/useful ?

I doubt this will help.  Something sounds a bit flaky somewhere on the
TS system.   I'd also suggest phoning MS Support.  

>2) Is there anybody who had the same problem and can help?

I'd suggest searching at groups.google.com using the advanced search
limiting yourself to newsgroups with *access* in the name.  Then put
keywords such as event ID stamp msaccess.exe faulting module.   But I
don't know if you will get many answers.  Just some questions.

Tony
Signature

Tony Toews, Microsoft Access MVP
  Please respond only in the newsgroups so that others can
read the entire thread of messages.
  Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.