QUSER password must be *NONE

---

The prestart job that lets CAWIN95 communicate with the AS/400 runs under the user profile QUSER. The big gotcha thats bit us is QUSER must be authorized to every library in the library list. If someone sticks a library in the system library list without QUSER having authority, all prestart jobs in QCMN fail, and 32 bit clients like CAWIN95 and the 32 bit OS/2 client fail to connect. 16 bit clients like CAWIN3.1 don't use a prestart job, and are unaffected. It's a bitch to figure out the first time it happens.

---

I had problems with my Anynet connection timing out after installing IE 4.0. I was using CA V3R1M2. Installing the new nsadmin.exe didn't fix the problem. However, installing Service Pack SF45545 did.

---

Start your host server on the AS/400. Before you can use CA/400, the AS/400 has to be ready to serve it to the PC. STRHOSTSVR *ALL This command ships as *PUBLIC *EXCLUDE authority. Make sure you fix that too.

---

Another possibility is that you need to start the Host Servers (these run in subsystem QSERVER). If you enter te following command "STRHOSTSVR *ALL" you will start the Host Servers. This was thhe problem that I had.

---

The CWBSY1000 comes up for just about any error, not just "security" type errors. I most recently had this when I forgot to install MSDLC on the PC prior to firing up the SNA connection.

---

Use the CWBPING 'as400name' command on the pc. All the server tasks should be up and running.

---

Hi, try droping the ODBC source then creating it again. We had this problem on some win95 data entry systems and this worked to fix it. (don't ask me why, i do not know). On one machine, we had to blow off client access completely and re-install. (Operator must have made the bit gods angry.....) Also, we had similar wierdness when the client machine did not have a proper DNS entry. Hope this helps

---

I'm trying to use Client Access ODBC 32 bits driver under Windows 95, everytime I try to connect to the data source I always get the same message : CWBSY1000 Communication error while validating security information on system S....... Everything works fine when I use Client Access and the 16 bits ODBC driver under Windows 3.1 What can I do to make it work ???

---

Yes I have other machines that are hooked via TCP/IP and I can ping the AS/400 from the machines that do not work. I have not had to put anything in the hosts files for either working or not working machines but I have tried to do this but still doesn't work. I think it has something to do with Win NT user profile but not sure where to look for it..

---

If you are using TCP/IP, can you ping the AS/400 and can the AS/400 ping this PC? Did this succeed for both IP address and name (PC-to-AS/400)? My experience has been that the majority of the time when I get this error the host servers are not started on the AS/400. However, if you don't have name resolution (DNS Server or HOSTS file) I think you will get this same error. Do you have other CAW95NT PCs connected to the AS/400 using TCP/IP?

---