I cannot preview reports when using any embedded DS connection. I can however preview reports if I switch to 'Shared' DS connections.
I am on Visual Studio 2017 version 15.7.5
Any ideas why?
Embedded Data Source Configuration is given below.
Check with the credentials under data source properties
Can you attach a screenshot for the following issue ,so that we can get an exact solution to your problem
Related
Can someone help me with the error: Failed to save modifications to the server. Error returned: 'The following system error occurred: Class not registered
'.
I am getting this while loading the excel/csv. I tried uninstalling the application quite many times but no luck, I still see the same issue
Can you please share the source from where you downloaded the Power BI?
If you have downloaded from Microsoft windows store, try uninstalling it and then reinstall Power BI with installer instead of Microsoft Store version from the official website.
Download the version of Power BI Desktop that matches the architecture (x86 or x64) of your Windows OS. Run the MSI installer and follow the setup steps.
Microsoft Power BI Desktop is available for 32-bit (x86) and 64-bit (x64) platforms.
Thanks!
It could be server to desktop version mismatch. Are you using power-BI report server or cloud service? What is the version of your desktop power-BI?
Are you using any custom connector?
It seems to me the compatibility issue.
The last thing I would request you to check is the size of the file you are trying to publish.
Hope you are doing well.
I really need your help.
I am trying to create a tabular model in Azure analysis service with SSDT 2017.
Data is in Azure SQL Server.
I chose the compatibility 1400 and I saw the database objets.
But when I try to import data from the database I have an error "error ole dB".
I have also created a model with compatibility 1200. And all runs well with this compatibility.
Do you have any Idea on how to solve this issue ?
Please check your Azure SQL database compatibility level.
In SSMS, right-click the database name > Properties > Compatibility Level.
For more details, please reference: Compatibility level for Analysis Services tabular models.
Set the compatibility level 140 and try again.
Hope this helps.
Please try the latest version of SSDT 2017 (15.9.0). Download and install from here. Before installing SSDT for Visual Studio 2017 (15.9.0), uninstall Analysis Services Projects and Reporting Services Projects extensions, and close all VS instances.
Another possible solution is to try SSDT 2019. If you do not have VS 2019 download and install the Community version, then install the Analysis Services extension.
It is really unbelievable that I am not able to find such a simple thing, I have searched everywhere.
Actually I want to open sdf file which is a part of my project. I found that it can be opened with sql server management studio, external tools etc. but I want to open it in Visual studio by adding a simple data connection.
Am I asking too much? But Man! I am not able to find this simple thing on internet.
I my add connection window I don't see option for sql server compact data connection.
I already installed compact edition and when I am trying to install it again it is saying that it is already installed.
But for some reason visual studio is not showing up in the list of Data Sources Types.
I found this question, he is facing the same issue and his issue was also not resolved even after applying what was told in the answer
Adding SQL Server Compact Edition data source to Visual Studio?
Could somebody help to get this simple thing working?
Install the SQL Server Compact Toolbox, it will also install a DDEX provider, that allows you to connect in Server Explorer (for 4.0 only, however)
Using Visual Studio 2017 with Data Lake Tools v. 2.3.1000.1, I am unable to submit a U-SQL job directly to Azure. I only have the option to submit locally:
This is the case even though I am connected to Azure through the "Server Explorer" tool window, from which I can access my U-SQL databases, view jobs that were previously submitted to Azure, etc.:
Using Visual Studio 2015, I have no such issue:
Am I forgetting a setting or a property somewhere, or is this perhaps a bug in Data Lake Tools for VS2017?
Do you still have the issue?
I sometimes see this happen if I open an existing solution and the tabs are already open, and I have not yet logged in. I then log in and the drop down menu of the open window will not be refreshed.
I close and reopen the script and it normally shows up.
Another reason, that I think will be addressed soon, could be that you have a filter on your cloud view explorer on which subscriptions you expose. If you hid the subscription there with your ADLA account, you will not see it in the pull down.
In any case, please let us know if you still have the issue and none of the two suggestions help.
I would like to debug the Sitecore code just like asp.net code, but do not know how to.
The solution is outside wwwroot.
Using Visual Studio 2013, IIS 10.0, Windows 10, Sitecore 8
Does attaching a process, is all I have to do to be able to debug.
In Visual Studio, when I click on Tools > Attach Process, there is no aspnet_wp.exe or w3wp.exe.
Is there any other process to follow.
When you try Debug > Attach to Proces please make sure your site is running.
Please also check if "Show Process from all users" is checked.
See below picture:
You can use dotpeek to debug the Sitecore Code.
Steps to debug Sitecore Code:
Download and Install Dotpeek.
Open dotPeek and click on StartSymbolServer default dotPeek uses port 33417.
Open Visual Studio options
In Debugging/Symbols tab click on add new symbol files location and enter http://localhost:33417 (or the port that you assigned in the previous step)
In VS options go to Debugging/General and uncheck “Enable Just My Code” option if it is checked
In dotPeek click on open icon that will show a dialog for loading an assembly
After the assembly is loaded right click on it and click generate pdb. In the appeared window choose the namespaces that you need to debug (or each one as I did) and click Generate
Now we are ready for debugging
Open VS and attach to the sitecore process (loading symbols may take longer than usual)
More info: http://bilyukov.com/debugging-sitecore-dotpeek/
Note: You can also export the Sitecore dll to a VS Solution in dotpeek along with its pdb file, then follow the above steps to configure your VS. You need to attach to the Process of the exported Sitecore Solution.
I use Attach to Process in Sitecore rocks.
Sitecore Rocks can be found in the Visual Studio Marketplace via the Tools | Extensions and Updates option in visual studio. Search for Sitecore Rocks in the Online folder.
If you want to attach to w3wp.exe you have to make sure the website is running in IIS under its own app pool with its own domain binded as well as host file updated to associate that domain with localhost 127.0.0.1. If you need more help, along with simplified detailed instructions, please reach out to me.
You can do one thing in this case. Go in Visual Studio to Debug > Attach to process....
Now you'll see a window containing available processes. We need to connect to IIS , hence mark the checkbox saying Show processes from all users. Once you do that, you'll find a process w3wp.exe. Jut select it and click Attach.