Is it possible to mount the NVME drive of an C5d instance in an Amazon Sagemaker Studio notebook? I can see the drive under 'lsblk' but am not allowed to format or mount it. The drive is also not visible in the '/dev' folder. I tried this with a regular C5d EC2 instance and there it works without any issue.
Edit: I tested it with Sagemaker Notebooks, not Studio, and it also works. It seems Studio doesn't have real access to the underlying infrastructure.
Kind regards
Related
Good morning. I recently installed Windows Server 2019 on Google Cloud Compute Engine and in there I installed a copy of 5 user copy SAGE 50 Premium 2020. I have given the server a static IP, and I have shared the Peachtree/Company folder on the Windows Server 2019, but I don't know how to access this shared folder from my Laptop or other desktops in the office. The local Sage installations in the office require access to this folder that is on the Windows Server, on the Compute Engine.
I read in some places that we require a VPN but even that I'm not sure how to set up withing the cloud.
Yes, you can connect your on-premises network with your cloud VM via VPN tunnel and then you'll be able to use windows sharing options.
Have a look at Google Cloud VPN. Also, you can check available option at Marketplace using keyword VPN in case you prefer or more familiar with other VPN solutions like OpenVPN. Don't forget to setup your firewall and routing options accordingly to the documentation of selected VPN.
I'm running an MS Access database with VBA code that has libraries for Microsoft Office 2010. Currently, there are users that are upgrading their machine to Windows 10 running Access 2016.
When the database is opened on a new machine running Access 2016 the libraries for the Outlook changes to 16.0.
When I try to open the file in the old Access 2010 environment, I run into this error:
Missing msoutl.olb.
Is there a way to make the database backwards compatible?
It sounds like the users share the same frontend hosted in a network folder.
If not done already, split the database to have a single shared backend database file. Then, to avoid your issue, distribute a separate copy of the frontend to each user's workstation.
On the workstation, let the user launch the frontend using a shortcut that runs a script to always keep the frontend current. This method is described in detail in my article:
Deploy and update a Microsoft Access application with one click
I am unsure about how to best resolve this issue. I have been working on a MVC application that requires user authentication, so I set up the project to use individual accounts, all well and good, it works fine.
However it saves the account data into a local db instance. I am at the stage where I want to host the application on a amazon web server I am renting. Publishing it to here has been fine, but now it can't connect to the local db so the sign up / register is no longer working.
My question is, can I somehow take this local db with me to the server, or do I need to generate a SQL script from it and deploy it on a local instance of SQL Express, and if so, how? I have had no luck with my attempts at either and would greatly appreciate any help.
Thank you.
I've never done this as Local DB is not recommended for anything in production so I'm not sure if it's allowed in AWS. In Visual Studio at the top of the solution explorer window there is a button to "Show all files" you should then see the hidden MDF local db file within the App_Data folder. Ensure that this file is being published to AWS.
I have installed IBM Rational Application Developer version 9.1 from the installation media. The media launches and installs the IBM Installation manager and I've selected the RAD 9.1 package for install. Among the options, I've requested that the "WebSphere Application Server v8.5" be installed, as well as the "WebSphere Portal Server v8.5" and all the options underneath.
Once I launch RAD, I go to the server tab (as instructed by the IBM Portal Developer course) and attempt to create a new WebSphere Portal server. The server wizard wants to know where the installation directory of the server runtimes are located for both WAS 8.5 and Portal 8.5.
For WAS this is simple, I point to the profile "AppSrv01" at the following location:
C:\Program Files\IBM\SDP\runtimes\base_v85_stub\profiles\AppSrv01
For the Portal Server, I assume there would be a default profile created, but there is not. There are several directories inside the stub directory, but no profiles. The best I can do is provide the following location:
C:\Program Files\IBM\SDP\runtimes\portal_v85_stub
Seems straightforward right? It complains of the following problem:
The Portal Server installation directory is not correct
Am I missing something here? Are there fix packs I need? Is the portal server runtime included with RAD 9.1 not enough to create and use a local portal server? DO I need to simply create a profile and if so where is the tool needed to do so? (I really really wish someone from IBM would explain this to me and how I am supposed to be indicated to the correct course of action)
IBM is, as usual, being very straightforward and easy to use/understand. Does anyone have any ideas about how I am supposed to proceed? The IBM Developer course that was bought and paid for assumes this step already and before you suggest it, yes I've already sent and am awaiting a response from the organization I am taking the course from.
Not sure I'm getting your description right. From what I can see, you installed RAD using IM from a media. Also, you selected WebSphere Application Server development tools and all underneath it as well as WebSphere Portal development tools.
These development tools options are stubs only, not the actual servers. With this I mean that they're useful for development and compiling purposes only, but not for deployment and testing because they are not the actual servers.
Here is the part that I don't understand. In the media that has IM and RAD, does it also have WebSphere Application Server and Portal Server available for installation? If not, then you need to get them and install them and then your can create the servers pointing to the install location of both servers in RAD. Once you do this, you can use RAD to create the profiles.
Hope this helps.
A few things, Install portal by itself and DO NOT install to a C:\Program Files make it something short like c:\IBM\WebSphere
it sounds like only portal stub got installed, did you have the portal media available as well.
If you install it using the same installation manager, RAD will be able to find it
How can I deploy Access applications to multiple companies, with linked tables to SQL Azure servers?
I'm planning to deploy the Access programs with Microsoft Access runtime, and I'm assuming that I'll need to include the odbc drivers as well? Is there a way to automatically have Azure create a new server when a company signs into my website and downloads a program, and have the Access program link to it? And is there a way to get around the IP address settings in Azure as well? Because companies will be using the programs on multiple PCs. Or is it possible to utilise that and charge per PC?
If you distribute the application pre-linked, then the user should not have to do anything to consume the data.
When using Access with SQL server you can in general use the standard windows built in SQL driver. However in the case of Azure you do need to download + install the native 11 drivers (so I recommend you use that driver during development and setup).
You can also have code include to re-link to the sql server, but as noted, if your application is “already” linked, then you really don’t have to do anything on application startup. Such re-linking would not be required every time the application starts, but only a “one time” re-link is required say if you’re going to change the database, or perhaps the user logon. How to re-link (DSN less) is outlined here:
http://www.accessmvp.com/DJSteele/DSNLessLinks.html
As noted, you really don’t need the above.
As for IP restrictions, in the Azure setup you can turn off such restrictions if you need a connection that will occur from any location, but that does open up a security hole. (when you first create the SQL database you will be prompted for firewall rules).
All of the above assumes you been developing that Access application with SQL server as the back end (you can even use the free edition of SQL express for development on your local machine).
Last but not least:
Because your connection is occurring OVER the internet, then you speed will be MANY times slower then using a local server. Read the following article to get a “grasp” of this speed difference:
http://www.kallal.ca//Wan/Wans.html
So MUCH additional work is required in Access to obtain good performance when your connection is OVER the internet as opposed to SQL server running on your local network.