Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problem to configure and run mssql.RSReports plugin #1

Open
ldaniel opened this issue Sep 6, 2016 · 11 comments
Open

Problem to configure and run mssql.RSReports plugin #1

ldaniel opened this issue Sep 6, 2016 · 11 comments

Comments

@ldaniel
Copy link

ldaniel commented Sep 6, 2016

Hi,

I'm trying to use the Reporting Services plugin mssql.RSReports. During the package configuration phase, I'm no sure about which values go in the following fields:

Server Path: (What kind/format of value is expected here?)
Data Source Path: (What kind/format of value is expected here?)
Data Source Parent: (What kind/format of value is expected here?)

Anyway, when I try to run the deployment I get the following error:

Uploading artifact [C:\windows\temp\ot-20160906T115512659\reports_AppTest.zip]
The splatting operator '@' cannot be used to reference variables in an expressi
on. '@set' can be used only as an argument to a command. To reference variables
in an expression use '$Set'.
At C:\windows\temp\ot-20160906T115512659.1\deploy-rsreports.ps1:241 char:6
' + @set <<<< Datasource for alle reports in serverPath location
' + CategoryInfo : ParserError: (Set:String) [], ParentContainsErro
rRecordException
' + FullyQualifiedErrorId : SplattingNotPermitted

When I look at line 241 in the generated PowerShell script on target server during the deployment phase, I have this:

@set Datasource for alle reports in serverPath location

I believe that the correct sentence should be:

Set Datasource for alle reports in serverPath location

At this point, I'm not sure whether the error comes from my previous configuration or from the Plugin installation.

Does anyone know what is the correct configuration and how to solve this error?

Thanks,

Leandro Daniel

@jdewinne
Copy link
Contributor

Hi,

I think this already got fixed. Which version are you using?

Regards,
Joris

@ldaniel
Copy link
Author

ldaniel commented Sep 14, 2016

Hi Joris,

According to the about screen on XLD: ssrs-plugin 1.1.0.

Regards,

Leandro Daniel

@jdewinne
Copy link
Contributor

Hi Leandro,

Can you upgrade to 2.0.1?

Regards,
Joris

@ldaniel
Copy link
Author

ldaniel commented Sep 16, 2016

Hi Joris,

Yes, I'm working on it and I will get back to you when done.

Thanks & regards,

Leandro Daniel

@ldaniel
Copy link
Author

ldaniel commented Sep 19, 2016

Hi Joris,

Since we share the plugin usage with other teams, I have compared the current version installed (1.1.0) with the latest one you suggested me to update.

The oldest version handles two types of XLD classes: mssql.RSReports and mssql.RSSync. However, the latest version (2.0.1) only has the mssql.RSReports funcionality, which will impact the current users of the plugin.

Is it possible to keep the mssql.RSSync type in the latest version?

Thanks & regards,

Leandro Daniel

@jdewinne
Copy link
Contributor

Hi,

Can you share your current version 1.1.0 with me so I can have a look? As that version isn't an official release, it might have been customized specific for you, or was part of our old community structure.

Regards,
Joris

@ldaniel
Copy link
Author

ldaniel commented Sep 20, 2016

Hi Joris, yes, I can share our version. How do you prefer, send it via e-mail or another way?

Regards,
Leandro Daniel

@jdewinne
Copy link
Contributor

Hi,

Can't you attach it within this issue?

Regards,
Joris

@ldaniel
Copy link
Author

ldaniel commented Sep 21, 2016

Hi Joris, please, see attached.
ssrs-1.1.0.zip

Regards,
Leandro Daniel

@jdewinne
Copy link
Contributor

Thanks. I've added the mssql.RSSync deployable to the master branch. However, the zip you attached doesn't contain the destroy-rssync.ps1 script. Do you have that available, or should I remove that rule?

Regards,
Joris

@ldaniel
Copy link
Author

ldaniel commented Sep 29, 2016

Hi Joris, just giving you an update on this. I am currently in contact with the team who owners the plugin type and I will get back to you as soon as possible.

Regard,
Leandro Daniel

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants