Im using License4J to add licensing to a project. I wrote up some demo programs that had worked initially, but then one day I logged on and tried to run it and my licenses all came back as invalid. No licenses can be verified except for floating licenses installed on the floating license server.
I've checked all L4J-related logs that I could find and none made any mention of license invalidations. I tried googling the issue but couldn't find any posts there either.
Related
By the end of last week our central IT Department introduced SCCM and applied it to a bunch of clients in our division. My colleagues and I work as so called "IT-Partner" in a 1st level support for a few hundrets of colleagues. Now we're facing some problems with our new SCCM System (installed packages do not work etc.) Now we'd like to "reset" applications so the SCCM Agend will reinstall them. I've read something about the detection methods but unfortunatelly I do not really know how they work nor I know where those methods are saved. I want to "analyse" those methods so I know which file to modify / delete that the agent will reinstall the application.
By the way, how much time does SCCM take from "assigning" a package to applying to the client?
Assuming you only have the client and no access to the SCCM Console the detection methods can be found using WMI. They are stored in root\ccm\CIModels in the Class Local_Detect_Synclet.
The format is XML in one column and it is designed so that all kinds of detection methods can basically be represented in the same style so it's not very readable but you should be able to get some basic understanding about the detection method used.
Keep in mind this is only true if the software was deployed in the "new" (introduced in sccm 2012) application format and not for the "old" package/program format.
If you want more detail I once tried to automate the process of triggering a reinstall for any given application but ultimately failed due to problems with the chache/distribution point. I posted all my findings here.
So from an application POV. When you deploy an app the detection method is setup in SCCM to determine wether or not the application installed successfully. This detection method could be configured a variety of ways. For example, it could check to see if the msi code is installed to determine success, it could check the .exe and compare it to a specific version, or even check a registry file for existence. In order to change/modify these detection methods you should be an SCCM admin and be able to login to the console. From there you would select the specific application or package you want to analyze and click through the properties of the deployment.
I am doing a software project, together with people in other states. I just set up a Bugzilla website (Bugzilla 4.4.9, Apache 2.4, and Windows 7 Professional 64-bit) and it is available on the internet. I have disabled Bugzilla's self-registration of user accounts.
Now I would like to further restrict the website access (such as search and view bug reports) only to those people who have Bugzilla accounts and have signed in. Put it another way, I don't want anonymous visitors to be able to use the website or search engines to index the site. Is this something doable without modifying Bugzilla's code, which is bad in many ways? If yes, how?
If brute-force modification of Bugzilla's code is the only way, I would very appreciate any info about which files to modify or, if available, the details. I am new to Bugzilla, and I never coded with Perl.
Googled for the answer, but did not find any.
I feel I got the answer:
sign into the system as the maintainer
Go to Administration, Parameters, User Authentication.
Check requirelogin
All the above does is only the homepage is visible to visitors, but no search of results or website browser is allowed.
Cheers.
The internal application which my team works on is currently on a version 10.y.z.build_number.
During a discussion if the next release is significant enough for 10.y+1.z.build_number or it should be 10.y.z+1.build_number I suggested that we could keep it simple and align the version numbers with the calendar.
For example the next release would be 13.8.1.build_number which stands for the 1st release for August 2013. The September one would be 13.9.1.build_number.
The idea has been discarded for now.
For a paid application I can imagine that having the 1st number is useful to easily distinguish between releases with free upgrades and major releases which require paid update. x+1.y.z would be paid and x.y+1.z would be free.
After a quick search I found Jeff Attwood's What's In a Version Number, Anyway?.
However for an unpaid internal application I cannot think of weak points for the calendar-aligned version numbers and the beauty of simplicity speaks to me. As one of the comments on Jeff Atwood's post says: Microsoft Office 2003 is a far more meaningful name than Microsoft Office 11.
The question:
Is my vision clouded by enthusiasm and are there known issues for calendar-aligned version numbers?
For an internal application, the information that the version needs to convey is the revision or commit of the sources from which said app is built.
Since you have access to the VCS managing that app sources, the version can help bug reporting like: "found in revision xxx".
That is far more valuable that a date-based tag, which can be subject to interpretation in order to find the exact version of the sources exhibiting a bug that need to be reporting.
You can combine that with any version policy you want, with tags: git, for instance, can generate a unique version number based on SHA1 + a tag. See:
"Deriving application build version from git describe - how to get a relatively straightforward string?"
"Simulating a global revision number with git"
But the idea remains: date is a metadata managed by a VCS or a build scheduler like Jenkins/Hudson/TeamCity... It doesn't have to be in the public version number of the app.
What need to be in that version number is an info allowing to get the exact sources from which that app was built.
Is there a simple and automatic way of checking if a visitor to my website (written in asp.net) is using the latest version of his browser? This would allow me to display a message to inform them that they're running an old version and that they might want to upgrade.
My website is tested on most broswers but I don't test old versions (such as Internet Explorer 6 etc). When one of my visitors is using such an old version, basically, I would like to encourage (not force) them to upgrade.
Of course I could do this myself by getting the version of the browser and look it up in my database but I don't want to have to maintain a 'browser version' database myself.
Any ideas?
Speaking as a user of websites, if I come across a site that advised me to upgrade my browser then that would be an immediate black mark against that site.
I might not be able to upgrade (if I'm accessing from a corporate network for example); I might have a specific reason for using a particular version (if I'm a web developer wanting to ensure compatibility with my user community for example).
So personally, I would say that a blanket disclaimer that you don't test this site on earlier versions would be the way to go. That's quite apart from the technical challenge of what you want to do.
Edit: as Yeti points out, however valid my concerns, I don't answer the question directly. This is done in Pace's answer, and the w3schools resource he points to gives you what you need to do this on the client side.
I am using Visual Studio Team System 2008, version 9.0.30729.1 SP. I have a database project that I was working with yesterday with no issues - I was able to build and deploy the database successfully. Today, however, when I open the solution I receive what is listed as a "Warning" that halts any Build/Deploy/etc process, but cannot be suppressed via the Project Properties page.
The Warning reads: "TSD3004: The application encountered an unexpected error. To diagnose this problem, enable tracing. You should contact product support."
I did contact Product Support, but they insist I pay for someone to help me get this fixed. There are zero records returned from an search of "TSD3004" on either MSDN or support.microsoft.com, and there are only three returned from a Google search (all irrelevant).
Can anyone please help me figure out what's happening?
Have you tried asking on Microsoft's dedicated forum?
http://social.msdn.microsoft.com/Forums/en-US/vstsdb/threads/
Actually I guess you did.. :)
http://social.msdn.microsoft.com/Forums/en-US/vstsdb/thread/eea24181-e115-4f56-a482-58059160d705