stack trace error when opening sage desktop

Hello. Initially, I could not login to CRE using the "ts.exe" executable (as in the login box for user name & password would not appear). I kept getting a message that said "you do not have access to the application data directory or it may have been virtualized by windows vista." This started appearing after I set up a crystal report for IV in the reports menu for job-cost. Thinking this was the cause, I logged in on our 2008 R2 server as admin & logged into timberline from there under my TS user name with no issue. I then deleted this report from the job-cost reports menu. I logged out from the server, and then logged back in under my user account, but still received the error message when trying to start timberline. I then decided to create a new user account for myself on the server, and disable the old user account. This solved the login issue described above when using the new user account, but when I now enter my login credentials for sage desktop, I receive a stack trace error  which says "target ID: integration with code - 2147221403 has message: invalid dvtarget device structure (exception from hresult 0x80040065)". When logged in as admin on the server, or some other user, I can start sage desktop without issue. Any help would be greatly appreciated. Thanks.

  • 0
    With Desktop issues, I would recommend a reinstall. You can try a simple uninstall/reinstall (remember to install patches as well), but you may have to do a "full" uninstall, including: uninstalling the Desktop client, including all other Sage-related installs (i.e. Pervasive), renaming or deleting the install folders, renaming the related registry keys (BACKUP REGISTRY AND BE CAREFUL WITH THIS), rebooting, and reinstalling.
  • 0 in reply to JDiCo
    Thanks for your answer. One follow-up question - is it safe to run a crystal report for the IV module from the reports menu in job-cost? Does this have the potential to cause any system issues? Thanks.
  • 0 in reply to skmark
    Reporting should never cause an issue with the system. That being said, I am not sure you are going to be able to get an IV- or PO-based report to run out of any accounting module as the embedded CR functionality and ODBC connections are different. When you use accounting data in IV or PO, you need to use special DSNs to pull that data, and there is no such DSN for the reverse.