Power Query script to get msmdsrv.exe port number via R

100%

Power Query script to get msmdsrv.exe port number via R

✓ Published0🌍 Public

Last edited Mar 13, 2017

Created on Mar 13, 2017

This example shows how to retrieve the port number of the msmdsrv.exe process by combining R scripts with Power Query’s M language. It first runs a system command via `system2` to capture the task list and netstat output, then parses the results using `read.fwf` with fixed-width columns. The M code invokes the R script through `R.Execute`, formats the resulting tables with `Table.TransformColumns` and `Table.PromoteHeaders`, and finally joins the process ID from the task list with the matching netstat entry to extract the local address port. The visualization relies on text-based data processing rather than graphical libraries.

AI-generated description

Similar vizzes

Loading thumbnail…

Getting $Embedded$ connection details in Power Query via R

This example shows how to extract connection details for the Power Query engine by querying system processes and network ports. It retrieves the process ID of `msmdsrv.exe` from a filtered `tasklist` command and then cross-references it with TCP port information obtained via `netstat`. The R script parses the command-line output into fixed-width tables using base R functions (`read.fwf`, `textConnection`, `system2`). No external visualization libraries are used; the focus is on data wrangling through R's base I/O and text-processing capabilities, making the connection details available for later analysis.

HHugoberry

80% match

Loading thumbnail…

Gist ed4042b20f9bcfc3ee801039049ad47f

This example shows the port number on which the SQL Server Analysis Services process (msmdsrv.exe) is listening by extracting it from live TCP connection data. It first identifies the process ID using the Windows `tasklist` command, then filters `netstat -ano` output for established connections matching that PID, and finally parses the local address to isolate the port. The visualization is implemented in Power Query’s M language, which invokes an embedded R script via the `R.Execute` function to perform the system calls and string processing. The result is a single value displayed as a table cell, demonstrating a system-monitoring query rendered through the Power BI data pipeline.

HHugoberry

76% match

Loading thumbnail…

Power Query finding port number of the running embeded tabular instance

This example shows how to locate the port number of a running embedded tabular instance in Power BI Desktop by reading a specific file from the user’s local workspace. It demonstrates a Power Query M function that dynamically identifies the current user by sorting folders in `C:\Users` by their `Date accessed` property, then navigates to the corresponding `AnalysisServicesWorkspaces` subfolder. The code uses the `Folder.Contents` and `Folder.Files` APIs to traverse the filesystem, filters for the file named `msmdsrv.port.txt`, and extracts its content using `Lines.FromBinary` with a specific code page. The result is the port number, presented as a text value.

HHugoberry

74% match

Loading thumbnail…

Gist 44e95c5ae2e212c1b41485ea7e31e0c4

This example shows a Power Query function that connects to an embedded Power BI Desktop tabular model and retrieves session information from the `$SYSTEM.DISCOVER_SESSIONS` dynamic management view. The function first locates the most recently accessed user profile folder, reads the `msmdsrv.port.txt` file to obtain the local port number, then uses that port to list available databases via the `AnalysisServices.Databases` API. It selects the first database and executes the provided DAX query using `AnalysisServices.Database`. The code demonstrates dynamic file system traversal, port discovery, and parameterized Analysis Services queries within the Power Query M language.

HHugoberry

70% match

Loading thumbnail…

Extracting Power Query queries

This example shows how to extract Power Query query definitions from an embedded Power BI tabular model by reading the model’s in-memory connection string. The PowerShell script first locates the dynamic port number for the local Analysis Services instance by scanning workspace files for `msmdsrv.port.txt`. It then uses the `Invoke-ASCmd` cmdlet to query the `$SYSTEM.TMSCHEMA_DATA_SOURCES` schema, revealing the connection string. The script decodes the base64-encoded `Mashup` portion of that string, writes it to a binary ZIP archive, and uses `System.IO.Compression.ZipFile` to extract `Section1.m`, which contains the readable Power Query formulas. This approach exposes the model’s underlying data-transformation logic without any direct UI interaction.

HHugoberry

70% match

Loading thumbnail…

R.Execute example without the use of R.Execute() in Power Query [behind the scenes this gets executed bin\x64\Rscript.exe" --encoding=UTF-8 RScriptWrapper.R"]

This example demonstrates how to execute an R script from within Power Query without explicitly invoking the `R.Execute` function, instead relying on the `AdoDotNet.DataSource` with the `R.Provider` to run a native query. The code passes a string containing an `output` variable that captures the result of `system2("whoami", stdout=TRUE)`, which retrieves the current username. The resulting table is then converted from binary R data using `RData.FromBinary`. This approach showcases the underlying use of `Rscript.exe` via the provider, highlighting an alternative integration path for R workflows in Power Query.

HHugoberry

69% match

Loading thumbnail…

STDOUT as data source in Power Query M

This example demonstrates how to capture a command-line program's standard output as a data source in Power Query M. It shows a minimal query that retrieves the current user name by running the `whoami` command, then feeds that result into a table. The implementation relies on the `R.Execute` function to invoke an R script, which uses `system2` with `stdout=TRUE` to capture the command's output, and `read.table` to parse it into a data frame. The resulting table is then returned as the query's output. This approach highlights a practical bridge between operating system commands and Power BI's data transformation layer.

HHugoberry

66% match

Loading thumbnail…

Gist 1ebcc44e40d3ea92b4063ad981cac31f

This example shows how to extract and prepare query log data from a local Power BI Tabular model for further analysis. It demonstrates reading the most recent `msmdsrv.port.txt` file from the Power BI Desktop Analysis Services workspace folder to obtain the active port number. The code then uses the `AnalysisServices.Database` function to connect to that port, retrieves the database catalog name, and evaluates the `QueryLog` table. Finally, it renames two columns—`SESSION_LAST_COMMAND_START_TIME` and `SESSION_LAST_COMMAND`—to clean the schema for downstream use in Power Query.

HHugoberry

66% match