Data conversion issues

[ttttt]

I have just upgraded to SAGE 50 version 2011 17.

When logging in for the first time to a particular account, a data conversion process takes place. At this point Sage closes down or just freezes. When I try again, it will not work as there is a message that there is no data available. I have to restore from backup for the conversion to initiate again but when it does, it will fail again.

It doesn't do it all the time and some accounts convert and then work perfectly well

Any suggestions?

[brucedenney]

Before you upgraded, did you run checkdata and make sure that all was good before you started?

Do you have full access rights to the location where the data is stored?

[ttttt]

Thanks for your quick response.

I have been informed that checkdata is run on all the accounts on a regular basis (FYI I am IT support and not a Sage user)

I have full admin rights.

Some of the failed accounts have converted after a few retries which seems a bit strange?

Around 40 accounts have now converted with just one or two still failing. If we assume that checkdata was not run on the remaining accounts, how do we get them converted?

Thanks again

[brucedenney]

If you are experiencing the same problem on multiple data sets, then I would suspect that the problem lies with the infrastructure.

Are you running conversion on the server?

[ttttt]

No, the conversions are 'running' from the client

[ttttt]

Addidtionally, I have re-installed Sage 50 2008 on another PC in the hope that I can open the problematic accounts and run a data check on them as they were working fine previously in that version. But when I've done this it is not accepting the username or password. All the data resides on a server. Any idea why I can't login now after this re-install of version 2008?

[brucedenney]

Why you can not log to V2008 is a separate problem, you can start a new thread for that if you wish.

I think the problem could be infrastructure, an SMB2 client talking to a SMB1 server or vice versa.

Data upgrade is a major strain on the network, I suggest you try running it on the server, this will eliminate, a lot of potential causes and help narrow down the problem and make it run a lot faster.