I want to stop the WebLogic managed server without giving admin URL and username and password while executing ./stopmanagedweblogic.sh Is there any way to create as stop script in which we can define admin URL and username and password and while stopping we have to just execute : ./stopmanagedweblogic.sh managed server name.
Related
I am trying to export the STARTLAYOUT.XML file from Windows 10 computer. I issue the following command in Powershell which is logged in as a local admin user.
Powershell Admin
I enter the local admin username and password
Run the command >Export-Startlayout c:\startlayout.xml
Error
Export-Startlayout: A specified logon session does not exist. It may already have been terminated.
At line1 Char1
Any ideas guys. I have not had issues like this before. These are Autopilot Intune joined AAD devices.
I downloaded Oracle 12c from website and installed it. In gave Sys password as "admin", all the setup was done successfully.
now, on the command prompt, i issue the following commands..
SQLPlus /nolog
I get the SQL>
i then say "connect sys/nimda#orcl as sysdba and it gets connected successfully.
I try to connect to 12c will all sorts of invalid passwords and it still works.
Funny, isn't it?
When you log on to the database server and that user is member of the operating system's DBA group, then - when connecting to that (local) database - you're authenticated at the operating system level and you can connect just as you tried it - with an invalid password.
You could also try, for example, sqlplus littlefoot/mukesh as sysdba, and it should work.
I am trying to link two SQL Servers (2008R2 and 2014) which are running in two separate (!) Active Directory domains.
The problem is that I can login into the remote server only with a Windows Account from the remote domain. So the challenge is to pass on the credentials to the remote server, but here I am stuck.
Local Domain (local network infrastructure): dom8, Server: dom8\sql2008, SQL (!) Login: localuser
Remote Domain (Microsoft Azure): dom14, Server: dom14\sql20148, Windows (!) Login: dom14\import
Server dom8\sql2008 wants to connect to dom14\sql2014 in order to pull some data.
Here is what I have tried on the local server: (logged into dom8\sql2008 as sa) :
-- Create a credential for the remote Windows login:
create credential cred_import WITH IDENTITY= 'dom14\user14',
SECRET = 'password' ;
-- Alter the local SQL login and add the created credential:
alter login local_user with credential = cred_import ;
-- Create the Linked Server entry:
exec sp_addlinkedserver
#server='dom14\sql2014',
#srvproduct='SQL Server'
-- Add the credential to the linked server:
exec sp_addlinkedsrvlogin
#rmtsrvname ='dom14\sql2014',
#useself = 'FALSE',
#locallogin=local_user,
#rmtuser = [cred_import], -- trying to pass on the credential
#rmtpassword = NULL
However, it does not work. Whenever user localuser tries to connect to the remote server through the local server, then it gets an error login failed.
By the way, I can connect to the remote domain by using SQL Server Studio as follows:
runas /netonly /user:dom14\user14 "C:\...\Ssms.exe"
So obviously I can create a credential of the remote side on the local side. Only a remote server link does not work.
You will need a trust between the two domains in order to log into a domain A machine with a domain B password.
Once the trust is in place, you can then go to the domain A machine and grant permissions to the domain B user ID the permissions needed to do what your wanting to do.
However, it looks more like your trying to use local accounts, not domain accounts based on your script. I suspect the way you have the domain referenced, versus the server it's self may be the cause.
Looking at lines:
-- Create a credential for the remote Windows login:
create credential cred_import WITH IDENTITY= 'dom14\user14',
SECRET = 'password' ;
Is DOM14 the name of your domain? Or the name of the server your trying to connect to?
exec sp_addlinkedserver
#server='dom14\sql2014',
#srvproduct='SQL Server'
A server in another domain would be XYZ.DOMAIN.COM where XYZ is the actual server name, and domain.com is the domain that server is in. Also, you will need to make sure the server has access to read the other domains DNS tables.
From server A, you should be able to go to a CMD prompt and ping the other server by name (FQDN may be needed depending on Suffix Search list). Not concerned if the ping fails, as long as the IP address for the server is returned. If you don't get an IP address back, you have a more basic problem of name resolution between domains (you may need a forwarder in Domain A's DNS server pointing Domain B's name to a DNS server in Domain B), and vice versa (A to B, B to A, etc).
I have Netbeans 7.4 & GlassFish Server 4.0, I've accidently removed the password in server properties..
now everytime I start Netbeans a message box pops up saying
Authorization failed while checking GlassFish Server status, Please provide valid administrator credentials
and it asks me for username and password
the password seemed to be auto-generated, I've tried to login with admin and leave the password blank or admin as a password, it didn't work.
I also tried to permanently remove and re download it again in Netbeans, I got the same issue.
as per http://it.i88.ca/2012/07/glassfish-3-solution-recovery-admin.html
you can change the content of glassfish/domains/domain1/config/admin-keyfile to
admin;{SSHA256}dvCEGFNHGtSyXIhJvwR5FnviH+u8fCadrUIqp6uJc1tP9Bv10CGT7A==;asadmin
and your asadmin password is now "changeit".
After installing the standard Tryton packages in Ubuntu 12.04, I can start the client and create a new database. But the client refuses to connect to the database. It will display the locally created databases, but will fail to add the localhost profile.
If I try to add a new profile, the client will show the installed databases, but on clicking ok will fail silently back to the start screen, without adding the new profile.
New profile setting was:
Hostname: localhost
Port: 8000
Database: [Correctly displays the list of created Dbs]
Username: [I've tried everything from tryton, admin, test to root]
I have also tried to connect directly in the Tryton client without adding a new profile, then it will always yield "Bad user or password", no matter how exact I re-enter the tryton user with his password, or any other user (admin, root) for that matter.
I have followed the procedure in the documentation (Readme.debian: adding database user in /etc/trytond.conf and so forth, have registered tryton user with postgres and in trytond.conf).
Do I need to be logged in as tryton on Remote Desktop maybe?
The client was started on the Ubuntu desktop via Remote Desktop, logged in as root.
Tried to log in as tryton, too. That will get to the desktop, but somehow not show the Terminal window. Hence I can't start the Tryton client. Terminal will blink for a second and then vanish.
When you create a dabatase from the tryton client it ask you the admin password. You must enter with the 'admin' username and with the admin password you used on the database creation step.
Once you enter the system you will see and step to create additional User. You can skip it if you want, as they can be created at any time from Administration -> Users -> Users menú.
You must never use the passwords entered on etc/trytond.conf as this credentials are used from the tryton server to conect to the database. User logins are managed by tryton server.