I want to connect jdbc salesforce in glue studio with JWT Authentication. The problem is that glue studio does not recognize escape parameters '/n' and takes it as a character. Do you know if glue studio uses any other escape parameters?
Cuz when I do OAuthJWTCert='all characters of pemfile' throws me this error "Member must have length less than or equal to 1024"
Related
I trying to integrate a power virtual agent bot with some flows to a bot that i have already created and deployed to teams.
So im following this documentation https://learn.microsoft.com/en-us/power-virtual-agents/advanced-use-dispatcher
As its said im trying to create a dispatcher and for that first i need to run the ContentConverter utility sample and im using: dotnet run -p ContentConverter.csproj -c Release -- -i -c -b
But im getting the error "The syntax of the command is incorrect."
Paths should not include angle brackets (<>). Angle brackets are used in sample commands to show something that needs to be replaced by your own info.
I have created a statless service fabric application in visual studio and need to publish two instances of it. The first goes well, but when i try to pusblish the second app i get the error:
2>Application Type DevelopmentType and Version 1.0.0 was already registered with Cluster, unregistering it...
2>Unregister-ServiceFabricApplicationType : Application type and version is still in use
2>At C:\Program Files\Microsoft SDKs\Service
2>Fabric\Tools\PSModule\ServiceFabricSDK\Publish-NewServiceFabricApplication.ps1:224 char:20
2>+ $reg | Unregister-ServiceFabricApplicationType -Force
2>+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2> + CategoryInfo : InvalidOperation: (Microsoft.Servi...usterConnection:ClusterConnection) [Unregister-Serv
2> iceFabricApplicationType], FabricException
2> + FullyQualifiedErrorId : UnregisterApplicationTypeErrorId,Microsoft.ServiceFabric.Powershell.UnregisterApplicatio
2> nType
2>
2>Finished executing script 'Deploy-FabricApplication.ps1'.
I want the instance to have the same ApplicationType, but when i publish with a new application name and a new publish profile i only get the error above.
The problem is that you're essentially trying to overwrite the existing app type with a new one but since the existing app type has an app associated with it, you get this error. In order to "overwrite" the app type, the system would need to delete it and register the new one. But it can't be deleted because it has an existing app associated with it. So that's why you get this error.
A little background on the difference between an application type and an application. It's sort of like the difference between a class and an instance in programming. An app type represents what an app can be. It contains the code, configuration, and data. But an app type is just a definition; it's not a running app. When you create an app, you create it to be based on an app type. Now you've got a running application. Just like the programming analogy, you can create multiple applications from one app type, which is what you're trying to do.
When you deploy from VS, it doesn't know your intention that you want to create a new application from an existing app type on the cluster. It assumes you want to deploy the application with the code that you've defined in your project. Since VS doesn't know how that code differs from what is on the cluster, it proceeds with attempting to remove any conflicting app type (an app type with the same name and version) in order to register a new app type with the code that was contained in your project. And that's when you run into the error.
So how do you resolve this? If your intention is really to just create another application from the existing app type, without any code differences between the two applications, then you'll need to handle this directly from PowerShell and not use VS. What you're trying to do is just basic management of your cluster. You'll want to use the New-ServiceFabricApplication PowerShell cmdlet (see https://learn.microsoft.com/en-us/powershell/servicefabric/vlatest/new-servicefabricapplication). Note that if you haven't configuration your application properly, you may run into port conflicts between the two applications. To avoid that, you'd want to parameterize your ports in your app manifest so that you can provide different port values when invoking New-ServiceFabricApplication.
When you edit a sql file in the Transact-SQL Editor in VS, you can push the connect button to bring up a db connection dialogue. How can I automate this from a VS extension? I can catch the fileOpen event no problem. Does anyone know where in DTE the connect command is hiding? Not just popping the dialogue, but a method that takes a connection string and connects the editor window.
Update
I've listed all my VS commands. The one corresponding to the connect button is "SQL.TSqlEditorConnect". I don't seem able to call it without getting in an endless loop, and I suspect it's just the command for opening the dialog, not creating the connection.
use the 'sqlcmd' as follows:
sqlcmd -S <ComputerName>\<InstanceName> -i C:\Temp\ClearTables.sql
As seen : Executing set of SQL queries using batch file?
edit::
Have you tried:
OPEN DATABASE [FileName | ?] [EXCLUSIVE | SHARED] [NOUPDATE] [VALIDATE]
As seen here -> https://msdn.microsoft.com/en-us/library/w01w7w4c%28v=vs.80%29.aspx
**Second Edit:: ** Have you tried SSH?
Thanks to Kevin Cunnane of MS's SSDT team, the answer is a service called the ISqlServerObjectExplorerService. This has an OpenQuery method that takes in a connection string.
This is available via the standard VS extensibility model (in your package, call either GetService or GetGlobalService, referencing this service).
ISqlServerObjectExplorerService service = DataPackage.Instance.GetService<ISqlServerObjectExplorerService>(typeof(ISqlServerObjectExplorerService));
if (service != null)
{
service.OpenQuery(new SqlConnectionStringBuilder(myConnectionString));
}
I am trying to understand the procedure of Integration the IM Client with Outlook 2010. The below link is used for this :-
https://msdn.microsoft.com/en-us/library/office/jj900715.aspx
Outlook is able to reach the CreateInstance method of my implementation.
If I have the Lync Client installed than the controls reaches till GetInterfaceMethod, in which I am returning the object of ILyncClient.
There is no progress after this. Following error is showed in the outlook debugs :
MsoIMProviderFactory--HrEnsureDefaultIMAppRegKeys Succeeded opening reg key (HKCU-SOFTWARE\IM Providers)
CMsoIMProviderFactory--HrEnsureDefaultIMAppRegKeys Succeeded querying reg key (HKCU-SOFTWARE\IM Providers-DefaultIMApp-IMapp)
CMsoIMProviderFactory--HrEnsureDefaultIMProcessRegKey Succeeded opening reg key (HKCU-SOFTWARE\IM Providers\IMapp)
CMsoIMProviderFactory--HrEnsureDefaultIMProcessRegKey Succeeded opening reg key (HKLM-SOFTWARE\IM Providers\IMapp)
CMsoIMProviderFactory--WhichMessengerInProcessList Using (IMapp) process name for search
CMsoIMProviderFactory--WhichMessengerInProcessList Using (IMapp) process name for search
Guys please give your feedback regarding the same ?????
If I don’t have Lync Client Installed than control never reaches to Authentication Method.
A. Do we need to implement the IMessenger interface also ?
B. If yes then please show some pointers on how to do that ?
Any pointers to resolve this would be helpful.
For building the COM server we are using out of process COM example(CSExeCOMServer). I had tried the same setup with outlook 2013 also. In this too the output remains the same.
Environment :-
Windows 7 Service Pack1 .
Outlook 2010 & 2013.
You would always need Lync installed in you machine since the interfaces which you used in your code are defined by Lync. If you want to remove this dependency then you will have to register your typelibrary (.tlb) in the system. To generate .tlb you need an .idl file which you can explore on net how to get.
If you want to be an IM Provider then you need not implement this IMessenger interface. But if you want to work in Legacy provider way you will have to implement this interfaces(this i had not tried).
And to resolve your issue I would need the code snippet as how you are defining the LyncClient class. Once you share that then I would try to help you.
I was able to make this work in both outlook 2010 & 2013 but then I used C# way of implementing the COM Server.
I'm trying to do this:
import groovy.sql.Sql
def sql = Sql.newInstance(
url:'jdbc:sqlserver://localhost\\myDB',
user:'server\user', //this I don't think I need because of SSPI
password:'password',
driver:'com.microsoft.sqlserver.jdbc.SQLServerDriver',
SSPI: 'true'
)
The problem I'm having is that this connection is just timing out. I can ping the machine. I can also connect to the database with Managment Studio logged into my SSPI user (or whatever you call it, I start the Management Studio with a different user)
So I've tried that with my SoapUI as well, started the program as a different user, but I still time out when I initiate the connection. So something is very wrong with my connection string and any help would be appreciated.
P.S. Yes, I don't know what's up with the \ backslashes after the URL to the server, I guess it indicates that it's at the root. If I don't use them I get a message that I'm on the incorrect version.
And then we found the answer..... First of all I had the wrong JDBC driver installed. You need to head over to microsoft to get the real deal:
https://www.microsoft.com/en-us/download/details.aspx?id=11774
Then you need to unpack this one, place the 4 or 4.1 version in your bin directory of SoapUI. (You are apparently supposed to use Lib/Ext, but that doesn't work for me)
Then, since we are trying to use SSPI or Windows Authentication, to connect to the SQL server, you need to place the sqljdbc_auth.dll from the driver/enu/auth folder. This is used in one of your path's or in SoapUI Lib folder. Remember to use the 32 bit dll for 32 bit SoapUI!!! I did not since my system is 64.....
After this, I used this string, but now you have the setup correct, so it should work fine as long as you remember to start SoapUI up using the correct windows user. (Shif-right click - start as different user - use the same user you have started the SQL server with)
Again, I wasn't completely aware of this from the start (yes, total newbie here) and it failed.
Finally, when you have done all this, this is the string that works - and probably a lot of derivatives since the failing part here were the driver and dll.
def sql =Sql.newInstance("jdbc:sqlserver://localhost;Database=myDB;integratedSecurity=true","com.microsoft.sqlserver.jdbc.SQLServerDriver")