windows 7 compliance for WS

Historical record of a forum that was for discussion of the setup, configuration, and use of OnePacs for research and educational purposes (non-clinical use).

Please direct any support inquiries through the standard OnePacs ticketing and support system.

The "Announcements" forum will continue to be active and contain announcements related to the OnePacs system.
jeremy
Posts: 140
Joined: Wed Nov 26, 2008 8:34 am

Re: windows 7 compliance for WS

Post by jeremy » Wed Dec 01, 2010 12:13 pm

Hi Hilaro -

Please attempt to gather the logs by following the instructions listed at http://wiki.onepacsforums.com/doku.php? ... debug_logs. If this is not possible, please zip the files located in C:\onepacs\workstation\logs. Send the logs to support@onepacs.com.

A new release (4.5.3.0) of the workstation was released on Nov 28. If this is not the version that you are attempting to install please download this version. It may be beneficial to attempt the following.

-Copy your poller query string if you have a custom query string so that you can paste it into the new install later.
-Uninstall 4.5.3.0 or previous version.
-Delete the c:\onepacs directory
-Reinstall 4.5.3.0
-Reboot

Regards,
Jeremy

tom
Posts: 107
Joined: Tue Jan 13, 2009 12:19 pm

Re: windows 7 compliance for WS

Post by tom » Wed Dec 01, 2010 7:43 pm

Hilario,

Haven't heard of an error like this before. Did you have the study downloader-only installed before? If so, you could try uninstalling onepacs, deleting the c:\onepacs folder, and then reinstalling, in case there were some files that were not updated properly.

Can you send us logs? If you click the "debug" option in the download manager as follows:

http://wiki.onepacsforums.com/doku.php? ... debug_logs

Can you send the logs through the onepacs system to the admin account? (Username admin)

hilario
Posts: 186
Joined: Tue Feb 24, 2009 4:49 pm

Re: windows 7 compliance for WS

Post by hilario » Mon Apr 04, 2011 3:30 am

OK, I sent you some logs via the internal Onepacs mail (to admin user).
Hope this problem won't be so tricky as the one related with Windows XP in Spanish.
Wait for your comments.
Regards

Hilario

hilario
Posts: 186
Joined: Tue Feb 24, 2009 4:49 pm

Re: windows 7 compliance for WS

Post by hilario » Fri Aug 26, 2011 2:01 am

I have send this by mail and also sent OnePacsAdmin a mail with a problem we have.
doing this I found I sent another mail monthes ago and I didn't have any answer.
I suppose there is a problem some part.
I include a copy of the MailScreen in order to debug the stuff.
Regards

I Include also the copy of the today mail. (I include passwords in another mail)
=============================================
Hello boys.
Theres long time I am telling you we have problems with OnePacs Workstation in Spain.
At the end we had to install ONIS on all the Windows 7 systems
But till now I was not able to send you all the details to debug.
NOW is the moment.

I have a brand new WS/dell, with a windows 7 PRO just installed, and a OnePacs Workstation Just Installed.
Every thing LAST VERSIONS.

You can access and check everything you need

Information to do it:
Use Teamviewer:
ID : 870 817 510
Passwd: XXXXX

Windows user: imago
passwd: XXXXXX

Let me know if you can't join the system

I am on skype hilariomartinez.
Regards
===============================================

tom
Posts: 107
Joined: Tue Jan 13, 2009 12:19 pm

Re: windows 7 compliance for WS

Post by tom » Fri Aug 26, 2011 8:31 am

Hilario,

It looks like this issue relates to some naming issues in Spanish language windows 7, as described in this link from microsoft

http://support.microsoft.com/kb/941209

The solutions for now are either to install an English language version of windows 7, if you don't mind, or wait until we update the workstation to work around this windows issue.

Thanks-

Tom

hilario
Posts: 186
Joined: Tue Feb 24, 2009 4:49 pm

Re: windows 7 compliance for WS

Post by hilario » Mon Aug 29, 2011 3:41 am

OK. No way to install english version.
We have to wait. Just for the info we have the same issue on Windows XP:
I think it appears on the two last version of the viewer. Before (for example 4.3.0.1 was OK)
Another option is to install previous release of the workstation (4.2.0.1). What could be the drawbacks of this?
Regards

tom
Posts: 107
Joined: Tue Jan 13, 2009 12:19 pm

Re: windows 7 compliance for WS

Post by tom » Mon Aug 29, 2011 4:37 am

Interesting that this didn't occur with 4.2.0.1, I'll pass that on to the developer. If you want to use it and it works for you, it's ok. That's an ancient release though, I don't recall what features were added since then.

There is a work-around to the windows issue described in the Microsoft link above, if you want to go through all of it. Looks like a bit of a hassle though.

I'll have the developers take another look at this issue.

hilario
Posts: 186
Joined: Tue Feb 24, 2009 4:49 pm

Re: windows 7 compliance for WS

Post by hilario » Mon Aug 29, 2011 8:24 am

was an error before not 4.2.0.1 but 4.3.0.1.
The microsoft workaround... I test it and I wasn't able to solve it.
How can I download 4.3.0.1 from your server?

As I told in another mail I have a WS configured with the problem, and you can access remotely.
Would it be convenient or do I close this WS for the moment?
Regards

hilario
Posts: 186
Joined: Tue Feb 24, 2009 4:49 pm

Re: windows 7 compliance for WS

Post by hilario » Tue Aug 30, 2011 10:20 am

Hello!
Where can I download previous copies of onepacs Workstation?

tom
Posts: 107
Joined: Tue Jan 13, 2009 12:19 pm

Re: windows 7 compliance for WS

Post by tom » Wed Aug 31, 2011 12:47 am

Hilario,

We fixed the problem in a special build for you. You dont need an old version. I emailed you a download link.

The issue is basically a microsoft blunder. Some genius at microsoft decided at some point that a .NET group which previously had been called "Everyone" in all versions of windows should be called "Todos" in Spanish, "Alles" in german, etc. The effect of this is nothing more than to simply break all software that is running on a foreign language platform than the one it was designed for, unless you make a list of translations for "Everyone" in every language the program will be running on.

At any rate, that's microsoft genius for you. We made a build that uses "Todos" as the group name, the download link should work fine. Try it out and let us know.

Tom

Locked