Unity 3.2 Pro + Asset Server, commiting fails

Unity Engine
1

Hi community :),

after upgrading to 3.2 I have severe problems with commiting changes to the Asset Server.

If I try to commit bigger changes to the project Unity gives me the following error:

Timed out awaiting result from Asset Server server
Got an SQL error while preparing to upload ()

editor-log entry:

Unloading 318 unused Assets to reduce memory usage. Loaded Objects now: 6349.
System memory in use: 0.64 GB.
Unloading 39 Unused Serialized files (Serialized files now loaded: 2 / Dirty serialized files: 2)
Updating library/qualitysettings.asset - GUID: 00000000000000009000000000000000...
 done: hash - a05668d90f8b7fe26f14873d3ee3c57a
Updating assets/standard assets/water (pro only)/water3/sources/materials/water3.mat - GUID: 9d1900bd13d814f0daf797e37e36f636...
 done: hash - 69d8c55b10d7023284fadb1bc7a0e025
Updating assets/standard assets/water (pro only)/water3/sources/meshes/watermesh.fbx - GUID: 745f3a24dcf0a4496b0e8d3ea5d93737...
 done: hash - f972261e4eb7f5f34f76a9ae332a7c87
Timed out awaiting result from Asset Server server
 
(Filename: C:/BuildAgent/work/f724c1acfee760b6/Editor/Src/AssetServer/Backend/ASBackend.cpp Line: 199)

Got an SQL error while preparing to upload ()
 
(Filename: C:/BuildAgent/work/f724c1acfee760b6/Editor/Src/AssetServer/Backend/ASBackend.cpp Line: 755)

In Unity 3.1 it all worked perfect.

Things I’ve done so far to resolve the problem:

  • restarted the Asset Server
  • restarted the Windows 2003 server, where the Asset Server is hosted
  • restarted the Windows 7 computer, where Unity 3.2 runs on
  • created a new project on the Asset Server and tried to commit
  • competely deleted and reinstalled unity 3.2
  • reimported all assets of the project

The Asset server is hosted on a Windows 2003 Server with the latest updates.
Unity 3.2 runs on a Windows 7 64 Bit computer, with the latest updates.

Any help is greatly appreciated.

2
  • How much time passes until you get the timeout?
  • Does it still work with Unity 3.1? Just so we know the server is not at fault.
  • To help us try and reproduce the issue could you sent in a bug report with a full editor.log (it automatically attaches) + the server logs? The server logs are at C:\Program Files\Unity\AssetServer\logs by default. Email me the case number.
  • How does the project “look”, does it have a huge amount of little files?
  • Can you work around this by splitting your commit into smaller pieces?
3

Thanks for the reply.

  • Unity works 10 to 20 Minutes with high hard-disk activity. In this time span Unity is frozen up.Then the timeout occurs,
  • In 3.1 it all worked perfectly.
  • E-mail sent. The bug report contains the editor log, but not the asset-server log. I completely deinstalled and reinstalled Unity, so the server-log in question is gone. I actually didn’t know it existed at all. Sry for that.
  • The project is made up mostly, of a huge amount of single fbx-files and their materials and textures. And a good amount of mp3 sound files. So yes, it has a huge amount of little files.
  • The division into many small pieces works. As long as the amount of data transfered is reasonably low it works good.
4

Any solution found yet? I have the same problem now…

5

Having the same issue here. Uploading a single terrain file. Any word on a fix would be useful.

6

I have the same Problem, looks like the server can’t handle large amount of little files, I am trying to commit around 50 little textures , 50 materials and 25 fbx models.

I even tried committing in smaller bunches, still the same problem, I am using unity 3.4.

7

The same error on a mac with asset server on windows 2003.
Project is 1,7GB.
Committing assets from any sizes fails with:

8

A memory issue with committing large amount of assets has been fixed, but that didn’t make it into the last release (will be in the next). There was an easy work around for that problem since it could be split up into smaller chunks and then it worked (the amount of assets you could commit would be proportional to the free memory on the system). However, some of you mention problems committing even single assets which does sound like it could be a different problem, when reproducing the memory problem there were no issues committing a small number of small assets, only hundreds of large assets which would eat up hundreds MB of memory. Could you file bug reports after this problem occurs so we can get the logs and OS/system details + add a description of the project/assets (upload project with the report if possible)? Put “Asset server” in the report title or just email me the tracker numbers.

9

I was using the asset server for a very lot smaller project.

I like to Commit a amazing amount of 417 KB to the asset server…

What i got was again:

Over all the project is around 9,2 MB in size.

That is very annoying , it makes the use of the asset server nearly impossible.

Downloading data form the asset server is not a problem at all.

Other users in the same network(unity 3.4 Windows )can commit to the server (win2003 server) without any problem.

I’m using a new mac mini. 8 GB ram.

Edit:

Next day , next try I got

and the next try its the old error.

10

Any body found a solution to this?

I just had the same exact problem, I was committing some files and I lost the net connection and when I tried to commit again got this error:

Using all the latest version of Unity Pro and Asset server.

11

Nope not solution so far, the support doesn’t know much more the we it seems.

12

My solution was to simply restart the server

13

Getting the same error here while trying to commit a tiny terrain file. Just got the newest asset server today and its happened on first commit after dl’ing the project with no trouble. Admin had no trouble uploading the project either. I have the latest everything.

14

Like Hesham already mentioned it above: Simply restart the Asset-Server and all should be fine. It happens always when i cancel a commit… and i always forget that and then its to late :sunglasses: