Hi,
i am trying to check in the files from my local server on live server but its showing the following message in
server error log
----5/8/2012 11:26:14 AM faisal--111.68.106.201.pern.pk(111.68.106.201)--SSL Disabled FailExistingTx
kindly guide me whats the issue.
Regards,
Faisal
Project is not checking in into server
Re: Project is not checking in into server
What is the size of the file you are checking in?
Can you look in your Vault Server Log for the errors surrounding that check in? That might tell us more.
Are you adding a file, or is this a change to a file that is in Vault?
Can you look in your Vault Server Log for the errors surrounding that check in? That might tell us more.
Are you adding a file, or is this a change to a file that is in Vault?
Beth Kieler
SourceGear Technical Support
SourceGear Technical Support
-
- Posts: 3
- Joined: Tue May 08, 2012 12:45 am
Re: Project is not checking in into server
Hi,
File size is about 40 kb. and i am changing in existing file not adding new file.
Regards,
Faisal
File size is about 40 kb. and i am changing in existing file not adding new file.
Regards,
Faisal
Re: Project is not checking in into server
Is the file a binary file?
Can you send me your Vault Server Log? You can send it to support at sourcegear.com (attn: Beth), and please include a link to this forum thread.
Can you send me your Vault Server Log? You can send it to support at sourcegear.com (attn: Beth), and please include a link to this forum thread.
Beth Kieler
SourceGear Technical Support
SourceGear Technical Support
-
- Posts: 3
- Joined: Tue May 08, 2012 12:45 am
Re: Project is not checking in into server
Hi,
The File i gonna to check in is .aspx file. i have send the file to sourcegear.com
Regards,
Faisal
The File i gonna to check in is .aspx file. i have send the file to sourcegear.com
Regards,
Faisal
You do not have the required permissions to view the files attached to this post.
Re: Project is not checking in into server
The email didn't arrive.
I'd like to have you increase your logging level on both the server and the client, then try to check in, and then send me your new sgvault.log and VaultGUIclient.txt.
Server level logging:
1) Go to C:\Windows\temp\sgvault and rename the log sgvault.log. This will force Vault to create a new one that will just cover the information that's needed.
2) Open the Vault admin web page and click on the logging link.
3) Change the logging level from Quiet to Debug.
4) Change the archive level from weekly to daily.
5) Click Save. All users will be disconnected and need to login again.
Client-side logging:
1) Close all instances of the Vault GUI client on the machine.
2) Go to %temp% and find the file VaultGUIClient.txt. Rename that file to force Vault to create a new one that will just cover the information that's needed. If you can't find the log, continue onto step 3.
3) Open a Vault GUI client, but don't log in.
4) Press the key combination Ctrl - Alt - Shift - F12.
5) In the lower left corner of the Vault window will be a path listed for the log.
6) Now you may go to File - Connect to Server to login and continue your test.
7) The debug level Vault Client-side logging will stop when you restart the Vault GUI client.
I'd like to have you increase your logging level on both the server and the client, then try to check in, and then send me your new sgvault.log and VaultGUIclient.txt.
Server level logging:
1) Go to C:\Windows\temp\sgvault and rename the log sgvault.log. This will force Vault to create a new one that will just cover the information that's needed.
2) Open the Vault admin web page and click on the logging link.
3) Change the logging level from Quiet to Debug.
4) Change the archive level from weekly to daily.
5) Click Save. All users will be disconnected and need to login again.
Client-side logging:
1) Close all instances of the Vault GUI client on the machine.
2) Go to %temp% and find the file VaultGUIClient.txt. Rename that file to force Vault to create a new one that will just cover the information that's needed. If you can't find the log, continue onto step 3.
3) Open a Vault GUI client, but don't log in.
4) Press the key combination Ctrl - Alt - Shift - F12.
5) In the lower left corner of the Vault window will be a path listed for the log.
6) Now you may go to File - Connect to Server to login and continue your test.
7) The debug level Vault Client-side logging will stop when you restart the Vault GUI client.
Beth Kieler
SourceGear Technical Support
SourceGear Technical Support