Skip to main content
Solved

What is - error. *** -[NSPlaceholderString initWithString:]: nil argument ?

  • February 20, 2015
  • 9 replies
  • 0 views

Forum|alt.badge.img+4

Hi,

I just created a new CS6 enterprise package, this is the error I receive when I push it out to a Mac using Casper remote 9.64, I've been unable to find an explanation for error ** -[NSPlaceholderString initWithString:]: nil argument *.

Just confirmed that the CS6 Install package works through ARD.

Any ideas?
Cheers
Phil

>>>>>>>>>>>>>>>>>>>>>>
Successfully authenticated.
Verifying Computer's Identity...
The MAC Address has been verified.
Checking Operating System Version...
Running Mac OS X 10.9.5 (13F34)
Verifying /usr/sbin/jamf...
/usr/sbin/jamf is current (9.64)
Verifying /Library/Preferences/com.jamfsoftware.jamf.plist...
Preparing Policy...
There was an error.
*** -[NSPlaceholderString initWithString:]: nil argument [/ul][/ul]

Best answer by jacob_salmela

I have seen this in our environment and was told it is a defect that prevents anything from running on a computer while it is at the login screen, such as a "startup" trigger. But there is no fix at this time.

View original
Did this topic help you find an answer to your question?

9 replies

Forum|alt.badge.img+13
  • Contributor
  • 180 replies
  • Answer
  • February 20, 2015

I have seen this in our environment and was told it is a defect that prevents anything from running on a computer while it is at the login screen, such as a "startup" trigger. But there is no fix at this time.


Forum|alt.badge.img+1
  • New Contributor
  • 5 replies
  • February 20, 2015

Is this an issue related to the recent 9.64 upgrade? I started noticing clients not applying the policies changes I am pushing out and found the same error messages in the log. I don't recall ever having this issue since I always schedule system update/maintenance tasks after hours when no one is logged in to the computer.


larsc
Forum|alt.badge.img+4
  • New Contributor
  • 5 replies
  • February 20, 2015

We also ran into this problem after upgrading to 9.64 two days ago and it rendered ~50 of our lab room Macs not able to talk to the JSS. It seems it starts working normally (at least temporarilly) when someone logs in at the consol. A restart does not help. As I understand this means the client won't be able to check-in or do inventory update as long as this problem persists - unless you manually (and daily?) physically logs in to them... Or has anyone come to any solution?


Forum|alt.badge.img+10
  • New Contributor
  • 306 replies
  • February 20, 2015

This is defect D-008559 and introduced in 9.64. It's been marked as critical to the dev team since it does impact operational usage. I'm patiently waiting as it also hit us.


Forum|alt.badge.img+18
  • Esteemed Contributor
  • 831 replies
  • February 20, 2015

Add me to this list...
Gabe Shackney
Princeton Public Schools


Forum|alt.badge.img+10
  • New Contributor
  • 306 replies
  • February 20, 2015

@gshackney email your account manager. Just let him know the defect number so they can add your account to the list. The more effected by this, the more resources allocated to fixing it.


Forum|alt.badge.img+18
  • Esteemed Contributor
  • 831 replies
  • February 20, 2015

According to him they hope to have 9.65 by end of day today to correct this.
Gabe Shackney
Princeton Public Schools


Forum|alt.badge.img+4
  • Contributor
  • 24 replies
  • February 20, 2015

Running into this as well. Ugh.


Forum|alt.badge.img+17
  • Contributor
  • 570 replies
  • February 20, 2015

Hi @lynnp

9.65 addresses the issue being discussed in this thread; it should be available for you to download under the My Assets section of JAMF Nation.

If you find, after updating to 9.65, that there are some machines that are not getting their communication with the JSS restored after ~10 minutes, please go through the steps in this KB.

Thanks!
Amanda Wulff
JAMF Software Support


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings