I contacted customer support, and sent the project files in question to their ftp-server. But so on one of these, I also get the same error as the other person here. WHEN it works (the program become sunstable very quickly). Running a query on such a set of about 100MB takes between 10 and 24 hours (on an Intel Core I7 machine with 6 gigs of RAM). But so I therefore broke the big file (500MB) down into 3 smaller ones (also no mean task in the absence of a 'Save as' command). I can think of very few less helpful answers (and of a lot more helpful ones). Needless to say - this does not help at all. But maybe somebody else here on the forum could help me? What is the deal with 'resetting sql files', for instance? Also most postings about this in this forum refer people to support instead of at least offering some possible troubleshooting tips. I have already missed a deadline and am not even close to a resolution of this issue. End of inner exception stack trace -Īt k7.a(String A_0, String A_1, Exception A_2)Īt k7.a(String A_0, Boolean A_1, Boolean A_2, Boolean A_3, ApplicationConnection A_4, String A_5, SimulateServerProjectParams A_6, Boolean A_7)Īt .(CreateOpenProjectParameters A_0, Boolean A_1, Boolean A_2, ApplicationConnection A_3)Īt .(String A_0, Boolean A_1, Boolean A_2, Boolean A_3, Boolean A_4, ApplicationConnection A_5)Īt .(String A_0, Boolean A_1, Boolean A_2, ApplicationConnection A_3, Boolean A_4)Īt .()Īt .(Object A_0, RunWorkerCompletedEventArgs A_1)Īt (RunWorkerCompletedEventArgs e)Īt (Object arg) It may be from a different database or the log may have been rebuilt previously.Īt .OnError(SqlException exception, Boolean breakConnection)Īt .OnError(SqlException exception, Boolean breakConnection)Īt .ThrowExceptionAndWarning(TdsParserStateObject stateObj)Īt .Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)Īt .RunExecuteNonQueryTds(String methodName, Boolean async)Īt .InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe)Īt .ExecuteNonQuery()Īt es.a(SqlConnection A_0, DatabaseIdentifier A_1, b0 A_2, Boolean A_3) Log file 'C:\Users\Eigenaar\Downloads\FoC_all+scenarios_Eng-Rus Nvivo9_log.LDF' does not match the primary file. If this is an existing database, the file may be corrupted and should be restored from a backup.Ĭould not open new database 'NVivo10'. If you are attempting to attach a database, retry the operation with the correct files. > : One or more files do not match the primary file of the database. But the other two ones won't even open anymore.įullText = gg: Failed to attach to database. One of those file that had taken about 10 hours now got processed in a bit over a minute. I have now broken the larger file up in 3 smaller files, have used a different computer (also i7 but desktop and with more cache, 12gigs of RAM and on an SSD drive).
#Nvivo 10 for windows 8 server failure keygen
![nvivo 10 for windows 8 server failure nvivo 10 for windows 8 server failure](https://s1.manualzz.com/store/data/004145409_1-cc97424418938a6d71f35ee9c4d1fa0c.png)
There isn't much that can be done unfortunately to make the query run any quicker. I am assuming that you have selected 700 nodes and 300 source documents in your query criteria. RE: Generating coding matrix excruciatingly slow CRM:01210001443ĭepending upon the scope and criteria selected, large queries can take hours. A request to support gave the following cheery answer:
![nvivo 10 for windows 8 server failure nvivo 10 for windows 8 server failure](https://img.yumpu.com/11755000/1/500x640/nvivo-10-getting-started-guide-qsr-international.jpg)
Nvivo can not run large queries (coding matrix) on this (keeps crashing/stopping about half way through - after about 12 hours). Maybe for coding (small) surveys, it's fine but we have a large dataset with about 300 internals (pdf files - some of a few MB), that have been coded to contain hundreds of tree nodes (some with up to 4 layers). And it has become clear to me that despite its price, Nvivo is not equipped to deal with larger datasets - something that is never advertized.
![nvivo 10 for windows 8 server failure nvivo 10 for windows 8 server failure](https://www.alfasoft.com/images/products/nvivo/images/1-NVivo-import.png)
I have encountered loads of problems with Nvivo (both 8 AND 9). algorithms to troubleshoot problems like this). I wish Nvivo would take this forum more seriously and actually answer questions properly here (e.g.