we are using SSIS 2016 and with parameterize connections. Every time we open the solution the connection manager is trying to connect with the credentials available in the project.param , due to unavailability of the password and repeated trying the db user account is getting locked.
Looking for some inputs if there is any settings we could change for connection manager not to try to connect when the solution is opened.
Thanks for your time on this.
RR
If you change the project setting to work in Offline mode, you should be able to open the project without validation checks firing which should alleviate the ever-so-fun lockout policy. That might be a user solution file setting so each team member might need to set it.
A different approach is to leave the design time user value to a non existent account. The run-time will swap in the properly parameterized connection but any developer opening the packages won't lock anyone out.
Related
I have three Access database MDB files with various tables I need to upsize to SQLServer. I need to be able to update the data regularly. I am using an SSIS package in Visual Studio. I have it set to use the 32 bit version for this project. I have one of the databases running just fine. Using the same techniques on the next database I create an OleDb connection manager using the Access 16 connection and the connection tests fine, I drop down the tables drop down and it finds the table names just fine. I pick a table and hit ok and it comes back with:
Exception from HRESULT:OxC0202038
I got these databases from another source. Two of the three were set without security. Being older MDB's they have the ability to have user level security. The table in question was in the one database that had security set to admin only. The deceiving part is that the oledb connection could find the table names at all with security set so I should not be able to read them. The ambiguity of the error message was not all that helpful either. But, once I reset the user level security to allow full access things worked fine.
I would like to find a way to let Access crash in such a way that when you re-open the database, you will get this popup message:
'The last time you opened "....accdb", it caused a serious error. Do you still want to open it?'
Reason for this that have to maintain a server with a lot of cronjobs that launch even more Access applications, and sometimes it happens that a crashed Access application cannot be launched anymore due to this popup which prevents opening the database until you click 'Yes'.
To test my solution (remove registry key HKCU\Software\Microsoft\Office\XX.0\Access\Resiliency\DisabledItems), I need to have an access database that crashes on request.
Is there a way to do this with a vba script?
Write a script that kills the running process.
I have set up a SQL Reporting Services-server on a couple of VMs running on a physical server and I have encountered a strange problem. While setting up a subscription to a report the owner name will appear as expected, COMPUTER_NAME\USER_NAME but when editing the same subscription the domain name will have changed to something like WIN-XXXXXXXXX\USER_NAME. When setting up SSRS on other VMs running on the same physical computer the same happens, with the domain name being replaced with the same thing. It seems that somehow SSRS replaces the domain name with the name of the physical machine.
The VM itself is not on the domain, having only local administrator accounts which is the one owning the subscription. The account has been set up in SSRS with the appropriate permissions. The vm has not changed name since installing SSRS.
The problem is that SSRS won't recognize the new name so the scheduled reports won't run and I can't edit the schedules. After searching online I could only find one other person with the same problem and unfortunately no solution was suggested. Is there any way I force SSRS to use the machine name of the vm instead of the physical machine? Or if there's a workaround to the issue entirely?
I bet your SSRS instance lives in a separate VM than your web application and is not set up under the same domain. As a workaround could you test this with mixed mode authentication and a local user account named 'LocalReportSubscriptionCreatorAccount'.
UPDATE
Subscriptions
SET
OwnerID = 'LocalReportSubscriptionCreatorAccount'
Figured out a fix: It seems that only one user was affected by this weird behavior, creating a new user and adding it to the administrator-group worked.
Update: I ran a SQL connection test function in my VBA and it reads open from my main workstation, I ran the same connection script at the client workstation and Runtime crashed. I also checked to make sure it was using a 32-bit rather than 62-bit driver and that the credentials were identical to another station that does work.If I run a connection test Runtime crashes, if I try to only run the query it says the connection can't be found. Both attempted from the user computer.
I successfully opened an ODBC Unicode connection to the MySQL database from the client computer at System DSN level. When I open the Access Runtime file and try to use a form to query the database I receive the error: "ODBC--connection to 'servername' failed." I have tried numerous names including changing the case sensitivity. I verified that the TCPIP address I used was indeed to the host for this database, and that the name using ipconfig /all - was of the appropriate case sensitivity. I have not been able to figure out if it is an issue with Access vs. Runtime, but I can't really see that being the problem here. The name of the table is "tbl_panel," and it is definitely within the database I connected to with ODBC with that exact name. The user requirements for the connection I used has basically "Read-Only" privilege, but that is all it should need as I am only checking the data. Unless creating a recordset is beyond the scope of SELECT, SHOW VIEW, CREATE TEMP TABLES. Furthermore, the fact that it can't find the server itself tells me its probably not to do with my SQL/VBA coding. Hovering over the tbl_panel in the Navigation Pane of Access shows "ODBC;DSN='servername';;TABLE=tbl_panel".
Here is the SQL string for creating the record set (truncated for space since the statement itself works fine):
stSQL1 = "SELECT tbl_panel.PNL_SN_ID FROM tbl_panel " & _ etc.
Set qryList = dbsInspect.OpenRecordset(stSQL1)
This has me pretty stumped, and I am a rookie when it comes to ODBC, so if it is something obvious please be kind. I did do a lot of searching, but most ODBC queries return issues with the initial setting up of the Data Source, or opening the connection in code. Is that a possibly for what I have to do? Include an opening statement for the table in VBA so that Runtime knows what to do? I'm going to feel silly if that is what the problem likely is and I typed all this for nothing.
This ended up being a bit issue. Despite using the ODBC connection tool in Control Panel --> Administrative Tools. I needed a 32 bit connection. This is answered in another SO question.
HOWEVER, I will note that the only way I ended up getting an useful error message was by creating a backend. Then it displayed the error message in the linked question below:
Related Question on SO
I have an issue. I have an Access Project (currently in access 2007), and the project connection properties are set to point to a hosted SQL database on our network. Unfortunately we had to move the databasem and now I have to change the connection properties as well.
However, when I open the adp file, the first thing it does is try to connect to the old database. I never get prompted or anything, the screen just sits there, and the title bar eventually indicates "not responding".
Anyone know how I can get to the connection properties, since Access never gives me a chance to do so?
Have you tried keeping the shift key held down while the database is opening to prevent any start-up forms or macros from running? If that does not help, you can change all the connections from VBScript.