9iASAgent fails after computer name change

Hi,
I has 9iAS and 8i installed and working on one machine. Then I had to change the server name including the domain etc. Now the 9iASAgent service fails at reboot and would not run afterward. Any remedies to this problems ???
KI

Hi,
We are looking into this issue. In the mean time deactivate the license before modifying any of the system information.
If you are facing the activation issue, please contact [email protected] with OrderId & Serial#
Thanks,
M7 Support

Similar Messages

EM not working Properly after computer name change

Hi Friends,
i hav 10gr2 DB, everything was fine.
last week my computer name changed, and EM stops to work.
so i reconfigure EM through command line.
after that EM started, but when go to 'Performance' or any other tab in browser.
its asks for login and shows 'oldcomputername:orcl:1521' in connection string.
so whats other things , i hav to change?
Thanks

Search every file under $ORACLE_BASE for the old name.
Assuming *NIX use find and grep.
Why do people rename servers? A name is a name is a name. All it ever does is cause problems.

Authentication popups after computer name changed to computer record name

Hi
I'm not sure if anyone else is facing this issue, but I have been unable to find anything in the forums.
I have setup a number of client machines on Lion Server, all using 10.7.4. I used WGM and Remote Desktop to make some changes and deploy software
Since then, I have been getting the following authentication popup on all client machines (twice after login, and then every 30 mins or so afterwards):
Mac OS S wants to make changes. Type an administrator's name and password to allow this.
The changes made prior to this happening were:
- Overplay VPN installed (using RD pkg install)
- Adobe CS 5.5 installed (using Adobe Enterprise Deployment Tool and RD package install)
- Evernote installed (using RD copy)
- Set computer name to computer record name (From WGM > Computer Groups > Preferences > Options)
I have now removed all the installed software from one machine, and log in as administrator, unbind the machine, rename the computer manually to the record name, rebind the computer.
As far as I can see, I have reverted all changes one at a time, and am still receiving the admin password requests when logged in as a network user.
The only machine that seems to be ok, is the one where the name change to computer record name was unsuccessful.
Does anyone have any suggestions as to how I can fix this issue?
Thanks
Suraj

Issue resolved. It turns out none of my changes caused the issue as much as Google Chrome Autoupdates. The new version constantly checks for updates which makes clients on Lion Server go haywire. Solution to turn off auto-updating:
Open a Terminal window:
defaults write com.google.Keystone.Agent checkInterval 0
Relaunch Chrome.

MSA Conntrans fails after machine name change

Hi
I have 5 remote laptops that have had their name changed and conntrans will no longer work.
When I ran SELECT @@SERVERNAME on database it retunred old name so I then ran
sp_dropserver 'oldname'
sp_addserver 'newname' , local
Stop / start SQL server
SELECT @@SERVERNAME now returns new name . However Conntrans still failing. Is the machine name embedded anywhere else ?
The mobile application does open it appears to be just the conntrans process that will not function.
Has anyone done this before ? Is it possible ?
Best Regards M

Hi Melita,
Please check note 1253027. This should solve your problem.
regards
Vivek

NitroX license disabled after computer name change

Hi,
We had to change the network names on several windows development machines containing the Nitrox environment.
After that change Nitrox wouldn't want to start on any of these boxes, failing to reactivate the license ("No activations left for this serial number").
That's certainly caused by Nitrox not recognising the machine it's installed on anymore.
What should we do now ? If only we had access to an admin console where we can control our own licenses it would be so simple.
Thanks in advance,
C dric Paternotte
SITEL Fribourg - Switzerland
Order Id INT001-5576
Nitrox 2.1.0M3 build 419, Eclipse 3.1.0, Windows XP SP2

Hi,
We are looking into this issue. In the mean time deactivate the license before modifying any of the system information.
If you are facing the activation issue, please contact [email protected] with OrderId & Serial#
Thanks,
M7 Support

Random characters after computer name

Hello,
We have a new issue with our agent deployment since we use MDT to deploy our workstations.
When computer register to ZCM some random characters appear after computer name, for example:
Computer name: corporate001
ZCM computer name: corporate001-741132927c2e6f41b5569a9f9409b983
Do you have an explaination?
ZCM Agent is automatically installed after deployment through a .vbs script.
cscript ZCMscript.vbs
Code:
Set objShell = CreateObject("Shell.Application")
objShell.ShellExecute "PreAgentPkg_AgentCompleteDotNet.exe", "-q " & "-x"
strComputer = "." ' local computer
strProcess = "Setup.exe"
Do Until isProcessRunning(strComputer,strProcess)
WScript.Sleep(5000)
Loop
Do While isProcessRunning(strComputer,strProcess)
WScript.Sleep(5000)
Loop
WScript.Quit 0
' Function to check if a process is running
FUNCTION isProcessRunning(BYVAL strComputer,BYVAL strProcessName)
DIM objWMIService, strWMIQuery
strWMIQuery = "Select * from Win32_Process where name like '" & strProcessName & "'"
SET objWMIService = GETOBJECT("winmgmts:" _
& "{impersonationLevel=impersonate}!\\" _
& strComputer & "\root\cimv2")
IF objWMIService.ExecQuery(strWMIQuery).Count > 0 THEN
isProcessRunning = TRUE
ELSE
isProcessRunning = FALSE
END IF
END FUNCTION

Yes, the random number is the "Device GUID".
In your Example there would already be a device called "corporate001" in your zone.
The GUID is added since there cannot be two devices with the same name.
There are reconciliation rules that determine "matches".
Most likely, your rules rely upon MAC and/or SN and this changed instead of relying upon Workstation Name.
No one way is "Correct".
It really comes down to what works for you.
Most likely a tweak of the rules to rely more upon "Workstation Name" may work best for you since I suspect your devices are in a domain if using MDT, which means the names are unique.

Computer name changes incrementally (1, 2, 3...)

Dear Apple Friends,
I have an issue that is affecting all the Macs on my home network: 3 MacBooks (wireless) and an iMac (hardwired) connected to an Apple Airport Extreme dual-band 802.11n/a/b/g 5Ghz/2Ghz wireless router. All the Macs are running Yosemite 10.10, I am running firmware v7.6.4 on the Airport (latest version). We have turned on Back to my Mac, File Sharing, and Screen Sharing (all are used pretty regularly) in the Sharing screen.
So here is what is happening...
All the Macs on our network are having their computer names changed with the suffix of (1), (2), all the way to 6 now.
I have tried resetting our Airport router (turn off/on again) and that seems to stop it for a day but then it starts again.
A few days ago, I did a factory reset on the Airport router per the instructions on the Apple website (hold down reset until it blinks constantly) to clear the router. Sure enough, the names started changing again after about a day.
Sometimes, I will change the name back, and it will rename itself again automatically right after I change it. i.e. John's MacBook Pro => John's MacBook Pro (1)
I have gone so far as to reboot every Mac on the network, shutting off the router, then turning it on again, and the issue returns. I am going to try and set up a DHCP reservation next and see if that helps.
Has anyone else run across this? If so, is this a bug or is there something I'm missing here? Thanks you for your time.

To "fix" I:
First, I turned off networking which was WiFi in my circumstance.
Next, I named my computer back to the original desired name in the "Sharing" system preference without the (n).
Then I added a "--no-namechange" parameter in the /System/Library/LaunchDaemons/com.apple.discoveryd.plist.
Unloaded and loaded the deamon:
sudo launchctl unload -w /System/Library/LaunchDaemons/com.apple.discoveryd.plist
sudo launchctl load -w /System/Library/LaunchDaemons/com.apple.discoveryd.plist
Last, I reconnected to the network.
Now when I connect to the network instead of getting something like below in the Console.app:
"discoveryd: Basic Bonjour Changing computer name from <hostname> to <hostname> (2)"
This appears in the Console.app:
"discoveryd: Basic Bonjour Would have changed computer name from <hostname> to <hostname> (2), but it's disabled"
I could not find a Yosemite bug filed https://bugreport.apple.com/, but this site helped me hack my solution:
http://www.insanelymac.com/forum/topic/301118-computer-name-changing-constantly- two-or-one-network-interfaces-enabled

How can I configure EM after machine name changed?

Dear all,
How can I configure EM after machine name changed?
Thanks in advance.

You can change it for Management Agents, but you need to re-install OMS if the hostname for the OMS host has changed.

Computer name changes after security update

We installed the latest security update for OS X 10.5.8 and after installation the computer name was automatically changed. It was "Name (2)". After the update it magically became "Name (3)". It becomes very confusing because we share this computer's printer with a Macbook and it can't find the shared printer after this happens. Is this normal? It has happened after two security updates.

This is how it SHOULD be. When you try to rename a Mac in a LAN to a Computer Name which is already given to another Mac in the LAN, Mac OS X will suggest to add a number to the name you tried. When you rename the Mac to this Computer Name before you connect to the LAN Mac OS X will add the number automatically.
But the problem this thread is about (imho) is that Macs with UNIQUE Computer Names in the LAN, unexpectedly add a number, when there is for sure no other computer with that exact name in the LAN.
I can witness this behavior round about two to three times in a month in our network of over one hundred Macs.
By the way: Not only the Computer Name will change but the Local Hostname too.
Computer Name: "Example Name" -> "Example Name (2)"
Local Hostname: "Example-Name.local" -> "Example-Name-2.local"
This looks more like a bug in the system than an operating error.
Any suggestions anyone?

Computer name change after migration

I did a software migration from my macbook to my new iMac. Everything went great except the migration named the new iMac "macbook", the name I used on the macbook. I went to system pref. and did the name change to iMac24 and that works fine for sharing on the local network. However, on the Finder the name of the new computer at Home is still "Macbook", the migrated name. Kinda confusing when looking at the Finder pane, two Macbooks show up, one under shared and one under places.
Also tried to change the name of the Home at the Mac HD but was told couldn't be done.
Is there anyway to change the name of the Home file or am I stuck with Macbook as the name for my iMac?

imagesbytjm wrote:
I did a software migration from my macbook to my new iMac. Everything went great except the migration named the new iMac "macbook", the name I used on the macbook. I went to system pref. and did the name change to iMac24 and that works fine for sharing on the local network. However, on the Finder the name of the new computer at Home is still "Macbook", the migrated name. Kinda confusing when looking at the Finder pane, two Macbooks show up, one under shared and one under places.
Also tried to change the name of the Home at the Mac HD but was told couldn't be done.
Is there anyway to change the name of the Home file or am I stuck with Macbook as the name for my iMac?
The Home name I presume is your "short" name.
You can change the short name in Accounts by unlocking the padlock and right-clicking the Account and selecting Advanced Options.
Pleased note the Warning and the required reboot.
I suggest being sure your backup is up-to-date before changing the short name.

Time Machine and computer name change

I just recently reinstalled the operator system after a computer crash when i did so changed the computer name and now when i go into time machine to restore the settings it only shows up as one sparse disc image.
i have found that when i can mount it manually but the files are not usable and when i mount it with time machine the history does not appear.

Go to System Preferences - Sharing and change the computer name there. You can also, optionally, change the name of your hard drive to further clarify the origin of your backups. Click once on the "Macintosh HD" on your desktop, then click its name to allow you to edit it.
Matt

Computer name change and Network name

Recently I changed my computer name from "XY Z's Computer" to one without the dreaded apostrophe and the spaces.
I did this in Sharing under Computer Name:
However, after doing this and rebooting, the new name is there - good - but if in Sharing Preferences, I click Internet Sharing and then click Airport Options, my original name is there, under the title, Network name:
Is there a single location where these changes can be made simultaneously?
Are there any other places where one might find the original computer name?
Is this a bug or simply something not well-documented that I should have known about?

i'd like to know how to do this also

Computer Name changes

I am moving a computer to a new use and need to change the computer name. After reformatting the hard drive and installing OSX and running all updates I was surprised to see the original computer name in the Sharing preference pane. So I changed it to its new name and when I rebooted it was back to the original. I have zapped the P-Ram and reset the logic board and just about everything I can think of including turning Sharing both on and off.
It just keeps changing back to the original name.
G4 500DP Mac OS X (10.4.9)

Hello! Read THIS to understand open firmware passwords. Tom

Computer Name changes when waking from sleep

Hi,
I'm running OS X Lion Server on a Mac Mini 2ghz Core 2 Duo and every time it wakes from sleep I get a message saying "There is already a computer on the network named MacServer, renaming to MacServer (2)".
It only happens when waking from sleep. If I reboot or use the mini for hours without sleeping it's fine, but once it's gone to sleep it renames on wake. When it sleeps overnight it's named MacServer (5) by the morning, as it wakes up every two hours or so to re-register itself on the network and each time it renames itself.
I don't have any other compters on the network with the same name. The only other computer is a MBP and has a completly different name.
Here's my setup;
My Mac Mini is wired via ethernet to a Time Capsule. AirPort is turned off (I've tried on and off).
My Mac Mini has a static IP address (x.x.x.40) with DHCP for everything else (DNS, etc.)
The Time Capsule is wired to an ADSL router via ethernet.
The ADSL router manages DHCP and NAT, with IP pool x.x.x.2 through x.x.x.30.
DHCP and NAT are turned off on the Time Capsule (bridged mode).
Wireless is turned off on the ADSL router.
Time Capsule is handling wireless.
I've tried resetting the ADSL router. I've tried resetting the Time Capsule (to factory defaults).
The problem seems to be with mDNSResponder, as the log seems to suggest that it is this daemon that thinks there's a duplicate computer name. I've even looked at the source code for mDNSResponder and the last mod-log entry suggests that a fix was put in for this issue in 2009. It doesn't look like it's fixed it, though.
I've tried doing a fresh install of OS Server several times now and, after the last install, it started happening before I got a chance to restore from a Time Machine backup. i.e. on a completly fresh install and assigning a completely new computer name.
Can anyone help me on this issue? It's driving me insane!

I switched the server's WI-FI off and connected the ethernet cable to the ADSL router instead of the Time Capsule and, after several reboots, sleeps and wakes, there was no change to the server name. The Time Capsule was still switched on, connected to the ADSL router via ethernet, and available on the network, however the server rename issue went away.
I then took the ethernet cable out of the ADSL router, plugged it back into the Time Capssule, put it to sleep, woke it up, and guess what? That right; 'The name of your computer "safserver" is already...renamed to "safserver (2)"'
So, it looks like it's the Time Capsule. I'm going to downgrade the firmware from 7.6.1 to 7.6.0 to see if the last update is responsible. If this doesn't cure it, I'll try older firmwares and, if none of them work it's time for a Genius appointment.
(I khow another obvious question lurks: "why not leave it plugged into the ADSL router?" Answer: "ADSL router doesn't supply Gigabit ethernet.")

Computer Name changed to MINWINPC

We have about 200 computers that show their computer name as "MINWINPC". Doing an "ipconfig /all" shows the original computer name but doing a "net user" shows the computer name as "MINWINPC". In the control panel applet - the original computer shows but
the registry key: HKLM\System\CurrentControlSet\Control\ComputerName\ComputerName shows as "MINWINPC". Users can still access the network but administrators are unable to remotely access those machines. The fix appears to be as simple as changing the registry
key back to the original computer name(and rebooting) but I would like to figure out what is causing the issue. Some of the machines seem to have the name change occur after they have received the latest round of patches from Microsoft after the reboot.
It is not happening to all our Vista machines. I have changed the computer name back the original, uninstalled all updates from the day of the name change and resintalled the patches but have been unsuccessful in recreating the problem. Any thoughts?

I know this is an old thread but a new patch is causing the same issue MS13-098. The only Microsoft submission I have found is in Japanese and is translated as follows:
Phenomenon
In Windows Server 2008 or Windows Vista, you might not be able to log an error appears to apply the new update the following programs, if you try to log on after the restart. • MS12-024 (KB2653956)
• MS13-098 (KB2893294)
Error message displayed is as follows.
Incorrect password or user name
Back to the top | feedback
Collapse image Cause
This behavior occurs when you apply the update KB2653956 in the state of some data is damaged following registry key, or does not exist.
HKEY_LOCAL_MACHINE \ SCHEMA \ wcm :/ / Microsoft-Windows-CoreOS? ...
Any string will contain the part of the ... Note:. Also, make sure to load the SystemRoot% \ system32 \ SMI \ Store \ Machine \ SCHEMA.DAT file% if the HKEY_LOCAL_MACHINE \ SCHEMA does not exist.
When you apply the update of KB2653956 in the state where the registry key is not present, the value of the following registry is changed to MINWINPC, logon will not be able to.
• HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Control \ ComputerName \ ActiveComputerName
• HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Control \ ComputerName \ ComputerName
Back to the top | feedback
Collapse image Solution
If this occurs, change to the correct computer name the value of the ComputerName registry and ActiveComputerName start in safe mode, has been mentioned above, and then restart.
Back to the top | feedback
Collapse image Workaround
To prevent this phenomenon occurs, you download and run the System Update Readiness Tool from the following KB.
http://support.microsoft.com/kb/947821
By performing the system update Preparation tool registry that is described in Section Symptoms are repaired.
If the repair is made, starting with log Recreated missing key as the following WinDir% \ Logs \ CBS \ CheckSUR.log file% is recorded.
Recreated missing key:? Wcm :/ / Microsoft-Windows-CoreOS ... \ metadata \ elements \ ComputerName
In addition, regardless of the presence or absence of entry damaged Microsoft-Windows-CoreOS, you can set the value of the ComputerName key in this tool. For this reason, the following log is recorded in the CheckSUR.log.
Recreated value: @ _type.
Recreated value: @ dataOnly.
Recreated value: @ default.
Recreated value: @ description.
Recreated value: @ displayName.
Recreated value: @ handler.
Recreated value: @ legacyName.
Recreated value: @ legacyType.
Recreated value: @ migrate.
Recreated value: @ scope.
Recreated value: @ xsd: type.
Back to the top | feedback
Note: This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. It contains information in response to emerging issues are listed. As a result of the speed of information provided may be typographical
errors are included in the article, you might be revised at any time without prior notice. For other considerations, and use conditions
Please refer to.
Back to the top | feedback
Collapse image Property
December 11, 2013 - Revision: - Last Review: 2901584: 4.0 Document Number
This document that was written about products for.
• Windows Vista Business
• Windows Vista Business 64-bit edition
• Windows Vista Enterprise
• Windows Vista Enterprise 64-bit edition
• Windows Vista Home Basic
• Windows Vista Home Basic 64-bit edition
• Windows Vista Home Premium
• Windows Vista Home Premium 64-bit edition
• Windows Vista Starter
• Windows Vista Ultimate
• Windows Vista Ultimate 64-bit edition
• Windows Server 2008 Datacenter
• Windows Server 2008 Datacenter without Hyper-V
• Windows Server 2008 Enterprise
• Windows Server 2008 Enterprise without Hyper-V
• Windows Server 2008 for Itanium-Based Systems
• Windows Server 2008 Foundation
• Windows Server 2008 Standard
• Windows Server 2008 Standard without Hyper-V
• Windows Web Server 2008
• Windows HPC Server 2008
• Windows Essential Business Server 2008
Hopefully Microsoft will get this on the MS13-098 Bulletin immediately which they are always slow doing.

9iASAgent fails after computer name change

Similar Messages

Maybe you are looking for