We have been using TFS with Visual Studio 2010 for quite sometime and untill yesterday the mail notifications(alerts) were being sent out properly .
Since today morning however it has stopped working and i am not able to figure out why ?
Any suggestions as to what could be wrong ?
You can get some good error information by setting the NotificationJobLogLevel to 2 and then querying the JobHistory table in the database. This should show you any errors that are occurring.
Related
We migrated our TFS 2017 to TFS 2018 by first using the "Move or Clone Team Foundation Server from one hardware to another" instructions (https://learn.microsoft.com/en-us/tfs/server/admin/move-clone-hardware) and then upgrading that to TFS 2018 which seemed to go just fine. TFS works, however the URLs in the emails that go out regarding work items are still pointing at the old server. The only URL that I can find to change is the Public URL on the Application Tier, which is already correct. In the message header on the emails that are sent out, the old server also appears to be the sending domain:
In-Reply-To: Tfs.WorkItem.Project.######oldservername
I can't find references to that old server anywhere though. Any idea what I might be missing?
We were able to find the issue. The tbl_AccessMapping table in the database for the Project Collection had different values in it than the tbl_AccessMapping table in the tfs_teamfoundationconfiguration database (specifically the accesspoint field). tfs_teamfoundationconfiguration was correct, so we synced those correct values over to the Project Collection database.
This took some time to take effect, I assume due to caching. Restarting IIS would likely fix it quicker.
I'm using TFS2015.
I made a change to C:\Program Files\Microsoft Team Foundation Server 14.0\Application Tier\TFSJobAgent\Transforms\1033\BuildCompletedEvent.xsl and now I'm no longer getting email alerts. So presumably, an error in my .xsl, but I can't seem to find any documentation on where such errors would get logged to.
I looked in the database at [Tfs_Configuration].[dbo].[tbl_JobHistory] but I see nothing relevant.
Worse, I reverted my changes and I'm still not getting email alerts. Unclear how to figure out what I did wrong and how to fix it.
There is a way to diagnose Email Alert logs with below command:
-diagnosing-email-and-soap-subscription-failures/
More detail steps and info please refer this blog from MSDN: TFS2010: Diagnosing Email and SOAP subscription failures
Figured it out. If there's an XSL transform error, it gets mailed to you as the notification. I had another notification issue which was preventing emails from getting to me at all.
I am using WebConnector version -2.1.0.30 with QuickBooks 2015 Enterprise.
WebConnector was working fine but all of a sudden when I run WebConnector and click on "Update Selected" button then it came up with this error (Note: by that time no one was logged on to QuickBooks).
Then as a quick fix I have deleted that QWC file and added a New one, that works fine.
Can any one please come up with a better solution and the reason behind this error.
Thanks in advance.
Chances are you're running QuickBooks on a shared Windows Server, or in a hosted scenario with someone like Right Networks, Intuit Cloud, Cloud9, etc.
If so, this error means that Windows Server auto-logged-out some user and closed QuickBooks for them, but is still holding the file lock on the QuickBooks company file. Windows will automatically release the file lock after a short amount of time (usually 30 minutes to an hour).
There is no "fix" outside of waiting for a while, and then trying again.
I am having a weird error when it comes to one of my projects in visual studio. I can start to debug, but when I run into an error or Visual Studio needs time to create a data tip my IIS express instance is lost and it will create a duplicate. After this happens and I try to hit the page again my browser will try to connect but will never get a response. I have tried to stop debugging and then start back up, but the IIS instance persists and I get the same result, trying to connect but no response. Also all of my break points turn to the not able to hit symbol.The only way to get back to being able to debug is to close visual studio and open it back up again. I'm sorry I don't have anymore information, but it almost seems to happen randomly.
Thanks in advance
Edit
This is what the break point looks like after I have stopped and restarted debugging.
I end up finding out the issue for anyone having the same problem. My initial question was not exactly what was happening. Whenever I stopped the IIS instance, the port that I was running the server on was being taken over by a Microsoft process. So when I hit run again my process was blocked and then showing the error above.
In order to fix this issue. I had to change the virtual directory for the project. You can do so by clicking in the web project and selecting properties. Pick Web on the left hand side and then change the url with to contain a different port and then click on create virtual directory.
So, we are using TFS 2012 RC and have modified the work flow a bit for a regular task item by adding a few custom transition states.
When updating tasks though Visual Studio 2012 RC, everything works fine. I can move through all the states without any problems. However, when updating the task through TFS Portal, either by dragging the item on the board or opening the form and changing the state using the pulldown, I get the following error: "TF237165: Team Foundation could not update the work item because of a validation error on the server. This may happen because the work item type has been modified or destroyed, or you do not have permission to update the work item."
This ONLY happens, however, when moving to the Done state and nothing else. All other states work fine.
So, I'm not sure what that means since it works fine in Visual Studio. What would be helpful if I could see the exception or more information somewhere, but I don't know where these validation errors are stored.
Any help would be greatly appreciated!
The issue was with the work flow. The transition was setting a field that was conflicting with the state also changing the same field.
In my case there was another issue.
The problem was that the field had a trailing \r\n in the data being sent down by the server. I believe the client javascript OM was removing this which makes the field dirty even though it’s read only.
Workaround was to make the field read-write instead of read-only. Then I set back it to read-only - and now it works.
Micrsoft promised they may fix it in next release.
In my case, on TFS 2013 U5 I had changed my TFS Profile DisplayName so that it did not match my ActiveDirectory DisplayName. I could not edit or create anything until I changed the DisplayName back.