Running Vault Pro 6.1.0.30531.
Browsing the web interface for Vault Pro item tracking I start with "Projects At-A-Glance" then click on the name of the first available item tracking project which then shows the "Recent Items" page for that project.
I now click on "Open" and get a list of items with status Open in the same project. If I use the drop-down at the top of the page to change projects it will sometimes work but most often will display an error page with the text "An unknown error has occurred".
I can find nothing in the server logs relating to this error.
Cheers,
Brett
Item Tracking unknown error
Re: Item Tracking unknown error
Is there anything in the Event Viewer related to the error?
Is there any pattern as to when this happens and when it doesn't?
Is there any pattern as to when this happens and when it doesn't?
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager
Re: Item Tracking unknown error
Nothing I can find in Event Viewer on either computer. No discernible pattern either, moving from first project to the second gives the error as does moving from second to first.
The only log info I can find is in the IIS logs:
2013-02-04 11:51:43 W3SVC1 xxx.xx.xxx.xxx GET /VaultService/VaultWeb/Login.aspx ReturnUrl=%2fVaultPro%2f 80 - 10.10.15.12 Mozilla/5.0+(compatible;+MSIE+10.0;+Windows+NT+6.2;+WOW64;+Trident/6.0) 302 0 0
2013-02-04 11:51:44 W3SVC1 xxx.xx.xxx.xxx GET /VaultPro/ - 80 - 10.10.15.12 Mozilla/5.0+(compatible;+MSIE+10.0;+Windows+NT+6.2;+WOW64;+Trident/6.0) 200 0 0
2013-02-04 11:51:46 W3SVC1 xxx.xx.xxx.xxx GET /VaultPro/Recent.aspx pid=105 80 - 10.10.15.12 Mozilla/5.0+(compatible;+MSIE+10.0;+Windows+NT+6.2;+WOW64;+Trident/6.0) 200 0 0
2013-02-04 11:51:49 W3SVC1 xxx.xx.xxx.xxx GET /VaultPro/OpenItems.aspx pid=105&qg=OpenItems&grouped=true 80 - 10.10.15.12 Mozilla/5.0+(compatible;+MSIE+10.0;+Windows+NT+6.2;+WOW64;+Trident/6.0) 200 0 0
2013-02-04 11:51:55 W3SVC1 xxx.xx.xxx.xxx POST /VaultPro/OpenItems.aspx pid=105&qg=OpenItems&grouped=true 80 - 10.10.15.12 Mozilla/5.0+(compatible;+MSIE+10.0;+Windows+NT+6.2;+WOW64;+Trident/6.0) 302 0 0
2013-02-04 11:51:55 W3SVC1 xxx.xx.xxx.xxx GET /VaultPro/OpenItems.aspx pid=103 80 - 10.10.15.12 Mozilla/5.0+(compatible;+MSIE+10.0;+Windows+NT+6.2;+WOW64;+Trident/6.0) 302 0 0
2013-02-04 11:51:55 W3SVC1 xxx.xx.xxx.xxx GET /VaultPro/Error.aspx - 80 - 10.10.15.12 Mozilla/5.0+(compatible;+MSIE+10.0;+Windows+NT+6.2;+WOW64;+Trident/6.0) 200 0 0
The only log info I can find is in the IIS logs:
2013-02-04 11:51:43 W3SVC1 xxx.xx.xxx.xxx GET /VaultService/VaultWeb/Login.aspx ReturnUrl=%2fVaultPro%2f 80 - 10.10.15.12 Mozilla/5.0+(compatible;+MSIE+10.0;+Windows+NT+6.2;+WOW64;+Trident/6.0) 302 0 0
2013-02-04 11:51:44 W3SVC1 xxx.xx.xxx.xxx GET /VaultPro/ - 80 - 10.10.15.12 Mozilla/5.0+(compatible;+MSIE+10.0;+Windows+NT+6.2;+WOW64;+Trident/6.0) 200 0 0
2013-02-04 11:51:46 W3SVC1 xxx.xx.xxx.xxx GET /VaultPro/Recent.aspx pid=105 80 - 10.10.15.12 Mozilla/5.0+(compatible;+MSIE+10.0;+Windows+NT+6.2;+WOW64;+Trident/6.0) 200 0 0
2013-02-04 11:51:49 W3SVC1 xxx.xx.xxx.xxx GET /VaultPro/OpenItems.aspx pid=105&qg=OpenItems&grouped=true 80 - 10.10.15.12 Mozilla/5.0+(compatible;+MSIE+10.0;+Windows+NT+6.2;+WOW64;+Trident/6.0) 200 0 0
2013-02-04 11:51:55 W3SVC1 xxx.xx.xxx.xxx POST /VaultPro/OpenItems.aspx pid=105&qg=OpenItems&grouped=true 80 - 10.10.15.12 Mozilla/5.0+(compatible;+MSIE+10.0;+Windows+NT+6.2;+WOW64;+Trident/6.0) 302 0 0
2013-02-04 11:51:55 W3SVC1 xxx.xx.xxx.xxx GET /VaultPro/OpenItems.aspx pid=103 80 - 10.10.15.12 Mozilla/5.0+(compatible;+MSIE+10.0;+Windows+NT+6.2;+WOW64;+Trident/6.0) 302 0 0
2013-02-04 11:51:55 W3SVC1 xxx.xx.xxx.xxx GET /VaultPro/Error.aspx - 80 - 10.10.15.12 Mozilla/5.0+(compatible;+MSIE+10.0;+Windows+NT+6.2;+WOW64;+Trident/6.0) 200 0 0
Re: Item Tracking unknown error
I'll need to consult with our developers on this one, since we don't have much to go on.
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager
Re: Item Tracking unknown error
We were able to reproduce this.
I've logged bug 16762 and we hope to fix it for Vault 7, due out later this year. Thanks for the report!
I've logged bug 16762 and we hope to fix it for Vault 7, due out later this year. Thanks for the report!
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager