Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 432
  • Last Modified:

Programs stopping on Server 2008

Just installed one of my technet licenses of Server 2008 to test for a doctor's office I support.  

I've installed the practice management software that he uses, but on every boot...it gives an error that the program has stopped and that Windows can look online for a solution.

I think I have disabled UAC everywhere that I can and DEP as well. This is my first time to set one up....not sure where to go from here.

Windows Server 2008 Standard. No domain or AD.

Dell PowerEdge 2900 with RAID 5 on a PERC 6/i.
0
meubanks
Asked:
meubanks
  • 4
  • 3
1 Solution
 
DavidCommented:
What does the event manager reveal?
0
 
meubanksAuthor Commented:
The software is Eaglesoft by Patterson....a dental practice management software.

Running 64 bit Server 2008 but the hardware specs list it as compatible.



+ System

  - Provider

   [ Name]  EagleSoft
 
  - EventID 0

   [ Qualifiers]  0
 
   Level 2
 
   Task 0
 
   Keywords 0x80000000000000
 
  - TimeCreated

   [ SystemTime]  2012-04-08T05:48:27.000Z
 
   EventRecordID 11
 
   Channel EagleSoft
 
   Computer SERVER
 
   Security
 

- EventData

   Service Exception thrown ... Code: GeneralError Message: Exception Details: Time out has expired and the operation has not been completed. Stack Trace: at System.Environment.GetStackTrace(Exception e, Boolean needFileInfo) at System.Environment.get_StackTrace() at Patterson.Services.ServiceUtils.ServiceException.LogError() at Patterson.Services.ServiceUtils.ServiceException..ctor(ServiceExceptionCode fc, String msg, String dt) at Patterson.Services.PattersonAppServer.AppService.ServiceStartup(Object state) at System.Threading._ThreadPoolWaitCallback.WaitCallback_Context(Object state) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Threading._ThreadPoolWaitCallback.PerformWaitCallbackInternal(_ThreadPoolWaitCallback tpWaitCallBack) at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback(Object state)
0
 
DavidCommented:
The record was generated by THEIR software, not the O/S.  MSFT has no idea what it means.
 You are going to have to ask Eaglesoft why they bothered to write code to report the problem and then let the application abort because of it.  They have to tell you what is wrong and what you need to do about it.
0
Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

 
meubanksAuthor Commented:
Just tried to run it manually and this is what it reported...not in the event viewer but the error message:

Description:
  Stopped working

Problem signature:
  Problem Event Name:      CLR20r3
  Problem Signature 01:      patter~2.exe
  Problem Signature 02:      16.0.21.0
  Problem Signature 03:      4dfa2486
  Problem Signature 04:      PattersonServerStatus
  Problem Signature 05:      16.0.21.0
  Problem Signature 06:      4dfa2486
  Problem Signature 07:      15
  Problem Signature 08:      61
  Problem Signature 09:      System.TypeInitialization
  OS Version:      6.0.6002.2.2.0.272.7
  Locale ID:      1033

Read our privacy statement:
  http://go.microsoft.com/fwlink/?linkid=50163&clcid=0x0409
0
 
DavidCommented:
It is absolutely a vendor-specific message.  You have to contact the vendor.  I did find below by googlin' for PattersonServerStatus that may help but there are a few web hits that also might help.  If you are under their support, just call them. This isn't anything  that you can expect people to know the answer to other then the programmers who wrote the software.
0
 
meubanksAuthor Commented:
Sorry for the confusion - I certainly do not expect to find third party answers here. Being unfamiliar with 2008 and UAC I thought maybe that was the culprit....that's why I posted the other error.

It also happened on another app that I installed....it's a monitor for USB 3.0 connectivity.  Again - just had me wondering if it was related to UAC or 64 bit OS.

Thanks for the help.
0
 
DavidCommented:
No prob .. It is unlikely it is specifically related to either of those things for the simple reason that this condition was trapped by their software.  So if it was an unexpected UAC or 64-bit issue, then more likely the program would have crashed and given a MSFT error.  Since their program was able to trap this specific problem, then it stands to reason they know exactly what to do about it.

(Too bad the developers went to all that trouble to test for something and report the problem, but got lazy and didn't report what needs to be done about it).
0

Featured Post

Hire Technology Freelancers with Gigs

Work with freelancers specializing in everything from database administration to programming, who have proven themselves as experts in their field. Hire the best, collaborate easily, pay securely, and get projects done right.

  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now