across 4.0 SP2 Auteur du fil: Uwe Schwenk (X)
|
|---|
Uwe Schwenk (X)
États-Unis
Local time: 18:19
anglais vers allemand
Just for information SP2 has been released and I am in the process of upgrading. I let you know if there are any issues.
Uwe
| | | | | Upgrading causes Across to crash | Sep 10, 2008 |
I just downloaded SP2, and completed the installation.
After that, I launched Across and it crashed.
It keeps crashing in crossWAN mode (that is, when I try to log in to the client's server).
I can open files in Standalone mode.
This looks like the same problem as this thread is talking about:
http://www.proz.com/post/936731#936731
I have contacted ... See more I just downloaded SP2, and completed the installation.
After that, I launched Across and it crashed.
It keeps crashing in crossWAN mode (that is, when I try to log in to the client's server).
I can open files in Standalone mode.
This looks like the same problem as this thread is talking about:
http://www.proz.com/post/936731#936731
I have contacted Across support, but I am not sure when I will get an answer.
I am not sure if I can "downgrade" to SP1 - does anyone know?
I still have the SP1c zip file... ▲ Collapse
| | | | Uwe Schwenk (X)
États-Unis
Local time: 18:19
anglais vers allemand
AUTEUR DU FIL | Upgrade and Crash | Sep 11, 2008 |
Katalin, Alessandra,
that’s actually a relatively easy issue to diagnose, but difficult to solve. Let me explain in more detail.
What you have encountered here is a version mismatch, meaning the versions you and the client are using are not on the same level or the database of the client is not at the same level.
Now this is not just a across issue. That’s more of a general issue with software per se. It’s like the windows update. Some people set it t... See more Katalin, Alessandra,
that’s actually a relatively easy issue to diagnose, but difficult to solve. Let me explain in more detail.
What you have encountered here is a version mismatch, meaning the versions you and the client are using are not on the same level or the database of the client is not at the same level.
Now this is not just a across issue. That’s more of a general issue with software per se. It’s like the windows update. Some people set it to automatic, some never update.
Can this be eliminated?
Well it can't. You might be able to mitigate to some extent, but this will never be totally eliminated. The way I am doing this is when I receive any requests, I am asking which version the potential client is on and let them know upfront which version I am working with and also why. An example would be the new SP2C with support for .Net (a life-saver for me with the new QC options).
If the client is willing to upgrade or patch his or her system, the issue is solved. If not than it gets tricky.
While you can downgrade, please make absolutely sure to contact across for precise instructions. The key is here the database.
Here is my "creative solution". I do not recommend this unless you are really sure about what you are doing.
As I stated in a response to another issue, my DB is on an external hard drive and that’s why this has worked so far.
When I get a request from a client, I first inquire about the version in use with the Client BEFORE I log on.
Depending on his/her version and the settings, when you log on, it might patch automatically before you even start and you want to avoid this, because otherwise you might have problems with your own databases.
Once I know the version, it is up to me to make the decision of whether I want to take the risk or not.
I am providing a solution in the form of an example:
However, as stated before when you can downgrade, please make absolutely sure to contact across for any help possible. Their support is good.
In this example the following applies:
a) The folder where all databases are located is called Localize.
b) The external hard drive is called K
c) Versions are being referred to as A, B, C, etc.
d) I am referring to me as VENDOR.
e) The client is referred to as CLIENT
Here we go.
Back up the database in TBX first (Recommendation)
1. CLIENT informs me that he is on version A.
2. VENDOR is on Version B.
3. VENDOR decides to accept the assignment, but does not want to compromise own setup.
4. VENDOR creates a copy of LOCALIZE, and renames it according to current VENDOR Version
5. VENDOR removes version B via the install routine in across.
6. After reboot, VENDOR checks the version. With the version matching the client, VENDOR logs on and checks whether his database works.
7. If that part is OK, then the logon to the client’s server is done.
8. The assignment for the CLIENT is completed.
9. (If applicable) The TBX file for the project is being provided to the VENDOR upon completion for future reference.
10. VENDOR Installs Version B again.
11. VENDOR removes the folder with the complete database set up for this particular CLIENT.
12. The Folder renamed in Step 4 is named again as it was before.
13. VENDOR logs on.
14. If step 9 applies, the TBX is imported into VENDORS database with the relevant settings.
Final Notes:
I do not go back any further than 4 patches at my home.
Also, since I am currently also evaluating across for my place of work, I can tell you this I made mandatory for all vendors wanting to do business with us.
1. I absolutely refuse to provide contractors for external logon partial versions, as some Clients do. I recommend the download from the across website.
2. The vendor has to communicate the version he or she is using, so I can evaluate whether it is even compatible with what we use. (Before anyone says something: I know backward compatibility is there, but then there is real life, based on operating system in use and other fun details, such as certain virus protection programs).
3. I mandate what version the vendor is to be using if they log on. If I send packages, it’s a different story.
Especially for point 3 some of you might say "What the ....?" and other not so nice comments.
However, while I am a freelancer, I also have a day job in a corporate group, and the translation database with a number of languages and the amount that is in there are HUGE assets worth a 7 digit figure, and the first number is not a 1. There is a very tight control required and I do not make any excuses for it, because if that goes south, that can have a huge impact on the revenue side, not to mention my job and the jobs of a few others.
Uwe
[Bearbeitet am 2008-09-11 03:06] ▲ Collapse
| | | | | My solution - complete uninstall and start over from scratch | Sep 11, 2008 |
Hi Uwe,
Yes, I figured it was some sort of version mismatch, even though the error message I got did not mention anything that would directly lead to that conclusion...
Since I had nothing to lose (I use Across only for this one client, and I had everything uploaded to their server), I could try a few things sort of "risk free".
First, I tried to install SP1 (over the crashing SP2). I thought this might work as it seemed that each service pack was a complete installation anyway... See more Hi Uwe,
Yes, I figured it was some sort of version mismatch, even though the error message I got did not mention anything that would directly lead to that conclusion...
Since I had nothing to lose (I use Across only for this one client, and I had everything uploaded to their server), I could try a few things sort of "risk free".
First, I tried to install SP1 (over the crashing SP2). I thought this might work as it seemed that each service pack was a complete installation anyway. The installation went smooth, I got no error messages, no warnings, nothing. (*)
After the installation was complete, I tried launching Across, and this time I got the same message as Alexandra, about the database file's version is larger than 329. (At this point I understood what Alexandra's problem was, that the databases were probably automatically converted.)
(*)I found this annoying, by the way. If this can screw up things - as it can - the user deserves at least a warning - your databases are a newer version than the software you are about to install - and a chance to confirm/cancel before proceeding.)
So, since this did not help, I went ahead and completely uninstalled Across.
Then, I installed the original 4.0 PE, then SP1. This was the last working version, so using this, I tried logging in to the client. This time it was OK, I saw all the familiar dialog boxes and messages. Now, for the past several weeks, every time I logged unto the client site, Across told me there was a patch available, but when I clicked on download, it hung for a while, then gave me an error dialog saying the installation could not complete because the command needed elevation, so I ended up canceling the patch. So today (again, thinking I have nothing to lose) I exited out of Across at this point, I disabled UAC (User Account Control) on my Vista machine, logged back to Across, and this time I could download and install the patch.
Guess what version I have now, after the patch?
SP2d3_EN.
That's what the client had, apparently.
And what is the version Across has on their website?
SP2c_EN
I don't understand why they don't make the latest patch available on their website, if it is already installed at Across servers at their corporate clients?
How is it possible, that I had no problem logging in and downloading/uploading stuff when I had SP1c and the client had SP2d3, but I encountered all these problems when I upgraded to SP2c.
So, SP1c + SPd3 = OK, but SP2c + SPd3 = crash - does not seem logical to me...
I guess I was lucky, as I did not have anything stored locally.
By the way, could anyone explain how to separate client databases, if I would ever work with the standalone version? - I don't even know where those files are, what kind of files they are?
[Edited at 2008-09-11 04:12] ▲ Collapse
| | |
|
|
|
Selcuk Akyuz 
Turquie
Local time: 02:19
anglais vers turc
+ ...
| File locations | Sep 11, 2008 |
Katalin Horvath McClure wrote:
By the way, could anyone explain how to separate client databases, if I would ever work with the standalone version? - I don't even know where those files are, what kind of files they are?
This is really a problem for me as well. My primary CAT is Deja Vu, but I also use Trados, Transit and SDLX. In all these CAT tools I know where my files are located, and I can open and edit them with other programs as well. For instance Deja Vu files can be opened with Access. But in Across, one needs to be familiar with SQL commands.
| | | | | Reply from Across Support | Sep 11, 2008 |
The contacted me this morning and sent an internal hotfix, SP2d4
It came with all the disclaimers that they do not guarantee stability and do not take any responsibility, etc.
Since my client has SP2d3, I am not going to install this until they tell me it is compatible - which I just asked in my reply email.
| | | | Uwe Schwenk (X)
États-Unis
Local time: 18:19
anglais vers allemand
AUTEUR DU FIL | Separating Client Databases | Sep 13, 2008 |
Katalin, Selcuk,
separating databases is not a good option for any translation memory, whether its across or any other tool, because you are actually losing the potential matches. The more quality entries you have in your database, the better.
When you switch to the CrossTank manager and select export, you have the following filter options:
server context (for crossGrid)
date
subject
relation
created by
modified by
status... See more Katalin, Selcuk,
separating databases is not a good option for any translation memory, whether its across or any other tool, because you are actually losing the potential matches. The more quality entries you have in your database, the better.
When you switch to the CrossTank manager and select export, you have the following filter options:
server context (for crossGrid)
date
subject
relation
created by
modified by
status
project
This way you can tie it nicely to one or more of these filter criteria.
What you can do instead of creating client databases (which actually defeats the purpose of a TM (IMHO) is to use the filter when exporting the TMX file. Additionally, you have the option to export as TBX or as TMX to integrate into other CAT tools.
When I have completed a project, I export everything for this particular project, store it together with the checked out files and thats it.
However, before you start exporting by client or project, I am recommending one master backup, menaing all.
Uwe
[Bearbeitet am 2008-09-13 00:54] ▲ Collapse
| | | | | Thanks Uwe, but the question was slightly different | Sep 13, 2008 |
Thanks Uwe for the explanation.
I already know how to export using filters.
That was not my question.
There are several reasons why I want to keep client TMs separate:
- I am used to it with other tools and it works well for me
- the materials I am working an differ from one client to the other, sometimes greatly, so there is no point in keeping them together (medical device IFU texts have very little in common with let's say gas turbines manuals and those have agai... See more Thanks Uwe for the explanation.
I already know how to export using filters.
That was not my question.
There are several reasons why I want to keep client TMs separate:
- I am used to it with other tools and it works well for me
- the materials I am working an differ from one client to the other, sometimes greatly, so there is no point in keeping them together (medical device IFU texts have very little in common with let's say gas turbines manuals and those have again nothing to do with computer hardware/software marketing texts)
- an "all-in-one" TM can be very large with performance problems, and it is more vulnerable, I mean if it gets corrupted, potentially everything gets corrupted - I like to limit the ripple effect of problems as much as I can
- etc.
Anyway, I must tell that I am a beginner user of Across, I started using it only recently with this current client of mine and they require me to work with the crossWAN system. Regarding the incompatibility problem I mentioned earlier in this thread I felt I got lucky, as all my translations were uploaded to the client's server.
The problem is, if I had local databases, they probably would have been deleted during the uninstall I had to do.
That's why I asked where the TM files were located - I mean psychically, on my computer's harddisk, which directory has them so I could make a safety backup copy of them somewhere else?
If I work in standalone mode, can I specify a directory for the new TM when "checking in" the source files, or before?
If I want to use an existing TM, can I specify which one, when I "check in" the source files?
Or is there no such option and Across would throw everything in a single big file (I understand that the tags mark the project, etc. but would the data physically located in the same SQL database)? ▲ Collapse
| | |
|
|
|
Uwe Schwenk (X)
États-Unis
Local time: 18:19
anglais vers allemand
AUTEUR DU FIL | Client databases | Sep 17, 2008 |
Katalin Horvath McClure wrote:
Thanks Uwe for the explanation.
I already know how to export using filters.
That was not my question.
There are several reasons why I want to keep client TMs separate:
- I am used to it with other tools and it works well for me
- the materials I am working an differ from one client to the other, sometimes greatly, so there is no point in keeping them together (medical device IFU texts have very little in common with let's say gas turbines manuals and those have again nothing to do with computer hardware/software marketing texts)
- an "all-in-one" TM can be very large with performance problems, and it is more vulnerable, I mean if it gets corrupted, potentially everything gets corrupted - I like to limit the ripple effect of problems as much as I can
- etc.
Anyway, I must tell that I am a beginner user of Across, I started using it only recently with this current client of mine and they require me to work with the crossWAN system. Regarding the incompatibility problem I mentioned earlier in this thread I felt I got lucky, as all my translations were uploaded to the client's server.
The problem is, if I had local databases, they probably would have been deleted during the uninstall I had to do.
That's why I asked where the TM files were located - I mean psychically, on my computer's harddisk, which directory has them so I could make a safety backup copy of them somewhere else?
If I work in standalone mode, can I specify a directory for the new TM when "checking in" the source files, or before?
If I want to use an existing TM, can I specify which one, when I "check in" the source files?
Or is there no such option and Across would throw everything in a single big file (I understand that the tags mark the project, etc. but would the data physically located in the same SQL database)?
Katalin,
I guess I had misunderstood the question. Call it an early senior moment. Let me ask you a question: I am assuming that you have the freelance version and you are using SQL Express that comes with it. Is this correct?
| | | | | Freelance 4.0 and SQL Express | Sep 17, 2008 |
I am assuming that you have the freelance version and you are using SQL Express that comes with it. Is this correct?
Yes.
| | | | Uwe Schwenk (X)
États-Unis
Local time: 18:19
anglais vers allemand
AUTEUR DU FIL | Freeelance and SQL Express | Sep 28, 2008 |
Katalin,
first of all sorry for the late reply, but we had some serious flooding and clena up took some time.
In regards to the file locations for the databases the thread http://www.proz.com/forum/across_support/110560-file_locations.html explains the locations of the database files.
In regards to your concern with deleting databa... See more Katalin,
first of all sorry for the late reply, but we had some serious flooding and clena up took some time.
In regards to the file locations for the databases the thread http://www.proz.com/forum/across_support/110560-file_locations.html explains the locations of the database files.
In regards to your concern with deleting databases during uninstall: As I suggested in another thread, it is (in my opinion) a great idea to have the databases on a separate hard drive (I am using an external one) and not in the default installation directory, so it will not be a problem when uninstalling.
As for separate databases, I see your point of having separate databases but the only option at this time for across would be to export every project into TMX upon completion (I would recommend this anyhow for backup purposes).
Personally, I am not really nervous about having everything in one database, because of the tagging capabilities through subject, relation, etc.
I am having a variety of subjects in mine, such as aerospace, martial arts, software hardware, and a number of others. So far, I did not encounter any issues.
Finally, going back to the original subject of the thread of the version mismatch, here is a little tip in case the Client has a newer version of the server installed.
When the client has a newer version installed than the translators he she works with, when creating the CRU file, there is a drop down box, which allows the client to create the package accroding to the version in use with the translator. However, the client has to know which version the translator is using.
Uwe ▲ Collapse
| | | | Uwe Schwenk (X)
États-Unis
Local time: 18:19
anglais vers allemand
AUTEUR DU FIL | across 4.0 SP2 | Oct 3, 2008 |
Getting back to the original topic, I have finsihed all testing and have now switched over completely to across. All other tools are phased out.
Uwe
| | |
|
|
|
business idiom
États-Unis
Local time: 18:19
italien vers anglais
+ ...
| Freeware not "free" - a lot of time wasted, anxiety created | Nov 18, 2008 |
I was interested in the freelance edition until reading this thread.
There is definitely a difference between freeware and FOSS. On other threads, I read about Across causing freelancers' computers to crash, etc.
At this time, I do not want to spend my time being a beta-tester for proprietary software. Not unpaid, at least. If ever I install it, I'll be sure to keep the database separate if I can. Thank you so much for the posts here.
I will stick to s... See more I was interested in the freelance edition until reading this thread.
There is definitely a difference between freeware and FOSS. On other threads, I read about Across causing freelancers' computers to crash, etc.
At this time, I do not want to spend my time being a beta-tester for proprietary software. Not unpaid, at least. If ever I install it, I'll be sure to keep the database separate if I can. Thank you so much for the posts here.
I will stick to simpler TEnTs and CATs for now. ▲ Collapse
| | | | To report site rules violations or get help, contact a site moderator: You can also contact site staff by submitting a support request » across 4.0 SP2 | LinguaCore | AI Translation at Your Fingertips
The underlying LLM technology of LinguaCore offers AI translations of unprecedented quality. Quick and simple. Add a human linguistic review at the end for expert-level quality at a fraction of the cost and time.
More info » |
| | CafeTran Espresso | You've never met a CAT tool this clever!
Translate faster & easier, using a sophisticated CAT tool built by a translator / developer.
Accept jobs from clients who use Trados, MemoQ, Wordfast & major CAT tools.
Download and start using CafeTran Espresso -- for free
Buy now! » |
|
| | | | X Sign in to your ProZ.com account... | | | | | |
Login to reply/comment 
