Hi there, 

 

We're having some issues while importing exported data.kit files. (System -> Export/Import)

Case: 

We want to move ~200 or so nodes (each accounting for about 2,5MB worth of data).

The data.kit export from the original server seems to work flawlessly, however when I try to import the data kit file on the new server, it halts in the middle of the the "Installing content" phase (after the file upload phase), the w3wp process heap grows (from around 500MB to around 1000MB) and eventually the application pool is automatically restarted.

If we observe the Temp folder while importing, we can see that all the temporary files and folders are changing (folders being made, files being moved) up until the server halts for some reason.

There is always a file lock on some random image file in the root of the Temp folder after a failed import, and one has to manually nuke the w3wp process holding the lock in order to delete the file. This might ofcourse be just the w3wp process being in the middle of the import while something else crashes, but I find it curious that it's always a lock on an image file.

I've tried granulating the nodes into smaller kit files (with as few as 5 nodes in each kit file). This seems to be working better, but for each file that succeeds, the nex one fails in the same way as described above (seemingly at random). 

Measures I've taken so far:

 

- Cleaning WAF/Files/Temp folder + WAF/Files/Upload folder between each kit upload

- Restarting app pool and restarted site

- Deleting (and clearing from wastebin) all imported nodes after each unsuccessfull import attempt

- Cleaning the settings folder  and re-enabling licence afterwards (incase we're encountering the inconsistent settings files bug)

I've also tried importing into a local development version, where the import actually succeeds (with larger kit files, around 50 nodes each). 

All webnodes instances (origin, new and development) are on b1539.

 

Did anyone here encounter a similar issue regarding import/export; and what did you do to resolve/get around it?

 

 

 

 

 

After some several hours of trying to debug the live instance, I resorted to copying the entire working directory of the webnodes installation from the virtual server(vmware) to a physical PC (my own development PC).

No alterations was done to any of the www root files.

Fired up the instance locally in IIS7, ran the import, no errors at all. 

 

I'm wondering if we're experiencing some kind of race condition /deadlock issue during file access, as I saw one or more files and folders being locked when the W3WP process was stale (only happened at the virtual server). Might be some vmware time synchronization issue. 

I wish to know exactly why we experienced all the forementioned issues (because I might want to do additional imports in the live environment in the future), so i'll keep this thread posted with my findings.