Check out doesn't work

Tilman · Post by **Tilman** » Wed Apr 11, 2007 6:19 am

Hi,

Our check outs have stopped working. I.e. when we do a checkout everything is going fine, according to the Messages tab, but then the GUI doesn't display the file as checked out out, neither in the folder, nor in the Pending Change Set tab. Also, the check in button is disabled. When I look at sgvault.log it also says that the check out was a success

Here is a copy of a relevant section

----11/04/2007 12:50:08 tilman.bregler--tilman.red-gate.com(172.16.1.23)--SSL Disabled VaultFileDownload starting
----11/04/2007 12:50:08 tilman.bregler--tilman.red-gate.com(172.16.1.23)--SSL Disabled Downloading delta for $/Red Gate/Current products/SQL Prompt/v 3.5.0/Testing/UIAutomation/SQLPromptTester.sj from 0 to 1652449
----11/04/2007 12:50:08 david.connell--davidc.red-gate.com(172.16.1.55)--SSL Disabled GetRepositories returned: Success
----11/04/2007 12:50:08 tilman.bregler--tilman.red-gate.com(172.16.1.23)--SSL Disabled GetLatest wrote 0 bytes to the Response Stream
----11/04/2007 12:50:08 tilman.bregler--tilman.red-gate.com(172.16.1.23)--SSL Disabled Ending download process
----11/04/2007 12:50:08 tilman.bregler--tilman.red-gate.com(172.16.1.23)--SSL Disabled EndDownloadProcess returned: Success
----11/04/2007 12:50:08 tilman.bregler--tilman.red-gate.com(172.16.1.23)--SSL Disabled Getting repository Structure-> Rep ID: 3 Base: 178500 Target: -1
----11/04/2007 12:50:08 tilman.bregler--tilman.red-gate.com(172.16.1.23)--SSL Disabled TreeManager: cache matches repository revision and folder security hasn't changed. Returning cached tree, revID 178500
----11/04/2007 12:50:10 tilman.bregler--tilman.red-gate.com(172.16.1.23)--SSL Disabled VaultServiceAPI::GetRepositoryTreeDelta() UserID:45 RepID:3 Base:178500 Target:178500 Calling VaultRepUtil.DiffRepTrees() - in-memory tree diff.
----11/04/2007 12:50:10 tilman.bregler--tilman.red-gate.com(172.16.1.23)--SSL Disabled GetRepositoryStructure returned: Success
----11/04/2007 12:50:10 tilman.bregler--tilman.red-gate.com(172.16.1.23)--SSL Disabled Getting list of checkout changes.
----11/04/2007 12:50:10 tilman.bregler--tilman.red-gate.com(172.16.1.23)--SSL Disabled TreeManager: cache matches repository revision and folder security hasn't changed. Returning cached tree, revID 178500
----11/04/2007 12:50:11 Andrew.Hunter--andrew.red-gate.com(172.16.1.53)--SSL Disabled VaultServiceAPI::GetCheck

We recently upgraded from 3.1.9 to 3.5.1. Also, just before this started happening the database ran out of disk space. After we allocated more space the problem started.

Any help would be much appreciated,

Tilman

Beth · Post by **Beth** » Wed Apr 11, 2007 8:53 am

Are you using Vault integrated with an IDE or just the Vault GUI by itself?

Could you go into your Help - Technical support on a client and copy the information from there for me? That will tell me more about the environment.

Also, there could be more still going on with the database. Could you tell me the sizes of your sgvault.mdf and sgvault_log.ldf files? In the properties pages of the database on your SQL server (looking in the SQL manager), can you tell me what limits are set on those files for size and if they are allowed unrestricted growth or not?

Tilman · Post by **Tilman** » Wed Apr 11, 2007 8:55 am

Hi Beth,

We are just using the GUI on its own.

Here is the information you requested:

Client Information
Vault Client Version: 3.5.1.4786
.Net Framework Version: 1.1.4322.2032
Operating System: Microsoft Windows XP Professional
Service Pack: 2.0
OS Version: 5.1.2600
Total Physical Memory: 2 GB
Time Zone: (GMT) Greenwich Mean Time : Dublin, Edinburgh, Lisbon, London

Server Information
Vault Server Version: 3.5.1.4786
.Net Framework Version: 1.1.4322.2300
Operating System: Microsoft(R) Windows(R) Server 2003, Standard Edition
Service Pack: 1.0
OS Version: 5.2.3790
Timezone: (GMT) Greenwich Mean Time : Dublin, Edinburgh, Lisbon, London
SQL Version: Microsoft SQL Server 2000 - 8.00.2039 (Intel X86)
May 3 2005 23:18:38
Copyright (c) 1988-2003 Microsoft Corporation
Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 2)

License Information
20 serial number(s):
1 of 20: 5 users, permanent
2 of 20: 1 users, permanent
3 of 20: 5 users, permanent
4 of 20: 5 users, permanent
5 of 20: 5 users, permanent
6 of 20: 5 users, permanent
7 of 20: 1 users, permanent
8 of 20: 5 users, permanent
9 of 20: 1 users, permanent
10 of 20: 1 users, permanent
11 of 20: 2 users, permanent
12 of 20: 1 users, permanent
13 of 20: 1 users, permanent
14 of 20: 1 users, permanent
15 of 20: 1 users, permanent
16 of 20: 1 users, permanent
17 of 20: 1 users, permanent
18 of 20: 1 users, permanent
19 of 20: 1 users, permanent
20 of 20: 1 users, permanent

Tilman

Tilman · Post by **Tilman** » Wed Apr 11, 2007 8:58 am

Having said that, it seems to work, very infrequently.

Also, it's more less everybody in our company who's got the problem.

Beth · Post by **Beth** » Wed Apr 11, 2007 9:32 am

The first thing I noticed is that you are behind on service packs on your SQL server. We have seen some issues stemming from not having later service packs.

I would recommend upgrading to service pack 4, unless you need to be able to delete entire repositories, in which case I'd recommend service pack 3a.

At the same time, can you check on the last couple of questions I had on your SQL server in my first post?

Tilman · Post by **Tilman** » Wed Apr 11, 2007 9:51 am

Sorry, overlooked those questions.

The sgvault.mdf is 17GB and the sgvault_log.ldf is 7GB, and they are allowed unrestricted growth.

Maybe I should also mention that the database ran out of space because the disk as full. We did create some more space, which made the 'FailDB...' errors go away, and after that the problems occured.

Tilman

Beth · Post by **Beth** » Wed Apr 11, 2007 1:45 pm

When the SQL server runs out of space it definitely can cause issues, so now it just appears to be a few remaining glitches after you gave it space.

I have seen some occasional weirdnesses with large log files. You might want to consider truncating that log.

1) First, perform a backup of your database
2) In the query analyzer run
BACKUP LOG sgvault TRUNCATE_ONLY,
3) Then in the query analyzer run
DBCC SHRINKDATABASE('sgvault', 0, TRUNCATEONLY)
4) Perform a fresh back-up.

Tilman · Post by **Tilman** » Thu Apr 12, 2007 5:32 am

Hi again,

Thanks for your help, we have now moved our Vault database to a new beefy server which seems to have fixed the problem.

Tilman