 |
Well, what about some fresh/new db under Windows Server 2019? Is it working there? |
 |
New DB is working there. Currently, I am checking one of the backups which cannot be opened under Windows Server 2019. On Win 10, same DB is opened without problems and diagnose shows no error. I am using VStudio 10.4.1 on both machines. I can send you that database if you give me mail address. |
|
|
ivan_smahin at paradigmasoft.com |
|
|
DB sent. Just checked one more time on Win Server. If I delete index file and then try to open DB, it creates .ind with only 68KB every time and then shows error. |
|
|
1. Well, db is diagnosed ok first time, but second time - there are few index problems found. We will check what's wrong there. 2. Do you mean "local db mode" for both 2016 and 2019 Windows Server or the db is under vServer? If it was "remote db" - please specify - is there the same vServer instance for both cases or not. BTW, if we are talking of vServer - it does not matter (almost ) which vStudio version is, in this case vServer versions are much more important. 3. I'm not sure that your issues are result of 2019/2016 Windows Server differences (BTW, following some sources - late 2016 is the same as 2019). So, please check your hardware. You are the first who reported such things like zeroed INI file, unable to open db on the particular OS, etc... |
|
|
I understand that about Windows Server 2019 being almost same as 2016, but we are not using both Windows Server 2016 and Windows Server 2019 here. What I am comparing is different behavior on Windows 10 and Windows Server 2019. I am currently using these versions on both Windows 10 and Windows Server 2019: vServer: 10.1.2 vStudio: 10.4.1 Problems are happening in both modes ( local and remote ). In local mode, on Windows Server 2019, database cannot be opened, and same database is opened using same vStudio version on Win 10. In remote mode, db cannot be diagnosed on Windows Server 2019, but same database on Windows 10 in remote mode can be diagnosed. For testing this, I used 3 separate Windows Server 2019 machines. Zeroed INI file happened on multiple machines, with Win 10, Win Server 2012 and Win Server 2019, |
|
|
>> For testing this, I used 3 separate Windows Server 2019 machines. Does it mean there is the same issues on all that machines? All that machines have own disk storages, etc.. - no shared components like same disk drive? |
|
|
Let's call these 3 machines PAM1, PAM2 and PAM3 PAM1 and PAM2 have shared storage. On them we have Windows Failover Cluster, and using disk from other storage which is connected as iSCSI target. DB is on that disk, connected through 20Gbps network. On PAM3, DB is on system SSD, in original location (C:\Program Files\Paradigma Software\VServer x64\databases). PAM1 and PAM2 have multiple networks, They have 20Gbps and 10Gbps networks where is 20Gbps teaming between 2 cards. PAM3 have 20Gbps which is teaming between 2 10Gbps cards. These machines does not have internet connection. |
|
|
Could you send me vServer's log (verboosemode == 3) after all that operations like db.Open, Diagnose, Reindex..? |
|
|
And one more thing - could you describe me how do you insert/update asset.path_unique field? SQL only? how that statements looks like? Send me please all that statements "as is". |
|
|
Files are sent via WeTransfer on your mail. Actually, Reindex is done successfully, but diagnose failed twice. path_unique is updated as every other field, and it is used to prevent duplicates. Insert/update of this field is done only using Api in XOJO, like tabelaAsset.StringField("path_unique").value = path |
|
|
Sorry, could you send it once more - it was no email - probably goes to the Junk folder. |
|
|
No problem, I sent it again. |
- Anonymous
