Following a restart of the Web Services Hub, the Plug-in for Informatica jobs launched from the command line end in FAIL state (Error state in the Dynamic Workload Console) and return the following exception in the job log:
AWKIPC005E Failed to run workflow.
Remote Exception
To enable the correct submission of plug-in jobs, after restarting the Hub, connect to the Informatica PowerCenter Web Services Hub URL and follow these steps:
In the Navigator pane, expand Web Service -> Batch WebService, and
then click Integration WebService
In the Operations pane, click Try-It from the toolbar
In the Web Service Operations avigator pane, click login.
Fill out the form in the right pane, pecifying the required
information in the UserName, RepositoryName, nd Password text
fields.
Click Send.
In the SOAP Response pane, copy the value for the SessionId tag.
In the Web Service Operations Navigator pane, click getWorkflowLog.
Paste the value copied previously in the SessionId text field and
then enter the required information in the FolderName, WorkflowName,
Timeout, and ServiceName text fields.
Click Send.
It should work.
Related
I have a project that has some connection managers configured. I deployed a package to the integration services server.
When I run this package on Visual Studio it runs fine. But when I try to execute this on the server it fails.
I get the following error msg:
"The runtime connection manager with the ID "aaa" cannot be found.
Verify that the connection manager collection has a connection manager with that ID.
How can I configure my connections on the server?
Thx
https://msdn.microsoft.com/en-us/library/ms140237.aspx
I believe this page contains the answer you are looking for. The SSIS designer has a "Connection Managers" area where you can edit the connection information.
In SSIS Designer, click the Control Flow tab, the Data Flow tab, or
the Event Handler tab to make the Connection Managers area available.
In our case, connections need to be at the package level, not the project level. There is an option to right-click on the connection and covert them to package level.
I'm creating a WebAPI that needs to authenticate against ADFS.
I am this lab but I keep running into a problem when I try have a client connect to it. I have setup the Web API on a test server and have provisioned a ADFS Client but every time I try to connect using a client I keep getting the following error window when the code runs the
This happens every time the following code is hit
AuthenticationResult ar = ac.AcquireToken(resourceURI, clientID, new Uri(returnURI));
I have no idea where or what is causing this any help would be appreciated.
Open the Event viewer in the box running ADFS (Window key-R: eventvwr.msc), and check the ADFS event log.
It should contain information about the error you are seeing. You can also enable debug logs. Right click the Admin node, select View and click 'Show Analytic and Debug logs'. Then open the 'AD FS Tracing' node, right click the Debug node and select 'Enable log'.
HTH
These are the steps I did under the administrator and farm account:
I go to central admin -> application management -> manage service applications
I click on New-> Business Data Connectivity Service
I enter/select the required fields like name, application pool, application pool identity and click on OK. After a while I see some text that my BDC is created succesfully.
No I see the list with all service applications. When I click on my created BDC service application I got this error:
Error An error occurred. Administrators, see the server log for more information.
Troubleshoot issues with Microsoft SharePoint Foundation.
Correlation ID: 27275209-7fc0-4912-9970-feba5356e9cc
Date and Time: 5/25/2013 9:19:41 PM
In the event viewer I see this error:
The BDC Service application BDC is not accessible. The full exception text is: Access is denied.
Why I get this error? I try it with the farm and administrator account. BUT I have selected another user account for the application pool for this BDC.
Make sure the 'Business Data Connectivity Service' is started under central admin -> application management -> Manage services on server.
Under central admin -> application management -> manage service applications, select your 'Business Data Connectivity Service', click on 'Administrator' in the ribbon, and add your current user in full control on the service. You should now be able to open it.
In IIS 7, I would click on "worker process" then "View Current Request" to see all the requests currently being executed.
http://technet.microsoft.com/en-us/library/cc732518(v=WS.10).aspx
In IIS 8, I do not see this option. Is there something I need to set up on IIS 8?
Edit: I tried running inetmgr as administrator as well.
There wasn't any UI hints, but was able to turn it on as a feature under server manager.
Server Manager -> Add Roles.
Web Server (IIS)
Web Server
Health and Diagnostics
Request Monitor
The required features can be installed with PowerShell.
IIS Manager:
Install-WindowsFeature Web-Mgmt-Tools
Request Monitor:
Install-WindowsFeature Web-Request-Monitor
With these features installed, run IIS Manager, browsing to the Worker Processes section shown in the screenshot below. From the list of Worker Processes, either double click on the process of interest to view currently executing requests or use the right-click context menu.
The back/forward arrows to the left of the address bar can be used to navigate back and forth between the list of requests and worker processes. The alt+left arrow / alt+right arrow keys perform the same actions.
I had to do this from an elevated command line
%windir%\system32\inetsrv\appcmd list requests
If you want to see requests exceeding more than 5 seconds
%windir%\system32\inetsrv\appcmd list requests /elapsed:5000
In a loop (assuming you are in %windir%\system32\inetsrv\
for /l %x in (,,) do (appcmd list requests /elapsed:5000 & timeout 2)
This show's the steps to install it. From https://portal.ektron.com/KB/10396/:
To run it after it's installed you will need to find the "Worker Process" icon on the server settings in IIS Manager.
Another good option with ASP.net is to go to task manager, right click on the process and select "Create Dump File" then download and double click on the created .dmp file to load it into Visual Studios debugger. Then look thru the threads and their call stacks to see where all the requests are being executed. This method allows you to see exactly what the requests are doing (infinite loops, deadlocks, etc.)
I installed and configured SQL Server 2005 with Reporting Services, Workgroup Edition on Windows 7. I have updated to Service Pack 4. The problem is that when I navigate to http://localhost/reports/Pages/Folder.aspx, Reporting Services don't show/display Contents or Properties menus, all I see is the SQL Server Reporting Services header with the Home/Help button.
EDIT: I figured it out. You need to create role assignments that explicitly grant you access together with full permissions. To do this, follow these steps:
Start Internet Explorer together with the Run as administrator option. To do this, click Start, click All Programs, right-click Internet Explorer, and then click Run as administrator.
Open Report Manager. By default, the Report Manager URL is http://ServerName/reports.
If you use SQL Server Express with Advanced Services SP2, the Report Manager URL is http://ServerName/reports$sqlexpress. If you use a named instance of Reporting Services, the Report Manager URL is http://ServerName/reports$InstanceName
In the Home dialog box, click Properties.
Click New Role Assignment.
Type a Windows user account name by using the following format:
Domain\User
Click to select the Content Manager check box.
Click OK.
In the Home dialog box, click Site Settings.
Click Configure site-wide security.
Click New Role Assignment.
Type a Windows user account by using the following format:
Domain\User
Click System Administrator.
Click OK.
Close Report Manager.
I figured it out. You need to create role assignments that explicitly grant you access together with full permissions. To do this, follow these steps: Start Internet Explorer together with the Run as administrator option. To do this, click Start, click All Programs, right-click Internet Explorer, and then click Run as administrator. Open Report Manager. By default, the Report Manager URL is http://ServerName/reports.
If you use SQL Server Express with Advanced Services SP2, the Report Manager URL is http://ServerName/reports$sqlexpress. If you use a named instance of Reporting Services, the Report Manager URL is http://ServerName/reports$InstanceName In the Home dialog box, click Properties. Click New Role Assignment. Type a Windows user account name by using the following format: Domain\User Click to select the Content Manager check box. Click OK. In the Home dialog box, click Site Settings. Click Configure site-wide security. Click New Role Assignment. Type a Windows user account by using the following format: Domain\User Click System Administrator. Click OK. Close Report Manager.