I am using Visual Studio Team System 2008, version 9.0.30729.1 SP. I have a database project that I was working with yesterday with no issues - I was able to build and deploy the database successfully. Today, however, when I open the solution I receive what is listed as a "Warning" that halts any Build/Deploy/etc process, but cannot be suppressed via the Project Properties page.
The Warning reads: "TSD3004: The application encountered an unexpected error. To diagnose this problem, enable tracing. You should contact product support."
I did contact Product Support, but they insist I pay for someone to help me get this fixed. There are zero records returned from an search of "TSD3004" on either MSDN or support.microsoft.com, and there are only three returned from a Google search (all irrelevant).
Can anyone please help me figure out what's happening?
Have you tried asking on Microsoft's dedicated forum?
http://social.msdn.microsoft.com/Forums/en-US/vstsdb/threads/
Actually I guess you did.. :)
http://social.msdn.microsoft.com/Forums/en-US/vstsdb/thread/eea24181-e115-4f56-a482-58059160d705
Related
I'm a starting dev and this site helped me a lot so far, thought somebody could maybe help with this. I have a SSD with 16kb sectors and couldn't install SQL Server 2022, ran the offered command solutions (did a bunch of other things in between, install and uninstall etc).
Now I find myself completely unable to even access SQL from shell (and also unable to uninstall express duplicates). Does anyone perhaps know what I could've messed up ? Tried to find solution on the website (and else) and couldn't find my specific problem.
Thanks in advance for any help.
EDIT : just realized the screens are in french, my bad. The shell screen states that <sqllocaldb> isn't recognized as a command name or function etc. First (white) screenshot is of my services displaying how I can't start SQL with an error code.
I have not been using Azure Machine Learning service (preview) for too long. To my knowledge it only has been released since the last Microsoft Ignite conference. That's why I think I can not find my question on StackOverflow or any other forum for that matter.
It is as follows:
With help of the Azure Machine Learning service SDK in Python I created my experiment in a Jupyter Notebook locally.
I then configured it to run a Hyper Drive config,
The results came in one by one (as I had a total of 50 runs and 4 simultaneously). It took 7 hours to complete the Hyper Drive run in total.
The next day I went to portal.azure.com to view the results and that worked. I was able to see every run of the hyperdrive and could even compare results.
But then....
I have no clue to as what could have happened, but when I tried to navigate to the experiment again I got a blank white screen. When opening the dev console via F12 I got so see a lot of red errors. All from react. I have zero experience with react, but I am quiet sure that this is the error. React errors when viewing experiment
Hope someone can help. Thanks in advance.
Thanks for reporting this! It's a known issue and a fix is being rolled out.
I have an error on an SSIS package. I tried to report it to Microsoft, but it seems there is no support at the page where i logged my ticket (https://connect.microsoft.com/SQLServer/feedback/details/2794452/error-when-openeing-or-executing-package)
Where am I supposed to log bug with MSSSIS?
Here is a link to a screen dump of the bug:https://www.dropbox.com/s/8ykgso5xuuw7vg4/SSIS%20package%20execution%20Visual%20Studio%20error.png?dl=0
Connect is not support. Is feedback.
If you need support, open a support case, via http://support.microsoft.com Note that support is not free.
The Microsoft node.js sql server driver (https://github.com/Azure/node-sqlserver) has not had any commits for 11 months. Anyone know what's going on with this effort? My company is using it actively, but has run across some issues that led me to the repo and the discovery that it seems to have been abandoned. Lots of open bugs also.
Should we give up on this driver and try another? Any recommendations?
Microsoft, please weigh in here.
I emailed the Microsoft main contributor and he was very helpful, although he did admit that officially MS has never declared one way or the other if they were going to continue support. Guess we'll wait and see.
In regards to my original problem - this info may help someone.
I was using queryRaw and listening for events to build the response. This method allows the user to submit multiple sql queries in one request (just separate them with ;). A large text datatype field was getting truncated and I couldn't figure out why. Turns out that the 'more' parameter that is supplied by the driver means that you must concatinate the return data.
Lots of trial and error when figuring out this driver.
I am trying to import customizations over to my server machine that is running Dynamics CRM 4. I am able to upload the customizations file on my CRM and it shows me all the entities.
However when I try to Import these entities CRM gives me an SQL Server error.
I need to get the details of the error and therefore I need to Enable tracing on the CRM server.
How do you enable tracing on Dynamics CRM? I have found quite many pages when I googled the term but I didn't quite get what i was looking for.
There's a Diagnostic Tool for 4.0 that enables tracing within CRM for you. Enabling tracing causes CRM to emit a ton of debug/error information and is definitely the first step we take when troubleshooting non-trivial issues. Often times the error will tell you exactly what's wrong.
You can get the diag tool from the CRMTools.zip link here. You'll want the CRMDiagTool4.zip file. Extract the contents of CRMDiagTool4.zip onto your CRM server and run the CrmDiagTool4.exe. From the dropdown menu, choose "Dynamics CRM Server". Click the first button to enable tracing. Enabling tracing is a huge performance hog, so enable it right before you start your import and disable it right after the error occurs.
To help you read the output, there's a CRM Trace File Viewer that lets you filter by message type. Reading the logs without it would be extremely painful. Open the viewer on the server and point it to one of the trace files that was generated (if you installed CRM to the default directory, those will be located in C:\Program Files\Microsoft CRM\Trace). Finally, filter the log entries down to warnings or worse by choosing Filter -> Log Level -> Warning. (A fancier version of the viewer is available as a part of the helpful and free Stunnware Tools.)
Good luck!